docs(exposition): clarify required Content-type header for scrapes #2772
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
Signed-off-by: Lukas Juozas Janušaitis <lukas.janusaitis@hostinger.com>
LukoJy3D
force-pushed
the
docs/exposition/clarify_required_content_type_for_scrapes
branch
from
2c77a01 to
4b70e1b
Compare
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.
In prometheus/prometheus#16155, it was suggested to clarify it in exposition formats.
While writing it, I feel that some aspects overlap with those mentioned in https://prometheus.io/docs/instrumenting/content_negotiation/. Therefore, it may be sufficient to mention it in the migration guide, but I will give this a try.