rabbitmqctl node_health_check and its HTTP API counterpart are DEPRECATED

162 views
Skip to first unread message

Anthony Mastrean

unread,
Oct 19, 2020, 3:03:38 PM10/19/20
to rabbitmq-users
It seems like running the Stage 6 health check, directly from the docs, returns the deprecation warning for the previous health check command. Is this intentional? Is it actually `node_health_check` that's deprecated, no matter how you run it?

rabbitmq-diagnostics -q node_health_check 


The warning, for reference:

[warning] <0.904.0> rabbitmqctl node_health_check and its HTTP API counterpart are DEPRECATED.

Michael Klishin

unread,
Oct 20, 2020, 12:20:45 AM10/20/20
to rabbitmq-users
This is intentional. See [1][2] for a list of modern health checks.
As of 3.8.10, they will be exposed as HTTP API endpoints as well.

2. rabbitmq-diagnostics help

Michael Klishin

unread,
Oct 20, 2020, 12:29:06 AM10/20/20
to rabbitmq-users
I have removed stage 6 from the docs (yet to go live). In an environment with a fairly small (say, a few 100s)
queues and connections you can achieve something similar by enabling per-object metric reporting [1]
and configuring an alert on certain per-object metrics (which metric and threshold you pick is up to you).

Anthony Mastrean

unread,
Oct 20, 2020, 10:14:19 AM10/20/20
to rabbitmq-users
Thank you!
Reply all
Reply to author
Forward
0 new messages