Skip to content
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

Provide support for metrics through OpenTelemetry #2291

Closed
tomkerkhove opened this issue Nov 16, 2021 · 2 comments
Closed

Provide support for metrics through OpenTelemetry #2291

tomkerkhove opened this issue Nov 16, 2021 · 2 comments
Labels
feature All issues for new features that have been committed to needs-discussion stale-bot-ignore All issues that should not be automatically closed by our stale bot

Comments

@tomkerkhove
Copy link
Member

tomkerkhove commented Nov 16, 2021

Proposal

Provide support for metrics through OpenTelemetry which allows end-users to use the destination that they prefer.

image

Source: https://opentelemetry.io/docs/

Ideally, end-users can use the OTLP collector and take it from there.

Use-Case

Allows end-users to use the destination that they prefer instead of us having to implement every one of them.

We already support Prometheus, and HTTP add-on is adding support through kedacore/http-add-on#321, but this allows us to be more flexible.

Anything else?

Metrics in OpenTelemetry spec has just gone stable (https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md) but some pieces are still experimental so we should wait (https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/metrics)

Go support is in Alpha (https://opentelemetry.io/docs/go/#status-and-releases) but already has decent coverage (https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#metrics)

Long story short, already tracking for when it goes stable.

@stale
Copy link

stale bot commented Jan 15, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Jan 15, 2022
@tomkerkhove tomkerkhove added feature All issues for new features that have been committed to and removed feature-request All issues for new features that have not been committed to labels Jan 15, 2022
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Jan 15, 2022
@JorTurFer JorTurFer added the stale-bot-ignore All issues that should not be automatically closed by our stale bot label Jan 16, 2022
@tomkerkhove
Copy link
Member Author

Duplicate of #3078

@tomkerkhove tomkerkhove marked this as a duplicate of #3078 Sep 27, 2022
@tomkerkhove tomkerkhove closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature All issues for new features that have been committed to needs-discussion stale-bot-ignore All issues that should not be automatically closed by our stale bot
Projects
None yet
Development

No branches or pull requests

2 participants