Logging for IBM MQ as a Service - IBM Cloud

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.

Locations where platform logs are generated

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

Table 1. platform log locations
Americas	Asia-Pacific	Europe
Dallas (`us-south`) - Yes	Tokyo (`jp-tok`) - No	Frankfurt (`eu-de`) - Yes
Washington (`us-east`) - Yes	Sydney (`au-syd`) - No	London (`eu-gb`) - Yes
Toronto (`ca-tor`) - No	Osaka (`jp-osa`) - No	Madrid (`eu-es`) - No
Sao Paulo (`br-sao`) - No	Chennai (`in-che`) - 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.

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.

Label	Explanation
`message.ibm_messageId`	Starting `AMQ` - this value refers to the category of the IBM MQ diagnostic message, see AMQ messages in the main IBM MQ documentation for further detail
`message.ibm_version`	The IBM MQ version in the form `9.4.5.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 IBM MQ error

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

Analyzing IBM MQ as a Service logs

You can set a filter to view logs from IBM MQ by adding the App filter. When you have logs from an IBM MQ service instance you can then select mqcloud in this filter and this will limit your view to only logs from your IBM 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"