관측 가능성 플랫폼을 사용하면 설정한 알림의 알림 채널을 구성할 수 있습니다. 이벤트로 인해 알림이 발생할 때마다 시스템은 이러한 맞춤 채널로 알림을 전송합니다. 이렇게 하면 원하는 방법에 따라 필요한 수신자에게 알림을 보낼 수 있습니다.
Google Distributed Cloud (GDC) 에어갭 어플라이언스는 알림 전송을 위한 Slack 또는 이메일과 같은 알림 채널을 미리 정의하지 않습니다.알림을 받을 채널을 하나 이상 정의해야 합니다. 알림 채널 구성을 정의하지 않으면 GDC 관측 가능성 시스템은 플랫폼 리소스의 구성을 기본값으로 사용합니다. 따라서이메일 알림 채널을 구성하지 않았지만 관리자가 조직에 대해 구성한 경우 시스템에서 해당 채널로 알림을 보냅니다.
시작하기 전에
알림 채널을 구성하거나 보는 데 필요한 권한을 얻으려면 프로젝트 IAM 관리자에게 프로젝트 네임스페이스에서 다음 역할 중 하나를 부여해 달라고 요청하세요.
관측 가능성 파이프라인 편집기: ObservabilityPipeline 맞춤 리소스를 수정합니다. 관측 가능성 파이프라인 편집자 (observabilitypipeline-editor) 역할을 요청합니다.
관측 가능성 파이프라인 뷰어: ObservabilityPipeline 맞춤 리소스를 확인합니다. 모니터링 파이프라인 뷰어 (observabilitypipeline-viewer) 역할을 요청합니다.
ConfigMap 객체를 만들고 프로젝트 네임스페이스에 배포합니다. 객체에는 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.
다음을 바꿉니다.
CUSTOMIZED_CONFIGMAP_NAME: 다음 단계에서 ObservabilityPipeline CR에 사용할 구성 파일의 이름입니다.
PROJECT_NAMESPACE: 프로젝트의 네임스페이스입니다.
명령줄 편집기에서 ObservabilityPipeline 커스텀 리소스를 구성하여 alerting 필드에 중첩된 alertmanagerConfig 필드의 구성을 가져옵니다.
# 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...
다음을 바꿉니다.
PROJECT_NAMESPACE: 프로젝트의 네임스페이스입니다.
CUSTOMIZED_CONFIGMAP_NAME: ConfigMap 객체에서 구성 파일에 사용한 이름입니다. 이름은 정확하게 일치해야 합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 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."]]