Configura canales de notificaciones para las alertas
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
La plataforma de Observabilidad te permite configurar canales de notificaciones para las alertas que configures. El sistema envía una alerta a estos canales personalizados cada vez que un evento provoca una alerta. De esta manera, puedes notificar a los destinatarios que necesites según tus métodos preferidos.
El dispositivo aislado de Google Distributed Cloud (GDC) no predefine canales de notificación
destinados a enviar alertas. Debes definir al menos un canal para recibir alertas. Si no defines una configuración del canal de notificaciones, el sistema de Observabilidad de GDC toma la configuración de los recursos de la plataforma como predeterminada. Por lo tanto, si no configuras los canales de notificación de, pero un administrador lo hizo para la organización, el sistema enviará alertas a esos canales.
Antes de comenzar
Para obtener los permisos que necesitas para configurar o ver canales de notificaciones, pídele al administrador de IAM del proyecto que te otorgue uno de los siguientes roles en el espacio de nombres del proyecto:
Editor de Observability Pipeline: Edita o modifica recursos personalizados de ObservabilityPipeline. Solicita el rol de editor de Observability Pipeline (observabilitypipeline-editor).
Visualizador de canalización de observabilidad: Visualiza recursos personalizados de ObservabilityPipeline. Solicita el rol de visualizador de la canalización de Observabilidad (observabilitypipeline-viewer).
Configura los canales de notificaciones
Sigue estos pasos para configurar los canales de notificaciones de las alertas que configuraste para el monitoreo del sistema:
Crea un objeto ConfigMap y, luego, impleméntalo en el espacio de nombres de tu proyecto. El objeto debe contener las reglas de configuración en el archivo alertmanager.yml.
apiVersion:v1kind:ConfigMapmetadata:# The name must match the ConfigMap name specified in the ObservabilityPipeline custom resource.name:CUSTOMIZED_CONFIGMAP_NAME# Choose namespace that matches the project's namespacenamespace:PROJECT_NAMESPACEdata:# The file name must be alertmanager.yml.alertmanager.yml:|# Add the customized Alertmanager configuration here.
Reemplaza lo siguiente:
CUSTOMIZED_CONFIGMAP_NAME: Es el nombre del archivo de configuración que usarás en la CR de ObservabilityPipeline durante el siguiente paso.
PROJECT_NAMESPACE: Es el espacio de nombres de tu proyecto.
Configura el recurso personalizado de ObservabilityPipeline en un editor de línea de comandos para importar la configuración en el campo alertmanagerConfig anidado en el campo alerting.
# Configure observability pipelineapiVersion:observability.gdc.goog/v1kind:ObservabilityPipelinemetadata:# Choose namespace that matches the project's namespacenamespace:PROJECT_NAMESPACEname:observability-configspec:# Configure Alertmanageralerting:# Permission: PA and AO# The alerts configuration must be in the key "alertmanager.yml" of the configMapalertmanagerConfig:CUSTOMIZED_CONFIGMAP_NAME...
Reemplaza lo siguiente:
PROJECT_NAMESPACE: Es el espacio de nombres de tu proyecto.
CUSTOMIZED_CONFIGMAP_NAME: Es el nombre que usaste para tu archivo de configuración en el objeto ConfigMap. El nombre debe coincidir exactamente.
Guarda los cambios en el CR de ObservabilityPipeline y cierra el editor de la línea de comandos.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThe Observability platform allows users to configure custom notification channels for alerts, ensuring that notifications are sent to the desired recipients through their preferred methods.\u003c/p\u003e\n"],["\u003cp\u003eGDC air-gapped appliance requires users to define at least one notification channel to receive alerts, as it does not have predefined channels; if no channels are defined, it uses organization-level configurations.\u003c/p\u003e\n"],["\u003cp\u003eTo configure or view notification channels, users need specific permissions, either the Observability Pipeline Editor role for modifying configurations or the Observability Pipeline Viewer role for viewing configurations.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring notification channels involves defining the configuration in an \u003ccode\u003ealertmanager.yml\u003c/code\u003e file, creating a \u003ccode\u003eConfigMap\u003c/code\u003e object with this file, and then updating the \u003ccode\u003eObservabilityPipeline\u003c/code\u003e custom resource to point to this \u003ccode\u003eConfigMap\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Configure notification channels for alerts\n\nThe Observability platform lets you configure notification channels for the alerts you set up. The system sends an alert to these customized channels whenever an event causes an alert. This way, you can notify the recipients you need according to your preferred methods.\n\nGoogle Distributed Cloud (GDC) air-gapped appliance does not predefine notification channels\n\nintended for sending alerts. You must define at least one channel to receive alerts. If you don't define a notification channel configuration, the GDC Observability system takes the configuration from the platform resources as a default. Consequently, if you don't configure\n\nnotification channels but an administrator did it for the organization, then the system sends alerts to those channels.\n\nBefore you begin\n----------------\n\nTo get the permissions you need to configure or view notification channels, ask your Project IAM Admin to grant you one of the following roles in your project namespace:\n\n- **Observability Pipeline Editor** : edits or modifies `ObservabilityPipeline` custom resources. Request the Observability Pipeline Editor (`observabilitypipeline-editor`) role.\n- **Observability Pipeline Viewer** : views `ObservabilityPipeline` custom resources. Request the Observability Pipeline Viewer (`observabilitypipeline-viewer`) role.\n\nConfigure notification channels\n-------------------------------\n\nWork through the following steps to configure notification channels for the alerts you set up for system monitoring:\n\n1. Define the Observability alerting configuration following the specification in \u003chttps://prometheus.io/docs/alerting/latest/configuration/\u003e.\n2. Create a `ConfigMap` object and deploy it into your project namespace. The object must contain the configuration rules in the `alertmanager.yml` file.\n\n apiVersion: v1\n kind: ConfigMap\n metadata:\n # The name must match the ConfigMap name specified in the ObservabilityPipeline custom resource.\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eCUSTOMIZED_CONFIGMAP_NAME\u003c/span\u003e\u003c/var\u003e\n # Choose namespace that matches the project's namespace\n namespace: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePROJECT_NAMESPACE\u003c/span\u003e\u003c/var\u003e\n data:\n # The file name must be alertmanager.yml.\n alertmanager.yml: |\n # Add the customized Alertmanager configuration here.\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCUSTOMIZED_CONFIGMAP_NAME\u003c/var\u003e: The name of your configuration file to use it in the `ObservabilityPipeline` CR during the following step.\n - \u003cvar translate=\"no\"\u003ePROJECT_NAMESPACE\u003c/var\u003e: The namespace of your project.\n\n | **Note:** Follow the same syntax as described in \u003chttps://prometheus.io/docs/alerting/latest/configuration\u003e to define the notification channels in the `alertmanager.yml` file.\n3. Configure the `ObservabilityPipeline` custom resource in a command-line editor to import the configuration in the `alertmanagerConfig` field nested in the `alerting` field.\n\n # Configure observability pipeline\n apiVersion: observability.gdc.goog/v1\n kind: ObservabilityPipeline\n metadata:\n # Choose namespace that matches the project's namespace\n namespace: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePROJECT_NAMESPACE\u003c/span\u003e\u003c/var\u003e\n name: observability-config\n spec:\n # Configure Alertmanager\n alerting:\n # Permission: PA and AO\n # The alerts configuration must be in the key \"alertmanager.yml\" of the configMap\n alertmanagerConfig: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eCUSTOMIZED_CONFIGMAP_NAME\u003c/span\u003e\u003c/var\u003e\n ...\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePROJECT_NAMESPACE\u003c/var\u003e: The namespace of your project.\n - \u003cvar translate=\"no\"\u003eCUSTOMIZED_CONFIGMAP_NAME\u003c/var\u003e: The name you used for your configuration file in the `ConfigMap` object. The name must match exactly.\n4. Save the changes in the `ObservabilityPipeline` CR and exit your command-line editor."]]