Hi Gary and Justin,
thanks for your suggestions. I created the PR #3118[1] to add the new
command `check` to the Command Line utility. This command exposes some
checks for nodes and queues using the management API for most of them.
The checks have been implemented to be modular. Each user can comp
My recommendation would be to keep things simple. There isn't going to be
one test that will satisfy all use-cases.
It's worth noting that we already have lots of different ways to inspect a
lot of different data points on the broker via the management API. You can
access data about message counts
I imagine the equivalent of the oracle db query : "select * from
DUAL", ie: something that exercise the server.
A combination of queue produce and consume, on some existing queue or
on a temp queue for that purpose.
I guess an existing queue may be better b/c on production systems
queue creation m
I'm implementing a tool to determine whether the broker is in a healthy
state. There is a series of health checks that can be performed, starting
with the most basic and very rarely producing false positives, to
increasingly more comprehensive, intrusive, and opinionated that have a
higher probabil
