The UI handles the case where the 2 fields are not present.
This can happen in a mixed-version cluster, where a node
of a previous version returns records without the fields.
The UI uses default values (active = true, activity status = up),
which is valid as the consumers of the node are "standalone"
consumers (not part of a group).
References #3753
This is an important metric to keep track of and be aware (maybe even
alert on) when consumers fall behind consuming stream messages. While
they should be able to catch up, if they fall behind too much and the
stream gets truncated, they may miss on messages.
This is something that we want to expose via Prometheus metrics as well,
but we've started closer to the core, CLI & Management.
This should be merged as soon as it passes CI, we shouldn't wait on the
Prometheus changes - they can come later.
Pair: @kjnilsson
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Depending on whether the "owner" of the consumer is a channel (for AMQP
consumers) or a connection (for stream consumers) and whether the stream
management plugin is enabled or not. The link will lead to the channel
page, the connection page, or the stream connection page.
Diana Parra Corbacho
David Ansari
Michael Klishin
Arnaud Cogoluègnes
Gabriele Santomaggio
Gerhard Lazu