MQ
Last updated on 27 March, 2023LogicMonitor currently has two DataSources for monitoring MQ:
- AWS_MQ_Broker
- AWS_MQ_StandbyBroker
AWS_MQ_Broker
Source: CloudWatch
Datapoints:
- burstBalance
- cpuUtilization
- currentConnectionsCount
- establishedConnectionsCount
- heapUsage
- inactiveDurableTopicSubscribersCount
- journalFilesForFastRecovery
- journalFilesForFullRecovery
- networkInBytes
- networkOutBytes
- openTransactionCount
- storePercentUsage
- totalConsumerCount
- totalMessageCount
- totalProducerCount
- volumeReadOps
- volumeWriteOps
Default Polling Interval: 5 minutes.
Additional Configuration Necessary?: No. This DataSource will automatically apply to and start collecting data for any MQ Broker resources discovered for your AWS Account.
AWS_MQ_StandbyBroker
Source: CloudWatch
Datapoints:
- burstBalance
- cpuUtilization
- currentConnectionsCount
- establishedConnectionsCount
- heapUsage
- inactiveDurableTopicSubscribersCount
- journalFilesForFastRecovery
- journalFilesForFullRecovery
- networkInBytes
- networkOutBytes
- openTransactionCount
- storePercentUsage
- totalConsumerCount
- totalMessageCount
- totalProducerCount
- volumeReadOps
- volumeWriteOps
Default Polling Interval: 5 minutes.
Additional Configuration Necessary?: No. This DataSource will automatically apply to and start collecting data for any MQ StandbyBroker resources discovered for your AWS Account.