Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upScrape target returns Empty body/Content-Lenght: 0, but no target error is raised #4937
Comments
This comment has been minimized.
This comment has been minimized.
|
An empty result is valid. OpenMetrics handles this. Dupe of #1169 |
brian-brazil
closed this
Nov 30, 2018
This comment has been minimized.
This comment has been minimized.
|
@brian-brazil sorry for the noise. I just couldn't find any issue that would match this description. Thanks. |
This comment has been minimized.
This comment has been minimized.
|
No problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zstyblik commentedNov 30, 2018
Proposal
Prometheus should raise/show error for targets which return either empty body or
Content-Lenght: 0. Such condition doesn't seem like a valid state to me. Also, it'd help to identify targets which don't produce metrics for one reason or another(I guess counter to this is "add alert rule which is going to check whether metrics X is present").I remember I had to deal with validation error due to missing
\nat the end of metrics list, but that seems to be gone now. Could it be regression? Could it be a new bug? It could be a newBug Report
What did you do?
Hooked up Prometheus to consul. However, one of the scrape targets returns 200 OK, empty body and
Content-Lenght: 0due to bug in the code. However, this is not related to consul as the same can be observed with static targets as well.What did you expect to see?
Scrape target down/scrape error.
What did you see instead? Under which circumstances?
Target is being reported as UP, no errors are being show in Web UI.
Environment
System information:
Prometheus version:
Prometheus configuration file: