HornetQ Monitoring: Difference between revisions
| (4 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[WildFly_Monitoring#Metrics|WildFly Monitoring]] | * [[WildFly_Monitoring#Metrics|WildFly Monitoring]] | ||
=Relevance= | |||
* EAP 6.4.10 | |||
=JMX Monitoring= | =JMX Monitoring= | ||
| Line 9: | Line 13: | ||
==Destinations== | ==Destinations== | ||
All deployed JMS destination, Dead Letter Queues and Expiry Queues can be monitored over JMX. The deployed destination ObjectName pattern is: | |||
<pre> | |||
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=<queue-name> | |||
</pre> | |||
Dead Letter Queue ObjectName: | |||
<pre> | |||
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=DLQ | |||
</pre> | |||
ExpiryQueue ObjectName: | |||
<pre> | |||
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=ExpiryQueue | |||
</pre> | |||
===JMX Attributes=== | ===JMX Attributes=== | ||
==== | ====messageCount==== | ||
For clustered destinations, 'messageCount' refers to the number of messages stored in the ''local queue''. It is not a cluster-wide metric. The total number of messages stored by the clustered destination can be obtained by adding 'messageCount' values across all nodes. | |||
====deliveringCount==== | ====deliveringCount==== | ||
==== | For clustered destinations, 'deliveringCount' refers to the ''local queue''. It is not a cluster-wide metric. | ||
====scheduledCount==== | |||
For clustered destinations, 'scheduledCount' refers to the ''local queue''. It is not a cluster-wide metric. | |||
====messageAdded==== | ====messageAdded==== | ||
==== | For clustered destinations, 'messageAdded' refers to the ''local queue''. It is not a cluster-wide metric. | ||
====consumerCount==== | |||
For clustered destinations, 'consumerCount' refers to the ''local queue''. It is not a cluster-wide metric. | |||
The number of JMS consumers currently associated and consuming messages from this destination. | |||
====entries==== | |||
===JMX Operations=== | ===JMX Operations=== | ||
Latest revision as of 21:29, 1 June 2017
Internal
Relevance
- EAP 6.4.10
JMX Monitoring
jboss.as:subsystem=messaging,hornetq-server=default
Destinations
All deployed JMS destination, Dead Letter Queues and Expiry Queues can be monitored over JMX. The deployed destination ObjectName pattern is:
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=<queue-name>
Dead Letter Queue ObjectName:
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=DLQ
ExpiryQueue ObjectName:
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=ExpiryQueue
JMX Attributes
messageCount
For clustered destinations, 'messageCount' refers to the number of messages stored in the local queue. It is not a cluster-wide metric. The total number of messages stored by the clustered destination can be obtained by adding 'messageCount' values across all nodes.
deliveringCount
For clustered destinations, 'deliveringCount' refers to the local queue. It is not a cluster-wide metric.
scheduledCount
For clustered destinations, 'scheduledCount' refers to the local queue. It is not a cluster-wide metric.
messageAdded
For clustered destinations, 'messageAdded' refers to the local queue. It is not a cluster-wide metric.
consumerCount
For clustered destinations, 'consumerCount' refers to the local queue. It is not a cluster-wide metric.
The number of JMS consumers currently associated and consuming messages from this destination.