Skip to main content

Alerts

Entities​

Oodle's alerting system allows you to monitor your metrics and receive notifications when certain conditions are met. There are three entities that make up the alerting system:

  • Monitors
  • Notification Policies
  • Notifiers

Additionally, you can create composite monitors that combine multiple monitor conditions.

Alerts functionality is available in the Oodle UI under the Bell icon in the sidebar navigation.

Monitors​

Monitors are the core of the alerting system. They define:

  • A PromQL query to evaluate
  • Conditions for triggering alerts (Warning and Critical thresholds)
  • Notification policy to be used for routing alerts
  • Labels allow specifying a set of additional labels to be attached to the alert.
  • Annotations specifies a set of informational labels that can be used to store longer additional information such as alert descriptions or runbook links.

Labels and annotations can be templated in a similar manner as documented in Prometheus alertmanager.

Monitors are periodically evaluated and alerts are triggered when threshold conditions are met.

See the Monitors documentation for detailed configuration instructions.

Monitors

Notifiers​

Notifiers are the endpoints where alerts are sent. Oodle supports several types of notifiers:

See the Notifiers documentation for detailed configuration instructions for each notifier type.

Notifiers

Notification Policies​

Notification policies determine how alerts are routed to different notifiers. Policies allow you to:

  • Define separate notifiers for Warning and Critical alerts
  • Create global policies that apply to all monitors in addition to the specific policies attached to the monitors.

See the Notification Policies documentation for detailed configuration instructions.

Notification Policies

Composite Monitors​

Composite monitors allow you to create monitors based on combinations of multiple monitors. Using the ALERTS metric, you can implement complex logic such as:

  • Alert only when multiple conditions are met simultaneously (AND logic)
  • Alert when any of several conditions are met (OR logic)
  • Alert when a threshold number of monitors are firing

For example, you can create a composite monitor that triggers only when both a database monitor and an API service monitor are firing, helping you identify dependent service failures.

See the Composite Monitors documentation for detailed configuration instructions and examples.

Support​

If you have any questions or need any assistance, please contact us via our help chat app available on the Support link in the sidebar, or by reaching out to support@oodle.ai.