Skip to content

AWS MQ ActiveMQ

Collect AWS MQ ActiveMQ monitoring data.

Configuration

Install Func

Enable hosted Func under Integration - Extensions in Guance. All prerequisites are installed automatically; proceed with script installation.

To deploy Func yourself, see Self-hosted Func Deployment

Enable the Script

Note: Prepare an AWS AK with the required permissions in advance. For simplicity, you can grant the global read-only policy ReadOnlyAccess.

Enable the Script in Hosted Func

  1. Log in to the Guance console.
  2. Open the Integration menu and select Cloud Account Management.
  3. Click Add Cloud Account, select AWS, and enter the required information. Skip this step if the cloud account is already configured.
  4. Click Test, then click Save if the test succeeds. If it fails, check the configuration and test again.
  5. In Cloud Account Management, locate the added cloud account and click it to open its details page.
  6. Click Integration on the cloud account details page. Under Not Installed, find AWS MQ ActiveMQ, click Install, and complete the installation in the dialog.

Enable the Script Manually

  1. Log in to the Func console, open Script Market, enter the Guance script market, and search for integration_aws_mq
  2. Click Install and enter AWS AK ID, AK Secret, and the account name.
  3. Click Deploy Startup Script. The system automatically creates a Startup script set and configures the startup script.
  4. After activation, find the trigger under Management / Automatic Trigger Configuration. Click Execute to run it immediately without waiting for the schedule. After a short wait, check the task execution records and logs.

For manual deployment, use the startup script generated by the AWS MQ ActiveMQ Cloud Collector.

Verification

  1. Under Management / Automatic Trigger Configuration, confirm that the task has a trigger configured. Check the task records and logs for errors.
  2. In Guance, check for asset information under Infrastructure / Custom.
  3. In Guance, check Metrics for the corresponding monitoring data.

Metrics

The measurement is aws_AWS/AmazonMQ.

MetricName MetricDescribe Dimensions Unit
HeapUsage_Average JVM heap memory usage (average) Broker percent
JournalFilesForFastRecovery_Average Journal files replayed for recovery after a normal shutdown (average) Broker Count
JournalFilesForFullRecovery_Average Journal files replayed for recovery after an abnormal shutdown (average) Broker Count
NetworkIn_Average Data received by the broker (average) Broker B
NetworkOut_Average Data sent by the broker (average) Broker B
StorePercentUsage_Average Persistent storage usage (average) Broker percent
TotalConsumerCount_Average Total consumers across all broker destinations (average) Broker Count
ConsumerCount_Average Consumers for the destination (average) Broker, Queue or Broker, Topic Count
ConsumerCount_Maximum Consumers for the destination (maximum) Broker, Queue or Broker, Topic Count
DequeueCount_Average Messages acknowledged by consumers per minute (average) Broker, Queue or Broker, Topic Count
DispatchCount_Average Messages dispatched to consumers per minute (average) Broker, Queue or Broker, Topic Count
EnqueueCount_Average Messages sent to the destination per minute (average) Broker, Queue or Broker, Topic Count
EnqueueTime_Average Latency from arrival at the broker to delivery to the consumer (average) Broker, Queue or Broker, Topic ms
ExpiredCount_Average Expired, undelivered messages per minute (average) Broker, Queue or Broker, Topic Count
MemoryUsage_Average Memory usage for the destination (average) Broker, Queue or Broker, Topic percent
ProducerCount_Average Producers for the destination (average) Broker, Queue or Broker, Topic Count
ProducerCount_Maximum Producers for the destination (maximum) Broker, Queue or Broker, Topic Count
QueueSize_Average Messages in the queue (average) Broker, Queue Count

Feedback

Is this page helpful?