Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

Health check logging levels based on error #282

Closed
joakime opened this issue Jun 8, 2016 · 1 comment
Closed

Health check logging levels based on error #282

joakime opened this issue Jun 8, 2016 · 1 comment
Assignees
@joakime
Milestone
async-support

Comments

@joakime
Copy link

joakime commented Jun 8, 2016

As a result of comment from @aozarov from Issue #231, we should alter the logging levels based on If the Health Check results in 200, it should be a DEBUG/FINE level event, and all other results should be a higher level.

I favor WARN for non-200 results.
@joakime joakime self-assigned this Jun 8, 2016
@joakime joakime modified the milestone: async-support Jun 8, 2016
@gregw gregw mentioned this issue Sep 8, 2016
Closed
@gregw
Copy link
Contributor

gregw commented Sep 8, 2016

obsoleted by GoogleCloudPlatform/jetty-runtime#4

@gregw gregw closed this as completed Sep 8, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@joakime joakime

Labels
None yet
Projects
None yet
Milestone
async-support
Development

No branches or pull requests
2 participants
@gregw @joakime