[
https://issues.apache.org/jira/browse/ARTEMIS-4579?focusedWorklogId=902497&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-902497
]
ASF GitHub Bot logged work on ARTEMIS-4579:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jan/24 05:31
Start Date: 30/Jan/24 05:31
Worklog Time Spent: 10m
Work Description: jsmucr commented on PR #4752:
URL:
https://github.com/apache/activemq-artemis/pull/4752#issuecomment-1916108015
> There **is** a management method which shows details of in-flight
messages. It's called `listDeliveringMessagesAsJSON`. That operation, combined
with `listScheduledMessagesAsJSON`, should give you everything you need, right?
It should but there are two things I don't like about this approach:
* The output requires some postprocessing, and therefore it is fairly
unusable from the GUI.
* There's nothing that stops the broker from transforming and exporting
significant amount of data when all I need is one number.
> I still feel like there's a better solution here
Again, I'm all ears. The bigger picture is that fast response time is a
must, or I'm stopping a car assembly line (literally), so every help is much
appreciated. :-)
Issue Time Tracking
-------------------
Worklog Id: (was: 902497)
Time Spent: 3.5h (was: 3h 20m)
> Add the *FirstMessage* API for scheduled messages
> -------------------------------------------------
>
> Key: ARTEMIS-4579
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4579
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.31.2
> Reporter: Jan Šmucr
> Priority: Major
> Fix For: 2.33.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Alerting on issues with messages not being received properly for a period of
> time is an uneasy task. We use the {{getFirstMessageAge()}} command to
> trigger alerts in Zabbix, and it works as long as there are no consumers.
> But this approach fails when there are consumers repeatedly failing to
> receive a message. That message is getting scheduled for redelivery over and
> over, and even though there still is an old message in the queue to be
> reported, it's no longer visible via {{getFirstMessage*()}} API.
> The goal here is to add a set of functions working with messages scheduled
> for delivery:
> {noformat}
> getFirstScheduledMessageAsJSON()
> getFirstScheduledMessageTimestamp()
> getFirstScheduledMessageAge()
> {noformat}
> It may be not the most effective approach but it's quite a convenient one,
> especially when monitoring a wide set of queues, each with its own set of
> alerts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
