This is what is displayed for a health check that is validates whether an endpoint returns 200:
No message is returned so health checks defaults to displaying the exception message. This doesn't look user friendly.
The health check should have a failure message like "Request to xxx timed out" if there is a timeout. Or "Request to xxx returned yyy status code".
We should do the same for other built-in checks: polling an endpoint for 200, a database for a good response, or message queue, etc. The failure message message should explain what has gone wrong in a friendly way. More detail from the exception message is still available from the exception details if the user wants to view it.
davidfowl
commented
1 month ago
Is there an existing issue for this?
Describe the bug
This is what is displayed for a health check that is validates whether an endpoint returns 200:
No message is returned so health checks defaults to displaying the exception message. This doesn't look user friendly.
The health check should have a failure message like "Request to xxx timed out" if there is a timeout. Or "Request to xxx returned yyy status code".
We should do the same for other built-in checks: polling an endpoint for 200, a database for a good response, or message queue, etc. The failure message message should explain what has gone wrong in a friendly way. More detail from the exception message is still available from the exception details if the user wants to view it.
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
No response