Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

Take error scenarios into account in aliveness test #856

Merged
merged 4 commits into from
Oct 16, 2020

Conversation

lukebakken
Copy link
Contributor

Fixes #855

For instance, if `message-ttl` is set to `0`, there will never be a
message in the queue for the check. In this case, return `503`

Fixes #855
@lukebakken lukebakken self-assigned this Oct 13, 2020
@lukebakken lukebakken marked this pull request as draft October 13, 2020 17:00
@lukebakken lukebakken marked this pull request as ready for review October 14, 2020 13:06
@lukebakken
Copy link
Contributor Author

@michaelklishin all set for review.

@michaelklishin michaelklishin merged commit 6b62271 into master Oct 16, 2020
@michaelklishin michaelklishin deleted the rabbitmq-management-855 branch October 16, 2020 02:43
michaelklishin added a commit that referenced this pull request Oct 16, 2020
Take error scenarios into account in aliveness test

(cherry picked from commit 6b62271)
@michaelklishin
Copy link
Member

Backported to v3.8.x.

michaelklishin added a commit that referenced this pull request Oct 19, 2020
 * Remove documentation to the now deprecated One True Health Check™.
   It is too intrusive and too prone to false positives to recommend.
 * Aliveness test is also a health check, and will respond with a 200
   or 503 as of #856
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

API request to aliveness-test when message-ttl is 0 results in a 500
2 participants