[rabbitmq-discuss] API aliveness test

James Carr james.r.carr at gmail.com
Fri Aug 12 00:22:12 BST 2011

In our monitoring that we have hooked up we check for the JSON
response and just wrap it in a try catch, raising an error if an
exception is thrown or status is not "ok"


On Thu, Aug 11, 2011 at 4:43 PM, Jason J. W. Williams
<jasonjwwilliams at gmail.com> wrote:
> Hi,
> The documentation for the API aliveness-test call
> (/api/aliveness-test/<vhost>) defines the success result
> ({"status":"ok"}), but not the failure results. When I use
> "rabbitmqctl stop_app" to simulate a failure, I get fairly ugly
> traceback returned over HTTP (https://gist.github.com/1140707) that'll
> crash the JSON parser. So should I just do a string match for
> {"status": "ok"} (or HTTP error code match) and consider any other
> return a failure, or are there JSON-friendly error outputs as well?
> Thank you in advance.
> -J
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list