Stay organized with collectionsSave and categorize content based on your preferences.
The alert config for model monitoring.
Fields
enableLoggingboolean
Dump the anomalies to Cloud Logging. The anomalies will be put to json payload encoded from protoModelMonitoringStatsAnomalies. This can be further synced to Pub/Sub or any other services supported by Cloud Logging.
notificationChannels[]string
Resource names of the NotificationChannels to send alert. Must be of the formatprojects/<project_id_or_number>/notificationChannels/<channelId>
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-27 UTC."],[],[],null,["# ModelMonitoringAlertConfig\n\nThe alert config for model monitoring.\nFields `enableLogging` `boolean` \nDump the anomalies to Cloud Logging. The anomalies will be put to json payload encoded from proto [ModelMonitoringStatsAnomalies](/vertex-ai/docs/reference/rest/v1beta1/projects.locations.batchPredictionJobs#ModelMonitoringStatsAnomalies). This can be further synced to Pub/Sub or any other services supported by Cloud Logging.\n`notificationChannels[]` `string` \nResource names of the NotificationChannels to send alert. Must be of the format `projects/\u003cproject_id_or_number\u003e/notificationChannels/\u003cchannelId\u003e` \n`alert` `Union type` \n`alert` can be only one of the following:\n`emailAlertConfig` `object (`[EmailAlertConfig](/vertex-ai/docs/reference/rest/v1beta1/ModelMonitoringAlertConfig#EmailAlertConfig)`)` \nemail alert config. \n\nEmailAlertConfig\n----------------\n\nThe config for email alert.\nFields `userEmails[]` `string` \nThe email addresses to send the alert."]]
