traceloop / traceloop/openllmetry
🚀 Feature: OpenTelemetry Metrics
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this feature for?
All Packages
🔖 Feature description
Some values, like token usage, are better reported (also) as otel metrics. We should update all instrumentations to send metrics as well as traces.
🎤 Why is this feature needed ?
More ways to use the outputted data. Observability platforms can use metrics to set alerts on or to create dashboards.
✌️ How do you aim to achieve this?
This needs to be researched and defined. Please consult on slack before starting to work on this.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
None
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 reviewing the instrumentation across all packages and the OpenTelemetry Metrics specification linked in the issue. Consult the project Slack before beginning, since the approach still needs to be researched and defined. Done means the instrumentations report relevant values as metrics in addition to traces, with the scope agreed by maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100