IBM Support

MustGather: Instana MQ Sensor/Tracer

Troubleshooting


Problem

This guide provides essential steps for collecting data related to Instana MQ sensor/tracer. Before contacting IBM® support for assistance, please review the information below to familiarize yourself with the troubleshooting process.

Resolving The Problem

To explore potential solutions, search for issues, access documentation, or visit support forums, head to the IBM® Support page. If you are aware of the affected component, refer to the relevant MustGather details below:

MustGather Data Collection Requirements for Instana MQ Sensor/Tracer

Monitored environment details:
 
1. Environment where IBM MQ is running (VM, Kubernetes etc)
 
2. IBM MQ version
 
3. OS and version in case of VM
 
4. Is the monitoring local or remote?
 
5. In case of local monitoring, is the client using local binding or client binding?
 
6. SaaS url of the agent monitoring IBM MQ
 
7. Provide info/details about eventual HA solution in place
 
8. Verify if the issue is mentioned in the troubleshooting section of Instana documentation - https://www.ibm.com/docs/en/instana-observability/current?topic=technologies-monitoring-mq 
 
Agent logs:

Collect debug log of Instana agent:
See the MustGather page for Instana Agent for more details

IBM MQ logs:

Unix/Linux:  /var/mqm/qmgrs/<qmgr_name>/errors/AMQERR0n.LOG  with n=1,2,3
Windows:  <drive>:\ProgramData\IBM\MQ\qmgrs\<qmgr_name>\errors\AMQERR0n.LOG  with n=1,2,3

Agent Configuration:

Locate <instana-agent-dir>/etc/instana/configuration.yaml file and share it

Additional output & files to collect:
 
Include the following supplementary information to assist with issue resolution:
 
1. Screenshots showcasing the problem.
 
2. Relevant Instana UI links leading to the corresponding issue.
 
3. Additional info/files to collect:
 
  • Output of the following mq_status.sh script:
    Linux:  https://github.com/instana/serviceability/blob/main/agent/ibm-mq/mq_status.sh
    Windows (PowerShell): https://github.com/instana/serviceability/blob/main/agent/ibm-mq/mq_status.ps1
    You can redirect the output into a file (eg ./mq_status.sh > mqstatus.txt) and send it to IBM Support.
  • Linux:
    • netstat -anp > netstat.txt
    • Output of "ps -ef" 
  • Windows:
    • netstat -b -o > netstat.txt
    • wmic process list > processes.txt
  •  All available files and their exact locations:
    • mqs.ini, qm.ini for the affected QMGR(s), mqinst.ini
  • For Tracer related issues (user exit):
    • Tracer version
    • Tracer configuration:
      • Default location: `/var/mqm/exits64/mqtracingexit.conf`
    • Tracer logs:
      • Default location: `/tmp/ibmmqtrace`
    • Coredump Analysis (if applicable):
      • Provide backtrace of coredump using gdb/lldb/dbx

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSE1JP5","label":"IBM Instana Observability"},"ARM Category":[{"code":"a8mKe000000XZQ5IAO","label":"MustGather"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]

Document Information

Modified date:
04 June 2025

UID

ibm17233097