-
Notifications
You must be signed in to change notification settings - Fork 280
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
check_http: Optionally return content #1559
Comments
I know that I probably don't want to return long HTML page content, but a flag to also include the body text would be sweet and I can't really believe that this is not supported? |
Here's another example:
I will try to make a PR with an optional flag to return the content. |
towolf
added a commit
to towolf/monitoring-plugins
that referenced
this issue
Nov 9, 2018
This should help with figuring out ia problem at a glance when enabled for healthz endpoints on web APIs, for example. The content of the body can point to what the problem is and help with diagnostics. Fixes monitoring-plugins#1559
Thanks for merging. Here's an example where this is useful, Gitlab: Before
After
|
Now we just need a release ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using check_http on an API with a healthz endpoint, this is basically useless:
I'd like to see the content that the HTTP request response is returning. It's actually stating that an API on the internet that it is using is down. So I can't do anything and can ignore this problem.
The text was updated successfully, but these errors were encountered: