Add health check which doesn't go upstream #179
Closed
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 addresses a problem we saw with having a TCP 'socket open' health check for amqproxy (e.g. in a k8s environment). If debug was enabled then we would see socket EOF errors, as amqproxy tries to read from the client.
This health check is specifically for amqproxy, and not testing the upstream connection (we could use an AMQP heartbeat frame for that).
AMQP9999
only.HEALTHOK
and closes the connection.