Dash0 acquires Polar Signals

Component schema

CheckThresholdBaseline

object1 direct reference

Definition

Adaptive baseline detector configuration. Its presence on CheckThresholds re-interprets degraded and failed as z-score cutoffs against the check rule's own predicted value and typical spread.

AnomalyDirectionrequired

Which deviations from the prediction fail the check. For a hand-written expression there is no parsedExpression and therefore no thresholdComparator, so this is the sole source of truth for directionality.

"both""above""below"
number

Optional minimum seasonal spread, expressed as a fraction of the prediction. The server default is used when omitted. For example, 0.05 makes a sensitivity cutoff of 3 require at least a 15% deviation when the measured spread is smaller.

number

Optional minimum traffic rate required for the detector to evaluate. Supported only for Services Metrics and Spans Metrics queries, in requests/second and spans/second respectively. Traffic is derived from the query's authored selections, filters, grouping, and rate window and evaluated ad hoc at the detector timestamp. Dashboard variable placeholders are omitted, as in the observed check query. Other query types, including hand-written PromQL, cannot configure this floor. Export compiles this floor into a PromQL enablement condition with the authored filters and service namespace/name matching. Import retains the condition rather than a typed floor. No traffic query or volume gate is applied when omitted.

Used by 1

These schemas and endpoints reference this type directly.