You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/03/07 16:46:00 UTC

[jira] [Work logged] (ARTEMIS-4579) Add the *FirstMessage* API for scheduled messages

     [ https://issues.apache.org/jira/browse/ARTEMIS-4579?focusedWorklogId=908807&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-908807 ]

ASF GitHub Bot logged work on ARTEMIS-4579:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Mar/24 16:45
            Start Date: 07/Mar/24 16:45
    Worklog Time Spent: 10m 
      Work Description: jbertram merged PR #4752:
URL: https://github.com/apache/activemq-artemis/pull/4752




Issue Time Tracking
-------------------

    Worklog Id:     (was: 908807)
    Time Spent: 3h 40m  (was: 3.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.33.0
>
>          Time Spent: 3h 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)