HornetQ extension

  • Latest Dynatrace
  • Extension
  • Published Oct 27, 2025

Automatic and intelligent observability for HornetQ with trace and metric insights.

Get started

Overview

With Dynatrace, you can get observability for HornetQ without touching any code, thanks to automatic monitoring.

Seamless end-to-end traces for connected producer and consumer services allow you to diagnose anomalies and pinpoint the root cause of the broken code before your customers are affected.

Comprehensive metrics give you insight into the health and performance of your HornetQ brokers, queues, and topics. Events point you to critical anomalies, reducing the mean time to repair.

Use cases

  • Capture every message across tiers without blind spots.
  • Troubleshoot asynchronous service problems across your stack proactively.
  • Improve the performance of your producer and consumer services end-to-end.
  • Prevent message processing anomalies to reduce the mean time to repair.
  • Monitor the health and performance of all your brokers, topics, and queues.

Requirements

Messaging clients (applications)

To get trace insight:

To get log insight:

Messaging servers (brokers)

HornetQ broker must run on a supported Linux or Windows operating system.

To get metric insight:

  1. Install OneAgent on the virtual machine or server of your HornetQ broker. Ensure your HornetQ broker process is monitored by OneAgent. The extension does not support gathering metrics from the client-side.
  2. Activate the OneAgent feature Java Metric Extensions 2.0 (JMX).

Activation and setup

  1. Find the extension in Dynatrace Hub to and add it to your environment.
  2. Add a monitoring configuration.

Details

The extension uses the JMX datasource to capture MBeans on your HornetQ process and ingest them in Dynatrace as metrics. It also includes a dashboard called HornetQ JMX Oveview for easy access and monitoring of your HornetQ JMX metrics and their custom topology, which includes the topics and queues of your HornetQ, along with the relevant custom screens for them.

Feature sets

When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.

In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.

All metrics that aren't categorized into any feature set are considered to be the default and are always reported.

A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.

topic-metrics
Metric nameMetric keyDescription
Message counthornetq.topic.messageCount
Durable message counthornetq.topic.durableMessageCount
Durable subscription counthornetq.topic.durableSubscriptionCount
Non durable subscription counthornetq.topic.nonDurableSubscriptionCount
Non durable message counthornetq.topic.nonDurableMessageCount
Subscription counthornetq.topic.subscriptionCount
Delivering counthornetq.topic.deliveringCount
hornetq.topic.messagesAdded
server-metrics
Metric nameMetric keyDescription
Connection counthornetq.server.connectionCount
queue-metrics
Metric nameMetric keyDescription
Consumer counthornetq.queue.consumerCount
Message counthornetq.queue.messageCount
Scheduled counthornetq.queue.scheduledCount
Delivering counthornetq.queue.deliveringCount
hornetq.queue.messagesAdded
Related tags
ApplicationJMXMessage queueApacheApplication ObservabilityMessage QueuesMessage Queues