Contributor Focus: [Service Objectives] Measure backend behavior in terms of reliability targets rather than raw counters only
ETA: 2 days
Context
Raw counts are useful, but operators also need service-level indicators for freshness and timeliness.
Problem
Without defined SLO-style metrics, it is harder to reason about whether the backend is meeting product expectations.
Task Breakdown
- Define backend indicators such as poll freshness, execution lateness, and retry delay.
- Add instrumentation for those indicators.
- Expose the metrics in a stable, documented format.
- Suggest thresholds or targets that are reasonable for current scale.
- Document known limitations of the measurements.
Acceptance Criteria
- Backend timeliness can be measured directly.
- Metrics are understandable by contributors and operators.
- Suggested thresholds are documented.
- The observability model supports future alerting work.
Contributor Focus: [Service Objectives] Measure backend behavior in terms of reliability targets rather than raw counters only
ETA: 2 days
Context
Raw counts are useful, but operators also need service-level indicators for freshness and timeliness.
Problem
Without defined SLO-style metrics, it is harder to reason about whether the backend is meeting product expectations.
Task Breakdown
Acceptance Criteria