Amazon MQ monitoring

Dynatrace ingests metrics for multiple preselected namespaces, including Amazon MQ. You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.

Prerequisites

To enable monitoring for this service, you need

  • An Environment or Cluster ActiveGate version 1.197+
    Note: For role-based access (whether in a SaaS or Managed deployment), you need an Environment ActiveGate installed on an AWS EC2 host.
  • Dynatrace version 1.201+
  • An updated AWS monitoring policy to include the additional AWS services.

To update the AWS IAM policy, use the JSON below, containing the monitoring policy (permissions) for all supporting services.

If you don't want to add permissions to all services, and just select permissions for certain services, consult the table below. The table contains a set of permissions that are required for all services (All monitored Amazon services) and, for each supporting service, a list of optional permissions specific to that service.

Example of JSON policy for one single service.

In this example, from the complete list of permissions you need to select

  • "apigateway:GET" for Amazon API Gateway
  • "cloudwatch:GetMetricData", "cloudwatch:GetMetricStatistics", "cloudwatch:ListMetrics", "sts:GetCallerIdentity", "tag:GetResources", "tag:GetTagKeys", and "ec2:DescribeAvailabilityZones" for All monitored Amazon services.

Enable monitoring

To enable monitoring for this service, you first need to integrate Dynatrace with Amazon Web Services:

Add the service to monitoring

In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.

Cloud-service monitoring consumption

As of 2021, all cloud services consume Davis data units (DDUs). The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs).

Monitor resources based on tags

You can choose to monitor resources based on existing AWS tags, as Dynatrace automatically imports them from service instances. Nevertheless, the transition from AWS to Dynatrace tagging isn't supported for all AWS services. Expand the table below to see which supporting services are filtered by tagging.

To monitor resources based on tags

  1. In the Dynatrace menu, go to Settings > Cloud and virtualization > AWS and select Edit for the desired AWS instance.
  2. For Resources to be monitored, select Monitor resources selected by tags.
  3. Enter the Key and Value.
  4. Select Save.

Configure service metrics

Once you add a service, Dynatrace starts automatically collecting a suite of metrics for this particular service. These are recommended metrics.

Recommended metrics:

  • Are enabled by default
  • Can't be disabled
  • Can have recommended dimensions (enabled by default, can't be disabled)
  • Can have optional dimensions (disabled by default, can be enabled)

Apart from the recommended metrics, most services have the possibility of enabling optional metrics.

Optional metrics:

  • Can be added and configured manually

View service metrics

You can view the service metrics in your Dynatrace environment either on the custom device overview page or on your Dashboards page.

View metrics on the custom device overview page

To access the custom device overview page

  1. In the Dynatrace menu, go to Technologies and processes.
  2. Filter by service name and select the relevant custom device group.
  3. Once you select the custom device group, you're on the custom device group overview page.
  4. The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.

View metrics on your dashboard

After you add the service to monitoring, a preset dashboard containing all recommended metrics is automatically listed on your Dashboards page. To look for specific dashboards, filter by Preset and then by Name.
aws-presets
Note: For existing monitored services, you might need to resave your credentials for the preset dashboard to appear on the Dashboards page. To resave your credentials, go to Settings > Cloud and virtualization > AWS, select the desired AWS instance, and then select Save.

You can't make changes on a preset dashboard directly, but you can clone and edit it. To clone a dashboard, open the browse menu () and select Clone.
To remove a dashboard from the dashboards page, you can hide it. To hide a dashboard, open the browse menu () and select Hide.
Note: Hiding a dashboard doesn't affect other users. clone-hide-aws

To check the availability of preset dashboards for each AWS service, see the list below.

mqdash

Available metrics

Name Description Unit Statistics Dimensions Recommended
ConsumerCount The number of consumers subscribed to the destination Count Average Broker, Topic
ConsumerCount Count Average Broker, Queue
CpuCreditBalance The number of earned CPU credits that an instance has accrued since it was launched or started (including the number of launch credits) Count Average Broker ✔️
CpuUtilization The percentage of allocated Amazon EC2 compute units that the broker currently uses Percent Average Broker ✔️
CurrentConnectionsCount The current number of active connections on the current broker Count Average Broker ✔️
DequeueCount The number of messages acknowledged by consumers, per minute Count Average Broker, NetworkConnector, RemoteBroker
DequeueCount Count Average Broker, Topic
DequeueCount Count Average Broker, Queue
DispatchCount The number of messages sent to consumers, per minute Count Average Broker, Topic
DispatchCount Count Average Broker, Queue
EnqueueCount The number of messages sent to the destination, per minute Count Average Broker, NetworkConnector, RemoteBroker
EnqueueCount Count Average Broker, Topic
EnqueueCount Count Average Broker, Queue
EnqueueTime The end-to-end latency from when a message arrives at a broker until it is delivered to a consumer Milliseconds Multi Broker, Topic
EnqueueTime Milliseconds Multi Broker, Queue
EstablishedConnectionsCount The total number of connections, active and inactive, that have been established on the broker Count Average Broker
ExpiredCount The number of messages that couldn't be delivered because they expired, per minute Count Average Broker, Topic
ExpiredCount Count Average Broker, Queue
HeapUsage The percentage of the ActiveMQ JVM memory limit that the broker currently uses Percent Average Broker ✔️
InFlightCount The number of messages sent to consumers that have not been acknowledged Count Average Broker, Topic
InFlightCount Count Average Broker, Queue
InactiveDurableTopicSubscribersCount The number of inactive durable topic subscribers, up to a maximum of 2000 Count Average Broker
JobSchedulerStorePercentUsage The percentage of disk space used by the job scheduler store Percent Average Broker
JournalFilesForFastRecovery The number of journal files that will be replayed after a clean shutdown Count Average Broker
JournalFilesForFullRecovery The number of journal files that will be replayed after an unclean shutdown Count Average Broker
MemoryUsage The percentage of the memory limit that the destination currently uses. Percent Average Broker, Topic
MemoryUsage Percent Average Broker, Queue
NetworkIn The volume of incoming traffic for the broker Bytes Average Broker
NetworkIn Bytes Sum Broker ✔️
NetworkOut The volume of outgoing traffic for the broker Bytes Average Broker
NetworkOut Bytes Sum Broker ✔️
OpenTransactionCount The total number of transactions in progress Count Average Broker
ProducerCount The number of producers for the destination Count Average Broker, Topic
ProducerCount Count Average Broker, Queue
QueueSize The number of messages in the queue. This metric applies only to queues. Count Average Broker, Queue
ReceiveCount The number of messages that have been received from the remote broker for a duplex network connector Count Average Broker, NetworkConnector, RemoteBroker
StorePercentUsage The percent used by the storage limit. If this reaches 100, the broker will refuse messages. Percent Average Broker
TempPercentUsage The percentage of available temporary storage used by non-persistent messages Percent Average Broker
TotalConsumerCount The number of message consumers subscribed to destinations on the current broker Count Average Broker ✔️
TotalDequeueCount The total number of messages that have been consumed by clients Count Average Broker
TotalEnqueueCount The total number of messages that have been sent to the broker Count Average Broker
TotalMessageCount The number of messages stored on the broker Count Average Broker ✔️
TotalProducerCount The number of message producers active on destinations on the current broker Count Average Broker ✔️