We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We upgraded from Dropwizard 2.1 to 4.0. Now our monitoring fails to get details in case of any unhealthy healthcheck because then the HTTP status 500 is used. Previously it was possible to override this, but that change was only done in com.codahale.metrics.servlets.HealthCheckServlet, not in io.dropwizard.metrics.servlets.HealthCheckServlet which our application now uses.
The text was updated successfully, but these errors were encountered:
b116e89
joschi
Successfully merging a pull request may close this issue.
We upgraded from Dropwizard 2.1 to 4.0. Now our monitoring fails to get details in case of any unhealthy healthcheck because then the HTTP status 500 is used. Previously it was possible to override this, but that change was only done in com.codahale.metrics.servlets.HealthCheckServlet, not in io.dropwizard.metrics.servlets.HealthCheckServlet which our application now uses.
The text was updated successfully, but these errors were encountered: