IBM Cloud Docs
Logging for IBM® MQ as a Service

Logging for IBM® MQ as a Service

IBM Cloud services, such as IBM® MQ as a Service, generate platform logs that you can use to investigate abnormal activity and critical actions in your account, and troubleshoot problems.

You can use IBM Cloud Logs Routing, a platform service, to route platform logs in your account to a destination of your choice by configuring a tenant that defines where platform logs are sent. For more information, see About Logs Routing.

You can use IBM Cloud Logs to visualize and alert on platform logs that are generated in your account and routed by IBM Cloud Logs Routing to an IBM Cloud Logs instance.

As of 28 March 2024, the IBM Log Analysis service is deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to IBM Cloud Logs before 30 March 2025. During the migration period, customers can use IBM Log Analysis along with IBM Cloud Logs. Logging is the same for both services. For information about migrating from IBM Log Analysis to IBM Cloud Logs and running the services in parallel, see migration planning.

Locations where platform logs are generated

Locations where logs are sent to IBM Log Analysis

IBM® MQ as a Service sends platform logs to IBM Log Analysis in the regions indicated in the following table.

Regions where platform logs are sent in Americas locations
Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao)
Yes Yes No No
Regions where platform logs are sent in Asia Pacific locations
Tokyo (jp-tok) Sydney (au-syd) Osaka (jp-osa) Chennai (in-che)
No No No No
Regions where platform logs are sent in Europe locations
Frankfurt (eu-de) London (eu-gb) Madrid (eu-es)
Yes Yes No

Locations where logs are sent by IBM Cloud Logs Routing

IBM® MQ as a Service sends logs by IBM Cloud Logs Routing in the regions that are indicated in the following table.

Regions where platform logs are sent in Americas locations
Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao)
Yes Yes No No
Regions where platform logs are sent in Asia Pacific locations
Tokyo (jp-tok) Sydney (au-syd) Osaka (jp-osa) Chennai (in-che)
No No No No
Regions where platform logs are sent in Europe locations
Frankfurt (eu-de) London (eu-gb) Madrid (eu-es)
Yes Yes No

Viewing logs

Logs that are generated by IBM® MQ as a Service service and from queue managers deployed within these instances can be viewed directly from an IBM Cloud Logs which is configured to receive platform logs for the corresponding region.

Launching IBM Cloud Logs from the Observability page

For more information about launching the IBM Cloud Logs UI, see Launching the UI in the IBM Cloud Logs documentation.

Fields by log type

For information about fields included in every platform log, see Fields for platform logs

Table 1. Key MQ log fields for debug
Label Explanation
message.ibm_messageId Starting AMQ - this value refers to the category of the IBM MQ diagnostic message, see reference for further detail
message.ibm_version The MQ version in the form 9.3.4.0
message.loglevel The level of log, for example WARNING or ERROR
message.ibm_serverName The name of the QueueManager
message.message The main message content for the MQ error
message.message The main message content for the MQ error

For a full reference on all of the available fields for MQ log messages, see IBM MQ documentation for JSON format diagnostic messages

Analyzing IBM® MQ as a Service logs

You can set a filter to view logs from MQ by adding the App filter. When you have logs from an MQ service instance you can then select mqcloud in this filter and this will limit your view to only logs from your MQ service instances.

If you want to isolate logs from a particular instance or queue manager you can use the following queries.

message.logSourceCRN can be used to isolate visible logs to a specific service instance. Get the CRN for your service instance and then set this query.

message.logSourceCRN:"<service-instance-crn>"

message.ibm_serverName can be used to filter on the name of your queue manager.

message.ibm_serverName:"QM1"