Skip to content

Alerts

Alerts are one example of a supported entity type, a component of the Coralogix infrastructure capable of sending notifications.

Supported entity subtypes

An entity subtype adds an added layer of granularity to an entity type. For Alerts, an entity subtype consists of three elements: an alert type, a condition, and status.

The following entity subtypes for Alerts are supported:
SourceTypeConditionStatusDescription
LogsLOGS_IMMEDIATETriggered / ResolvedAlert immediately when a log of interest is detected. Docs
LogsLOGS_THRESHOLDMore than / Less thanTriggered / ResolvedAlert when the sum of logs crosses a predefined threshold. Docs
LogsLOGS_RATIO_THRESHOLDMore than / Less thanTriggered / ResolvedAlert when the ratio between two log queries reaches a set threshold. Docs
LogsLOGS_TIME_RELATIVE_THRESHOLDMore than / Less thanTriggered / ResolvedAlerts when a fixed ratio reaches a set threshold compared to a past time frame. Docs
LogsLOGS_ANOMALYMore than usualTriggered / ResolvedAlert when a log crosses an AI-generated baseline. Docs
LogsLOGS_NEW_VALUETriggeredAlert on a newly detected value in a time series. Docs
LogsLOGS_UNIQUE_COUNTMore thanTriggeredAlert based on a unique value count per key. Docs
MetricsMETRIC_THRESHOLDMore than / Less than / More than or equals / Less than or equalsTriggered / ResolvedAlert when a metric crosses a predefined threshold. Docs
MetricsMETRIC_ANOMALYMore than usual / Less than usual/Triggered /ResolvedAlert when a metric crosses an AI-generated baseline. Docs
TracingTRACING_IMMEDIATETriggeredAlert immediately when span duration exceeds a set latency. Docs
TracingTRACING_THRESHOLDMore thanTriggeredAlert when trace latency crosses a predefined threshold. Docs
FlowFLOWTriggered / ResolvedAlert when any combination of alerts occur in a specific sequence within a defined timeframe. Docs

All supported entity subtypes, consisting of EntityType and EntitySubType, can be found in the Alerts API.

Alerts schema

General reference

The full schema for Alerts may be found here.

Context reference

All templates have access to the _context variable, which contains metadata about the notification source type, including system identifiers and trigger details. This context allows you to dynamically customize your template content based on the notification's origin.

Find out more here.