open-telemetry / open-telemetry/opentelemetry-ruby
Implement internal metrics
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Now that we have metrics... we can have metrics about the metrics! (and the logs and the spans.)
See Semantic conventions for OpenTelemetry SDK metrics
This document describes metrics emitted by the OpenTelemetry SDK components themselves about their internal state.
For example, otel.sdk.processor.log.queue.size - The number of log records in the queue of a given instance of an SDK log processor.
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 Semantic Conventions for OpenTelemetry SDK metrics document and identify the internal metrics required for the SDK's metrics, logs, and spans. Use the example otel.sdk.processor.log.queue.size as a reference, then determine the affected SDK components and how completion will be verified against the conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100