New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Feature: OpenTelemetry Metrics #251
Comments
@quest-bot stash 300 |
New Quest!A new Quest has been launched in @traceloop’s repo. Loot of 300 USD has been stashed in this issue to reward the solver! 🗡 Comment ⚔️ When you submit a PR, comment Questions? Check out the docs. |
@quest-bot embark |
@Humbertzhang has embarked on their Quest 🗡
Questions? Check out the docs. |
@quest-bot embark |
@hanchchch has embarked on their Quest. 🗡
Questions? Check out the docs. |
@quest-bot embark |
@naghost-dev has embarked on their Quest. 🗡
Questions? Check out the docs. |
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?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: