-
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
Use the new scrape config endpoint for the prometheus receiver #14464
Use the new scrape config endpoint for the prometheus receiver #14464
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple general questions I have.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more followup questions for my understanding.
…contrib into 1106-use-scrape-configs-endpoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM otherwise
…telemetry#14464) This fixes issue 1106 in the operator which relates to the collector failing to get scrape config jobs from the target allocator. Before this is merged this pr needs to be merged which adds this new endpoint.
Description:
This PR fixes issue 1106 in the operator which relates to the collector failing to get scrape config jobs from the target allocator. Before this is merged this pr needs to be merged which adds this new endpoint.
Link to tracking Issue:
open-telemetry/opentelemetry-operator#1106
Testing:
This was tested by running a custom collector in a kubernetes cluster with the changes in the operator and target allocator. You can see the collector pulling expected jobs from the target allocator here.
Documentation:
Closes #14597