lambdaclass / lambdaclass/lambda_ethereum_consensus
Grafana/Prometheus/Promex issues after long running sessions
Open
Nobody has claimed this yet.
bug
P1
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
After long running sessions, Loki continues to work and logs are rendered as expected but the rest of Grafana dashboards appear without data:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; begin by reproducing the loss of Grafana dashboard data after a long-running session and inspect the Grafana, Prometheus, and PromEx setup. Compare the affected dashboards with the still-working Loki logs; done means the non-Loki dashboards continue displaying data after extended operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100