open-telemetry / open-telemetry/opentelemetry-java
Better declarative config error messages
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
When an error occurs in declarative config, the error message should tell you the location in the document where the error occurred.
Currently, we only give generic errors of the form "batch span processor exporter is required but is null". These messages can be ambiguous since its possible to have multiple processors. Even when unambiguous, they're more difficult to parse and fix than something that includes document context like: .tracer_provider.processors[0].batch exporter is required but is null.
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
Locate the declarative config validation path that produces the generic error about a null batch span processor exporter, then inspect how document locations are represented during validation. Done means errors include the relevant document path, such as .tracer_provider.processors[0].batch, while retaining the existing validation context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100