-
Notifications
You must be signed in to change notification settings - Fork 420
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
target allocator missing default value for scrape settings for prometheusCR #1106
Comments
Thanks for reporting this! I can look in to the fix here. |
Alright, I began looking in to this and was able to reproduce this in my development cluster. The issue appears to be that the target allocator returns I think the fix will require two changes:
I can take both fixes. For the target allocator PR, we are going to need to include some of this information (relabel_config) in the job we set. I believe this is a good opportunity for us to change some of the internal models of the TA which currently make it more difficult to bubble up this information via http. Doing so will set us up for success for #1064 |
Repo with reproducer: https://github.com/seankhliao/testrepo0032
Target Allocator: 0.1.0 and main
Operator: 0.60.0
Collector: 0.60.0
When creating jobs/scrape targets from ServiceMonitors, the target allocator doesn't produce values for:
__scrape_interval__
__scrape_timeout__
__scheme__
__metrics_path__
__param_*
When the prometheusreceiver reads the HTTP SD configs, it produces errors like the below for
__scrape_*
,"target": "//a.b.c.d:port", "error": "Get \"//a.b.c.d:port\": unsupported protocol scheme \"\""
for missing scheme, and 404s (or other invalid input) for missing paths:Initial report in slack: https://cloud-native.slack.com/archives/C033BJ8BASU/p1663327567933649
The text was updated successfully, but these errors were encountered: