prometheus / prometheus/client_java
Implement Otel Translation Strategies per spec
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 833
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 86
Description
This will allow java users to enable NoTranslation mode for 1:1 otel metric names, if they so choose.
per the discussion on CNCF Slack, when we add documentation for this feature we should make sure to point out that modes without suffixes are technically in violation of the Open Metrics specification and may lead to unpredictable results. Example text for other warnings: https://github.com/prometheus/otlptranslator/blob/main/strategy.go#L25-L60
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 Prometheus configuration section and compare its translation strategies with the warning examples in prometheus/otlptranslator/strategy.go. Locate the Java metrics translation entry point and tests, then verify that users can select NoTranslation and that documentation explains the Open Metrics compatibility warning for suffixless modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100