opensafely-core / opensafely-core/sysadmin
Switch to ingest key
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
The collector proxy uses a configuration key to authenticate to Honeycomb. This was the only api key type that existed when we set it up
However, honeycomb now supports Ingestion keys, which can only write data, not modify config.
We should switch the collector to using one of these keys instead.
Probably also should do the same for any other otel emitting services, e.g. job-server, opencodelists, controller, etc
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
The issue names the collector proxy and possible emitters job-server, opencodelists, and controller, but no files. Start by locating their Honeycomb/OpenTelemetry authentication configuration; done means all intended services use ingestion keys and existing telemetry still works.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100