/healthcheck URI just returns a 200/ok for cloud service monitoring #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a URI under the prefix path
/healthcheckthat merely returns 200/ok without invoking the URI factory. It is to be used by monitoring services that are only concerned with whether Node is responding to inputs but need not form a redirect.e.g.
http://localhost:1337/healthcheckifuriPathPrefix == '/'http://localhost:1337/janus/healthcheckifuriPathPrefix == '/janus'It might be more ideal for this to be an implementation detail in janus-deploy instead, but the router isn't expose there to add additional routes at this time.