[
https://issues.apache.org/jira/browse/ARTEMIS-4579?focusedWorklogId=901115&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901115
]
ASF GitHub Bot logged work on ARTEMIS-4579:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/24 05:38
Start Date: 23/Jan/24 05:38
Worklog Time Spent: 10m
Work Description: jsmucr commented on PR #4752:
URL:
https://github.com/apache/activemq-artemis/pull/4752#issuecomment-1905325738
@jbertram Only by **very complicated** workarounds. I need to find out if
there's an old message in a queue that's been there for a while now, and I'm
not allowed to use DLQs for that, because it means a manual intervention on the
broker if processing fails too many times.
I know this method is heavy but so is our workflow here, which is pretty
much based on wasting resources in exchange for usability and easy maintenance.
:-)
I understand your point of view, I really do, but I also find Artemis to be
quite an advanced tool all by itself, and that if I slow it down by using a
method that is heavy on resources, it's entirely my fault as an operator.
Perhaps a page of documentation would be enough to get rid of responsibility
here.
Issue Time Tracking
-------------------
Worklog Id: (was: 901115)
Time Spent: 1.5h (was: 1h 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.32.0
>
> Time Spent: 1.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)
