Entity-linked Prometheus metrics & dashboards (per Session/deployment/resource group)
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 368
Description
Provide Prometheus-backed observability per entity. Each entity (Session, deployment, resource group, etc.) exposes instant and range metric values plus dedicated dashboards.
Scope:
- Define per-entity Prometheus metric schema (instant + range queries)
- Provide entity-scoped dashboards
- Re-implement the legacy monthly resource-usage API on top of the Prometheus-backed metrics (replacement for the existing 'resource usage per month' API)
Related existing issues to reference/link during BEP: BA-6449 (deprecate legacy resource usage/stats REST endpoints), BA-6114 (migrate resource_usage callers off Valkey), BA-126 (refactor resource usage API).
JIRA Issue: BA-6683
Contributor guide
Research direction
Start by reviewing the existing resource usage per month API and the related BA-6449, BA-6114, and BA-126 issues. Define what the BEP must cover for per-entity instant and range metrics, entity-scoped dashboards, and the Prometheus-backed API replacement; done means these schemas, dashboards, and replacement behavior are specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, python
- Domain
- backend-api-design, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100