[
https://issues.apache.org/jira/browse/ARTEMIS-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248142#comment-17248142
]
Justin Bertram edited comment on ARTEMIS-2897 at 12/15/20, 1:42 AM:
--------------------------------------------------------------------
[Slow-consumer
detection|http://activemq.apache.org/components/artemis/documentation/latest/slow-consumers.html]
might be useful here.
I think that inspecting {{messagesAcknowledged}} might also work here as well.
For example, if {{messageCount}} > 0 and {{consumerCount}} > 0 but
{{messagesAcknowledged}} is stagnant then you likely have a stalled consumer.
This would work for clients with misconfigured message selectors as well as low
message volume destinations. Tools like Prometheus have a rich query language
that should be able to handle this kind of work.
If you're using JMX another possibility would be using the {{lastAckTimestamp}}
recently added to the [message
counters|https://activemq.apache.org/components/artemis/documentation/latest/management.html#message-counters].
If {{lastAckTimestamp}} is too old then you might have a stalled consumer.
was (Author: jbertram):
[Slow-consumer
detection|http://activemq.apache.org/components/artemis/documentation/latest/slow-consumers.html]
might be useful here.
I think that inspecting {{messagesAcknowledged}} might also work here as well.
For example, if {{messageCount}} > 0 and {{consumerCount}} > 0 but
{{messagesAcknowledged}} is stagnant then you likely have a stalled consumer.
This would work for clients with misconfigured message selectors as well as low
message volume destinations. Tools like Prometheus have a rich query language
that should be able to handle this kind of work.
If you're using JMX another possibility would be using the {{lastAckTimestamp}}
recently added to the [message
counters|activemq.apache.org/components/artemis/documentation/latest/management.html#message-counters].
If {{lastAckTimestamp}} is too old then you might have a stalled consumer.
> Metrics: a queue meter matching management.QueueControl.getFirstMessageAge()
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-2897
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2897
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.14.0
> Reporter: Petr Kuzel
> Priority: Major
>
> The micrometer-instrumentation of the broker queues lacks a gauge for the
> oldest message in the queue.
>
> Could you implement the "first.message.age.ms" meter for queues, please?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
