TIBCO EMS extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Gain automatic and intelligent observability with trace and metric insights.
Monitor TIBCO EMS brokers, queues, and topics to detect issues and optimize performance.
Get started
Overview
With Dynatrace, gain code-free observability into TIBCO EMS through automatic monitoring, seamless end-to-end traces, and comprehensive metrics. Diagnose anomalies, pinpoint root causes, and reduce mean time to repair with intelligent event detection.
The TIBCO EMS extension detects multiple EMS instances, connects with or without SSL, and collects health and performance data from brokers, queues, and topics. You can filter entities with rules, define custom alerts (e.g., for queue buildup), and view a custom topology linked to SmartScape, with dedicated screens for each entity.
The included TIBCO EMS Overview dashboard lets you navigate all created entities. Additional sections appear in monitored hosts and process group instances for broker navigation—ensure new screens are enabled to access them.
Metrics, prefixed with EMS2, are available in the Data Explorer, and Feature Sets allow control over which metrics are monitored.
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:
- Install OneAgent on the virtual machine or server of your messaging clients (applications).
- Set up Dynatrace on Kubernetes or OpenShift for your messaging client (application) workloads.
To get log insight:
Messaging servers (brokers)
Prerequisites:
- TIBCO EMS broker 8.x or higher on a supported Linux or Windows operating system.
- OneAgent version 1.256+
- Dynatrace version 1.309+
- The
dtuseraccount must be able to executetibemsadmin, usually installed underTIBCO_HOME/bin. - A monitoring account must be created with sufficient privileges to run
showcommands undertibemsadmin. - Statistics must be enabled inside TIBCO EMS.
- If using SSL, provide a valid certificate so the extension can connect.
To get metric insight:
- Install OneAgent on the virtual machine or server of your TIBCO EMS broker process.
- Ensure your TIBCO EMS broker process is monitored.
- Select Add to environment to configure the extension:
- User: Internal TIBCO account with sufficient privileges to run
tibemsadmincommands. - Password: The user password.
- Avoid auto discovering instances and ports: Enable this flag to indicate the path and executable for
tibemsadminand ignore auto discovery. - Instances to monitor: List of instances to monitor if auto discovery is disabled.
- Use 64bit version: Use
tibemsadmin64as executable instead of onlytibemsadmin. - Timeout: How long the extension will wait for a response from
tibemsadmin. - Secure Connection: Select
nofor TCP oryesfor SSL. Ensure the correct listener is enabled. - Capture System Queues: Select
yesto capture System Queues. - Monitoring Rules: Set of rules that will filter in or out the queues or topics based on their names.
- User: Internal TIBCO account with sufficient privileges to run
- Open the TIBCO EMS Overview dashboard.
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.
TopicRateMetrics
| Metric name | Metric key | Description |
|---|---|---|
| Topic outbound message size rate | EMS2.TopicOutboundMsgSizeRate | Rate of messages removed from the topic by size |
| Topic outbound message rate | EMS2.TopicOutboundMsgRate | Rate of messages removed from the topic |
| Topic inbound message size rate | EMS2.TopicInboundMsgSizeRate | Rate of messages coming in to the topic by size |
| Topic inbound message rate | EMS2.TopicInboundMsgRate | Rate of messages coming in to the topic |
QueueMetrics
| Metric name | Metric key | Description |
|---|---|---|
| Queue receiver count | EMS2.QueueReceivers | Number of receivers |
| Queue Depth | EMS2.QueueDepth | Number of messages pending in queue |
| Queue pending message size | EMS2.QueueMsgSize | Size of messages pending in queue |
| Queue inbound total messages | EMS2.QueueInboundMsgTotal.count | Total number of incoming messages |
| Queue outbound total messages | EMS2.QueueOutboundMsgTotal.count | Total number of outbound messages |
TopicMetrics
| Metric name | Metric key | Description |
|---|---|---|
| Topic message depth | EMS2.TopicMsgDepth | Number of messages pending in topic |
| Topic message Size | EMS2.TopicMsgSize | Size of the messages pending in topic |
DurableMetrics
| Metric name | Metric key | Description |
|---|---|---|
| Pending messages | EMS2.DurablePendingMessages | Number of messages pending for this durable |
| Pending messages size | EMS2.DurablePendingSize | Total size of the messages pending for this durable |
BrokerMetrics
| Metric name | Metric key | Description |
|---|---|---|
| Inbound message count rate | EMS2.BrokerInboundMsgCountRate | Rate of inbound messages |
| Outbound message count rate | EMS2.BrokerOutboundMsgCountRate | Rate of outbound messages |
| Topics count | EMS2.BrokerTopicCount | Number of topics |
| Queues count | EMS2.BrokerQueueCount | Number of queues |
| Clients count | EMS2.BrokerClientCount | Number of clients |
| Sessions count | EMS2.BrokerSessionCount | Number of sessions |
| Producers count | EMS2.BrokerProducerCount | Number of producers |
| Consumers count | EMS2.BrokerConsumerCount | Number of consumers |
| Durables count | EMS2.BrokerDurableCount | Number of durables |
| Pending messages count | EMS2.BrokerPendingMsgCount | Number of pending messages |
| Pending messages size | EMS2.BrokerPendingMsgSize | Size of all pending messages |
| Memory usage | EMS2.BrokerMemoryUsage | — |
| Memory usage in KB | EMS2.BrokerMemoryUsageKB | — |
| Memory pooled | EMS2.BrokerMemoryPooled | — |
| Synchronous storage | EMS2.BrokerSynchronousStorage | — |
| Async storage | EMS2.BrokerAsyncStorage | — |
| Inbound message size rate | EMS2.BrokerInboundMsgSizeRate | Rate of inbound messages by size |
| Outbound message size rate | EMS2.BrokerOutboundMsgSizeRate | Rate of outbound messages by size |
| Storage read size rate | EMS2.BrokerStorageReadSizeRate | — |
| Storage read count rate | EMS2.BrokerStorageReadCountRate | — |
| Storage write size rate | EMS2.BrokerStorageWriteSizeRate | — |
| Storage write count rate | EMS2.BrokerStorageWriteCountRate | — |
| Instance status | EMS2.BrokerNodeStatus | Status of the broker instance |
| Uptime | EMS2.BrokerUptime | How long the broker has been up for |
QueueRateMetrics
| Metric name | Metric key | Description |
|---|---|---|
| Queue inbound message rate | EMS2.QueueInboundMsgRate | Rate of messages coming in to the queue |
| Queue inbound message size rate | EMS2.QueueInboundMsgSizeRate | Rate of messages coming in to the queue by their size |
| Queue outbound message rate | EMS2.QueueOutboundMsgRate | Rate of messages removed from the queue |
| Queue outbound message size rate | EMS2.QueueOutboundMsgSizeRate | Rate of messages removed from the queue by their size |
Limitations
- Queues, topics, and durables with spaces in their names are not supported by the extension and may cause loss of data.
Message Queues