open-telemetry / open-telemetry/opentelemetry-python-contrib
exceptions: review reported semantic conventions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
I was reading this https://opentelemetry.io/docs/specs/semconv/exceptions/exceptions-logs/ and it looks like semconv suggests to send the exceptions data as attributes instead of body as we are doing now in the exceptions instrumentation.
We can add the attributes, not sure we should be removing the body to not break any user.
cc @iblancasa
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 OpenTelemetry exceptions semantic-conventions specification, then locate the exceptions instrumentation that currently places exception data in the body. Compare the current output with the specified attributes and review existing tests for this instrumentation. Done means the required attributes are emitted while the compatibility decision about retaining the body is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100