[
https://issues.apache.org/jira/browse/JAMES-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628009#comment-17628009
]
ouvtam commented on JAMES-3841:
-------------------------------
Here some exemplary log metrics:
{code:java}
22:50:25.412 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.averageEnqueueTime, value=1.904904904904905
22:50:25.415 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.consumerCount, value=6
22:50:25.416 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.dequeueCount, value=0
22:50:25.416 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.dispatchCount, value=823
22:50:25.416 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.enqueueCount, value=826
22:50:25.416 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.expiredCount, value=0
22:50:25.416 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.inflightCount, value=823
22:50:25.416 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.lastUpdate, value=1667429416627
22:50:25.417 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.maxEnqueueTime, value=30.0
22:50:25.417 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.memoryLimit, value=1073741824
22:50:25.417 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.memoryPercentUsage, value=0
22:50:25.417 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.memoryUsage, value=0
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.messagesCached, value=0
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.minEnqueueTime, value=1.0
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.producerCount, value=3
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.size, value=0
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.storeLimit, value=24797315144
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.storePercentUsage, value=0
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.storeUsage, value=86610
22:50:25.418 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.tempLimit, value=24797302784
22:50:25.423 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.tempPercentUsage, value=0
22:50:25.424 [DEBUG] o.a.j.metrics - type=GAUGE,
name=ActiveMQ.Statistics.Broker.tempUsage, value=0{code}
> ActiveMQ: Collect statistics and publish metrics
> ------------------------------------------------
>
> Key: JAMES-3841
> URL: https://issues.apache.org/jira/browse/JAMES-3841
> Project: James Server
> Issue Type: Improvement
> Components: Queue
> Reporter: ouvtam
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, only some James metrics are available for ActiveMQ which are
> exposed in WebAdmin. Namely, enqueuedMail and dequeuedMail for each
> registered queue (i.e. spool and outgoing). Some ActiveMQ broker stats
> (memoryUsage, memoryLimit, storeUsage, storeLimit, maxEnqueueTime, etc.) are
> currently not available.
> According to [https://activemq.apache.org/statisticsplugin.html] ActiveMQ
> Metrics can be obtained through subscription or by polling regularly. At the
> moment the statistics plugin is only used to get the size of a queue.
> I propose to poll ActiveMQ statistics via ActiveMQHealthCheck and publish
> those as metrics. Currently, the health check creates a session and checks if
> no exception occurred.
> What do you think?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
