The associated dataset.

Optional dataset to query across. Defaults to whatever is configured to be the default dataset for the organization.

User defined id for getting/updating/deleting the alert rule through the API.

Human-readable and templatable name for the check. In Prometheus alerting rules this is called "alert".

An editable PromQL expression that can leverage the complete Dash0 Query Language. It furthermore
supports a variable called $__threshold.

• $__threshold can be used as a placeholder for both the degraded and failed thresholds. The
  thresholds are defined in the thresholds field. When $__threshold is used in the expression,
  the thresholds field is required and at least one of the thresholds must be defined.

  Usage of $__threshold implies that the PromQL expression may have to be evaluated up to two
  times using the degraded threshold and critical threshold respectively.

• Top-level AND statements are treated as enablement conditions that specify when the check should
  "be running", i.e., is active. The use-cases for enablement conditions are several, e.g., requiring
  a minimum amount of requests being served before triggering due to errors rates,
  maintenance windows or muted timeframes.

Specifies a check evaluation frequency.

For, also called "pending duration", specifies a time duration for how long the expression must
have been continuously satisfied before a check evaluation is created. When the check evaluation
is created, its "start" timestamp is set to the instant the pending duration started elapsing.

This is effectively equivalent to the "for" configuration in Prometheus alerting rules.

Default value is 0s, meaning that the check would transition immediately into one of the degraded
or critical states at the first failed evaluation.

If for is not set to 0s (or equivalent, like 0m), its value must be larger than or equal to that
of evaluationFrequency, as it does not make sense to expect the status of a check to change without another
evaluation having occurred.

Keep firing for, also called "resolution duration", that specifies a time duration for how long
the evaluation of the expression must be consistently healthy before an critical or degraded check
enters the healthy state, or de-escalates from critical to degraded.

This is effectively equivalent to the "keep_firing_for" configuration in Prometheus alerting rules.

Default value is 0s, meaning that the check would transition immediately into the healthy state at
the first successful evaluation.

If keep_firing_for is not set to 0s (or equivalent, like 0m), its value must be larger than or equal
to that of evaluationFrequency, as it does not make sense to expect the status of a check to change
without another evaluation having occurred.

Deprecated: use the "summary" annotation instead.

Deprecated: use the "description" annotation instead.

Deprecated: use "keep_firing_for" instead.