You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A similar issue for flow mode has been raised in #5136 and fixed in #5335
However, it seems that for static mode agent there is still no way to configure EnableProtobufNegotiation on prometheus.
This is needed for agent to be able to scrape native histogram. You need this turned on for prometheus to be able to send correct header and request protobuf. See src here.
Steps to reproduce
no such option in static/config/config.go
System information
No response
Software version
No response
Configuration
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Reimirno
changed the title
Prometheus native histograms are scraped in static mode
Prometheus native histograms are NOT scraped in static mode
Oct 17, 2024
This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
What's wrong?
A similar issue for flow mode has been raised in #5136 and fixed in #5335
However, it seems that for static mode agent there is still no way to configure EnableProtobufNegotiation on prometheus.
This is needed for agent to be able to scrape native histogram. You need this turned on for prometheus to be able to send correct header and request protobuf. See src here.
Steps to reproduce
no such option in
static/config/config.go
System information
No response
Software version
No response
Configuration
No response
Logs
No response
The text was updated successfully, but these errors were encountered: