Notification channels

Notification channels define how and to whom alert notifications are sent. A notification channel specifies the delivery method and recipients, and can be reused across multiple alerts. Every alert needs to be associated with at least one notification channel.

Any user on the account can create a notification channel. Both email and webhook notification channels are supported. All users in the account can view, edit, and delete channels created by themselves or other users.

Notification channels are managed independently of alerts, making it easier to reuse the same notification across multiple alerts.

Email notification channel settings

Configure an email notification channel to send alert notifications to email recipients. Email notification channel settings include:

Name. A unique name for the notification channel.

Recipients. The usernames or email addresses or up to 10 recipients.

Webhook notification channel settings

Configure a webhook notification channel to sent alert notifications to a webhook URL. Webhook notification channel settings include:

• Name. A unique name for the notification channel.
• Authentication type. The authentication method used for requests: None, which requires no authentication, or Basic, which requires a username and password.
• Endpoint URL. The Webhook URL that receives alert notifications.

Optionally, specify the following client certificate authentication settings:

• TLS hostname. The hostname used to verify the server's certificate. If not provided, it's derived from the endpoint URL.
• CA certificate. The CA certificate used to verify the certificate presented by the webhook endpoint. If the certificate is not signed by a well-known certification authority, enter the CA certificate in the PEM format.
• Client certificate. The client certificate used to authenticate requests to the webhook endpoint. Provide the certificate in PEM format.
• Client private key. The private key used with the client certificate. Provide the key in PKCS#8 format.

  📘

  TLS certificate requirements and dependencies

  TLS certificate fields are optional, but may be required depending on your endpoint configuration. These fields are interdependent. For example, if you provide a client certificate, you must also provide the corresponding client key. A CA certificate may also be required if the endpoint uses a private certificate authority.

You can also add custom headers. If you do so, you'll need to provide the name and value for each custom header.