-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add new calls to adopt status reporting for the prometheus receiver #27605
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I was looking around to see if there are any issues I can pickup. Is this still relevant? Looks like some things have changed since this issue was created.
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/prometheus
Is your feature request related to a problem? Please describe.
With the merging of open-telemetry/opentelemetry-collector#8169, we should begin moving over some components to start reporting. The prometheus receiver is very widely used and would be a great first candidate.
Describe the solution you'd like
Adhere to the ComponentStatus interface.
Describe alternatives you've considered
n/a
Additional context
I can take this on :)
The text was updated successfully, but these errors were encountered: