opensafely-core / opensafely-core/sysadmin
Migrate Honeycomb time-series metrics
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
Honeycomb are changing the way time-series metrics are stored, which means we need to migrate dashboards and triggers by the 10th of December 2026.
Examples of dashboards which need to be updated.
Honeycomb say you don't need to change anything about the way metrics are collected, but we configure a jobrunner-metrics dataset which might now be redundant because Honeycomb will store all metrics in the same Metrics dataset.
Contributor guide
No contributing guide indexed for this repository
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 Honeycomb migration guidance and the examples linked in the issue, then inspect services/otel-gateway/Dockerfile around the jobrunner-metrics dataset configuration. Identify all affected dashboards and triggers, migrate them to time-series metrics, and determine whether the separate dataset configuration is still needed. Done means the affected Honeycomb resources are migrated before 10 December 2026.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100