In OKD, an alert is fired when the conditions defined in an alerting rule are true. An alert provides a notification that a set of circumstances are apparent within a cluster. Firing alerts can be viewed in the Alerting UI in the OKD web console by default. After an installation, you can configure OKD to send alert notifications to external systems.
In OKD 4.6, firing alerts can be viewed in the Alerting UI. Alerts are not configured by default to be sent to any notification systems. You can configure OKD to send alerts to the following receiver types:
Routing alerts to receivers enables you to send timely notifications to the appropriate teams when failures occur. For example, critical alerts require immediate attention and are typically paged to an individual or a critical response team. Alerts that provide non-critical warning notifications might instead be routed to a ticketing system for non-immediate review.
OKD monitoring includes a watchdog alert that fires continuously. Alertmanager repeatedly sends watchdog alert notifications to configured notification providers. The provider is usually configured to notify an administrator when it stops receiving the watchdog alert. This mechanism helps you quickly identify any communication issues between Alertmanager and the notification provider.
You can configure alert receivers to ensure that you learn about important issues with your cluster.
You have access to the cluster as a user with the
In the Administrator perspective, navigate to Administration → Cluster Settings → Global Configuration → Alertmanager.
Alternatively, you can navigate to the same page through the notification drawer. Select the bell icon at the top right of the OKD web console and choose Configure in the AlertmanagerReceiverNotConfigured alert.
Select Create Receiver in the Receivers section of the page.
In the Create Receiver form, add a Receiver Name and choose a Receiver Type from the list.
Edit the receiver configuration:
For PagerDuty receivers:
Choose an integration type and add a PagerDuty integration key.
Add the URL of your PagerDuty installation.
Select Show advanced configuration if you want to edit the client and incident details or the severity specification.
For webhook receivers:
Add the endpoint to send HTTP POST requests to.
Select Show advanced configuration if you want to edit the default option to send resolved alerts to the receiver.
For email receivers:
Add the email address to send notifications to.
Add SMTP configuration details, including the address to send notifications from, the smarthost and port number used for sending emails, the hostname of the SMTP server, and authentication details.
Choose whether TLS is required.
Select Show advanced configuration if you want to edit the default option not to send resolved alerts to the receiver or edit the body of email notifications configuration.
For Slack receivers:
Add the URL of the Slack webhook.
Add the Slack channel or user name to send notifications to.
Select Show advanced configuration if you want to edit the default option not to send resolved alerts to the receiver or edit the icon and username configuration. You can also choose whether to find and link channel names and usernames.
By default, firing alerts with labels that match all of the selectors will be sent to the receiver. If you want label values for firing alerts to be matched exactly before they are sent to the receiver:
Add routing label names and values in the Routing Labels section of the form.
Select Regular Expression if want to use a regular expression.
Select Add Label to add further routing labels.
Select Create to create the receiver.