Use semantic metrics in the Service Dashboard
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Now that Count is a supported aggregation function for histograms, it would be nice to swap over the metrics derived from traces to metric semantic conventions defined by OTEL since these aren't subject to sampling.
The main one would be http.server.request.duration which can be used to calculate throughput, error rate, etc. https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestduration
Likewise, there is a semantic convention http.client.request.duration that could be used for displaying visualizations of outbound requests. Unfortunately, the low-cardinality path attribute is optional, but the Services tab could at least display external error per outbound host.
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 at the Service Dashboard and trace how metrics derived from traces currently produce throughput, error-rate, and outbound-request visualizations. Review the linked OTEL conventions for http.server.request.duration and http.client.request.duration; done means the dashboard uses these semantic metrics, including external errors by outbound host where supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100