SRE - Weekly report
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
Summarize usage to indicate how well the Dashboard is behaving.
Basically take https://mon.kernelci.org/public-dashboards/715f7faddb014b0e99fd025f4ae19a7a?from=now-1h&to=now&timezone=browser&var-summary_mode=range and format as an email to the Working Group.
If possible we'd like to see at least "Requests Count" grouped by "Response Status Code", which should give us a rough idea of failed requests, including timeouts.
Ideally we should get the uptime, to see how often the server crashed or otherwise was offline during releases deployments. That might require a periodical prometheus exporter hitting the "status" endpoint.
If this can be achieved directly by Grafana or Prometheus, it is an acceptable solution.
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
Start with the linked Grafana public dashboard and investigate whether Grafana or Prometheus can generate the requested weekly report directly. The result should email the Working Group with Requests Count grouped by Response Status Code and, if feasible, uptime or offline periods during deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100