opensafely-core / opensafely-core/opencodelists
Link Sentry errors to Honeycomb traces
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
Why are we doing this?
Sentry notifies us of errors on the site and allows us to interrogate them. Honeycomb allows us to view OTel data exposed by the site. Use of Sentry will be enhanced if we can relate Sentry errors directly to Honeycomb traces. This may help us identify what's causing an issue as Honeycomb has additional data, and can be more easily related to other requests. This can be done manually probably but it's not very convenient.
How will we know when it's done?
OpenCodelists Sentry errors can be related directly to Honeycomb traces in the UI.
What are we doing?
The Honeycomb documentation shows that this kind of linkage is possible in principle. investigate if it's possible for us, and enable it if possible.
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 linked Honeycomb documentation and review how OpenCodelists currently sends Sentry errors and OpenTelemetry data. Determine whether the two services can be linked in the UI, then document the required configuration and verify that a Sentry error opens its corresponding Honeycomb trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100