fix: set fallback_scrape_protocol to enable scraping by prometheus 3.x #417
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix the scraping error "Failed to determine correct type of scrape target." of the prometheus container by setting a fallback_scrape_protocol
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The prometheus container runned with the docker-compose.yml was showing the following error:
msg="Failed to determine correct type of scrape target." component="scrape manager" scrape_pool=scaphandre target=http://scaphandre:8080/metrics content_type="" fallback_media_type="" err="non-compliant scrape target sending blank Content-Type and no fallback_scrape_protocol specified for target"This was due to the fact that since version 3.x, prometheus needs to read a Content-Type alongside the metrics that specifies the scraping protocol to be used.
Adding the fallback_scrape_protocol fixes the problem but it probably would be a good idea to add a
Content-Typetoo.