Skip to content

[Backend] Build Keeper SLO Metrics for Poll Freshness and Execution Lateness #255

@ayomideadeniran

Description

@ayomideadeniran

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

  1. Define backend indicators such as poll freshness, execution lateness, and retry delay.
  2. Add instrumentation for those indicators.
  3. Expose the metrics in a stable, documented format.
  4. Suggest thresholds or targets that are reasonable for current scale.
  5. 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.

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbackendGenerated from backend issue tags: backendcomplexGenerated from frontend issue tags: complexkeeperGenerated from backend issue tags: keepermetricsGenerated from backend issue tags: metricsslosGenerated from backend issue tags: slos

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions