open-telemetry / open-telemetry/opentelemetry-python
Move synchronous gauge to stability
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem?
There is an incoming metrics API change in the opentelemetry specification to support a synchronous gauge instrument: https://github.com/open-telemetry/opentelemetry-specification/pull/3540.
This is spawned off of a long-running feature request in the specification for this instrument and a settable UpDownCounter: https://github.com/open-telemetry/opentelemetry-specification/issues/2318.
This should be implemented into the Python SDK once this specification change is merged.
Describe the solution you'd like
Implementation of the Synchronous Gauge instrument in the Python SDK.
Describe alternatives you've considered
If the OpenTelemetry Specification decides not to support this then this change is not needed.
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 by reading the OpenTelemetry specification pull request 3540 and issue 2318, then inspect the Python SDK's existing metrics instrument implementation. Confirm the specification change has merged before implementing the synchronous gauge; done means the instrument is supported in the Python SDK and its behavior is covered by the relevant project tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100