-
Notifications
You must be signed in to change notification settings - Fork 100
[Backend] Build Keeper SLO Metrics for Poll Freshness and Execution Lateness #255
Copy link
Copy link
Open
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programbackendGenerated from backend issue tags: backendGenerated from backend issue tags: backendcomplexGenerated from frontend issue tags: complexGenerated from frontend issue tags: complexkeeperGenerated from backend issue tags: keeperGenerated from backend issue tags: keepermetricsGenerated from backend issue tags: metricsGenerated from backend issue tags: metricsslosGenerated from backend issue tags: slosGenerated from backend issue tags: slos
Metadata
Metadata
Assignees
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programbackendGenerated from backend issue tags: backendGenerated from backend issue tags: backendcomplexGenerated from frontend issue tags: complexGenerated from frontend issue tags: complexkeeperGenerated from backend issue tags: keeperGenerated from backend issue tags: keepermetricsGenerated from backend issue tags: metricsGenerated from backend issue tags: metricsslosGenerated from backend issue tags: slosGenerated from backend issue tags: slos
Type
Fields
Give feedbackNo fields configured for issues without a type.
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