When a monitor generates an alert in Chronosphere Observability Platform, it triggers notifiers based on the assigned notification policy. Notifiers are the endpoints receiving notifications, including where to deliver alerts and who to notify. You can configure notifiers to send details of the alert to a channel such as email, PagerDuty, or Slack. Observability Platform also supports unfurling of monitor graphs in Slack. This integration enables Slack users to view or share monitors in Slack channels aimed at mitigating alerts. Notification policies are rules that determine how to route notifications to notifiers based on signals that trigger from monitors. Teams own notification policies, and assign them either to a specific monitor or set as a default policy for all monitors in a specified collection. For programmatic configuration, the Chronosphere API can route alerts with inlineDocumentation Index
Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
Use this file to discover all available pages before exploring further.
destinations that reference
external connections,
the default approach for new credentials and routes. The same API still accepts
notifier_slugs that reference separate
notifiers until you finish moving
those routes. You can’t set both on the same notifier list. While you
migrate, see
Notifier resource migration.
Optionally, you can use signals to create groups of
notifications. Signals determine how to group alerts, which affects how many
notifications Observability Platform sends.
To customize the title and description of notifications generated by a monitor,
see Notification templates.
To view a history of alerts for a monitor:
- In the navigation menu, select Alerting > Monitors.
- Select a monitor.
- Click Alert history in the actions menu.