[ https://issues.apache.org/jira/browse/ARTEMIS-4579?focusedWorklogId=901146&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901146 ]
ASF GitHub Bot logged work on ARTEMIS-4579: ------------------------------------------- Author: ASF GitHub Bot Created on: 23/Jan/24 09:04 Start Date: 23/Jan/24 09:04 Worklog Time Spent: 10m Work Description: jsmucr commented on PR #4752: URL: https://github.com/apache/activemq-artemis/pull/4752#issuecomment-1905601738 I've added a `MessageReferenceImpl` leak test. Issue Time Tracking ------------------- Worklog Id: (was: 901146) Time Spent: 1h 40m (was: 1.5h) > 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: 1h 40m > 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)