Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 31 Oct 2013 05:26:26 +0000 (UTC)
From: "Matt Pavlovich (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12634816.1362148381975.9686.1383197186647@arcas>
In-Reply-To: <JIRA.12634816.1362148381975@arcas>
References: <JIRA.12634816.1362148381975@arcas>
Subject: [jira] [Commented] (AMQ-4354) Persist JMX statistics so they
 survive a restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809941#comment-13809941 ] 

Matt Pavlovich commented on AMQ-4354:
-------------------------------------

Consistency definitely gets over a big hurdle, but I think we still have a problem of how to show lifetime metrics through the system.  

Broker enqueues 500 messages.. dequeues 250.. >> restart <<.. broker comes back up and shows 250 messages enqueued. Monitoring tools will only be able to provide "as-is", instead of absolute values. The total message traffic numbers driving things like capacity planning over time. If the thought process would be to move that tracking to the monitoring tools, that'd work, but we'd need a way to readAndReset() statistics in a somewhat atomic way to preserve correct values.

Thoughts?

> Persist JMX statistics so they survive a restart
> ------------------------------------------------
>
>                 Key: AMQ-4354
>                 URL: https://issues.apache.org/jira/browse/AMQ-4354
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: JMX
>    Affects Versions: 5.8.0
>         Environment: All
>            Reporter: Matt Pavlovich
>
> It would be really handy if JMX statistics survived a restart. 


--
This message was sent by Atlassian JIRA
(v6.1#6144)