Metrics Rules

Generate baseline threshold rules from recent derived-signal history. Existing rules are skipped automatically. Create is capped at 200 rules per run.

Window (hours)

Min points

Service scope

Mode

Attr FP

Build a derived-signal dashboard directly from your active rules. Existing chart titles are skipped automatically.

Create Rule

Manual create supports Threshold and Composite rules. Seasonal rules are generated via the Auto Rules panel. Threshold, composite, and seasonal rules can coexist for the same signal scope; on equal severity, precedence is seasonal > composite > threshold.

Name

Rule Type

Source

Signal

Service

Attr FP

Comparator

Warning

Critical

Min Sample

10 active rules

Name	Type	Source	Signal	Service	Attr FP	Primary	Secondary	Min Sample
CWV CLS	threshold	RUM Vitals	Cumulative Layout Shift CLS	any	—	gt / 0.1 / 0.25	—	5
CWV FCP	threshold	RUM Vitals	First Contentful Paint FCP	any	—	gt / 1800.0 / 3000.0	—	5
CWV FID	threshold	RUM Vitals	First Input Delay FID	any	—	gt / 100.0 / 300.0	—	5
CWV INP	threshold	RUM Vitals	Interaction to Next Paint INP	any	—	gt / 200.0 / 500.0	—	5
CWV LCP	threshold	RUM Vitals	Largest Contentful Paint LCP	any	—	gt / 2500.0 / 4000.0	—	5
CWV TTFB	threshold	RUM Vitals	Time to First Byte TTFB	any	—	gt / 800.0 / 1800.0	—	5
Composite trace distress	composite	Traces	Latency p95 latency_p95_ms	trace-svc-0	—	gt / 250.0 / 450.0	traces:trace_error_ratio gt / 0.04 / 0.08	5
Exception volume elevated	threshold	Errors	Exception Volume exception_volume	err-svc-0	—	gt / 1.0 / 3.0	—	1
Trace error ratio elevated	threshold	Traces	Trace Error Ratio trace_error_ratio	trace-svc-0	—	gt / 0.04 / 0.08	—	5
Trace latency elevated	threshold	Traces	Latency p95 latency_p95_ms	trace-svc-0	—	gt / 250.0 / 450.0	—	5

How Metrics Rules Work (Simple)

SOBS turns raw telemetry into minute-level derived signals, then evaluates rules. When a rule changes state to warning or outlier, you can connect notification rules and agent automation to raise or reuse GitHub issues.

Derived Signals Metrics Rules Notification Rules Auto Issue / Copilot

Threshold

One signal compared to warning and critical thresholds.

Composite

Primary and secondary signals must both be active.

Seasonal

Thresholds vary by hour/day bucket to reduce false positives on periodic traffic.

Example 1: Threshold Rule

Signal: trace error ratio. Warning = 0.08, Critical = 0.12, Min sample = 10.

signal trend warning event outlier event

Trigger example: after sustained rise, one point crosses warning then another crosses critical. A notification rule can send Slack/email, and an agent rule can auto raise or dedupe a GitHub issue when state is warning or critical.

Example 2: Composite Rule

Primary: error ratio. Secondary: trace volume. Both must be active at the same time.

Trigger example: high error ratio alone does not fire if traffic is low; once trace volume threshold is also crossed, composite rule activates. This is useful for reducing low-traffic noise before creating notifications/issues.

Example 3: Seasonal Rule

Signal: request latency. Different thresholds by hour-of-day (UTC), so peak hours can have higher baseline.

seasonal baseline envelope actual series bucket-triggered event

Trigger example: point breaches the active UTC bucket threshold. This usually catches true anomalies while ignoring predictable daily swings. The same event can then feed notification channels and agent issue automation.

Auto Make Metric Rules

Auto Generate Dashboard from Active Rules