open-telemetry / open-telemetry/opentelemetry-python
OTLP/HTTP exporter should honour the spec retry status codes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
See the table here https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#failures-1
I was kind of confused to see that table and the retry section here define differently https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#retry. So we should probably seek some clarification before actually implementing this change.
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 OTLP specification's Failures table and the Exporter retry section linked in the issue. Resolve the discrepancy before implementation; done means the applicable retry status-code behavior and the resulting change scope are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100