Data collection
IBM MQ
IBM MQ queue manager error logs, with JSON diagnostic records parsed in full and classic AMQERR text logs parsed line by line for message codes, severity, and timestamps.
- Logs
- Collector-based
- Package 1.0.0
What it collects
- Signals
- Logs
- How it collects
- Log file tailing (
filelog) - Where it runs
- On a Tracix Collector you install. Agentless collection is not offered for it.
- Package version
- 1.0.0
Included in the package
- IBM MQ overview dashboard, 7 panels
- A log-parsing pipeline that maps fields to OpenTelemetry semantic conventions first
How to connect it
- 01Open the connect wizardIn the Tracix console, open Integrations and pick IBM MQ.
- 02Install the Tracix CollectorInstall it where it can reach the data, then add the integration to that collector's policy.
- 03Fill in the connectionEnter the settings the wizard asks for. Collectors pick up the policy change on their own.
More in message queues
All packages in message queues
Apache Kafka
Message queues
Broker, topic, consumer-group lag and partition health from Kafka clusters.
Metrics
RabbitMQ
Message queues
Queue depth, consumer rates, exchange health from the RabbitMQ Management API.
Metrics
ActiveMQ
Message queues
Broker connections, consumers, message backlog, enqueue and dequeue rates, and store, memory, and JVM heap usage over the Jolokia JMX-HTTP bridge.
Metrics
Kafka Connect
Message queues
Connector and task health from the Kafka Connect REST API, including running, paused, and failed connector counts.
Metrics
NATS
Message queues
Connections, subscriptions, msgs/sec and JetStream stats via the Prometheus NATS exporter.
Metrics
NATS Streaming (STAN)
Message queues
NATS Streaming server logs parsed into process, subsystem, severity, and timestamp fields from the nats-server line format.
Logs
Connect IBM MQ to Tracix
Start free and connect it from the console, or book a demo and we will walk through your environment with you.