Activity tracking events for IBM® MQ as a Service
IBM Cloud services, such as IBM® MQ as a Service, generate activity tracking events.
Activity tracking events report on activities that change the state of a service in IBM Cloud. You can use the events to investigate abnormal activity and critical actions and to comply with regulatory audit requirements.
You can use IBM Cloud Activity Tracker Event Routing, a platform service, to route auditing events in your account to destinations of your choice by configuring targets and routes that define where activity tracking events are sent. For more information, see About IBM Cloud Activity Tracker Event Routing.
You can use IBM Cloud Logs to visualize and alert on events that are generated in your account and routed by IBM Cloud Activity Tracker Event Routing to an IBM Cloud Logs instance.
As of 28 March 2024, the IBM Cloud Activity Tracker 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 Cloud Activity Tracker along with IBM Cloud Logs. Activity tracking events are the same for both services. For information about migrating from IBM Cloud Activity Tracker to IBM Cloud Logs and running the services in parallel, see migration planning.
Locations where activity tracking events are generated
Locations where activity tracking events are sent to IBM Cloud Activity Tracker hosted event search
IBM® MQ as a Service sends activity tracking events to IBM Cloud Activity Tracker hosted event search in the regions that are indicated in the following table.
Dallas (us-south) |
Washington (us-east) |
Toronto (ca-tor) |
Sao Paulo (br-sao) |
|---|---|---|---|
| Yes | Yes | No | No |
Tokyo (jp-tok) |
Sydney (au-syd) |
Osaka (jp-osa) |
Chennai (in-che) |
|---|---|---|---|
| No | No | No | No |
Frankfurt (eu-de) |
London (eu-gb) |
Madrid (eu-es) |
|---|---|---|
| Yes | Yes | No |
Locations where activity tracking events are sent by IBM Cloud Activity Tracker Event Routing
IBM® MQ as a Service sends activity tracking events by IBM Cloud Activity Tracker Event Routing in the regions that are indicated in the following table.
Dallas (us-south) |
Washington (us-east) |
Toronto (ca-tor) |
Sao Paulo (br-sao) |
|---|---|---|---|
| Yes | Yes | No | No |
Tokyo (jp-tok) |
Sydney (au-syd) |
Osaka (jp-osa) |
Chennai (in-che) |
|---|---|---|---|
| No | No | No | No |
Frankfurt (eu-de) |
London (eu-gb) |
Madrid (eu-es) |
|---|---|---|
| Yes | Yes | No |
Viewing activity tracking events for IBM® MQ as a Service
You can use IBM Cloud Logs to visualize and alert on events that are generated in your account and routed by IBM Cloud Activity Tracker Event Routing to an IBM Cloud Logs instance.
Launching IBM Cloud Logs from the Observability page
For information on launching the IBM Cloud Logs UI, see Launching the UI in the IBM Cloud Logs documentation.
List of platform events
The following table lists the activity tracking event actions that the IBM Cloud platform generates IBM® MQ as a Service instances are processed.
| Action | Description |
|---|---|
mqcloud.instance.create |
An event is generated when you provision a service instance. |
mqcloud.instance.update |
An event is generated when you rename a service instance or when you change the service plan. |
mqcloud.instance.delete |
An event is generated when a service instance is deleted. |
List of management events
IBM® MQ as a Service service instances automatically generate events that allow you to track different actions within the service.
| Action | Description |
|---|---|
| mqcloud.queue-manager.create | An event is created when you create a queue manager |
| mqcloud.queue-manager.delete | An event is created when you delete a queue manager |
| mqcloud.queue-manager.update | An event is created when you update a queue manager |
| mqcloud.key-store-cert.create | An event is created when you import a certificate into a key store |
| mqcloud.key-store-cert.delete | An event is created when you delete a certificate from a key store |
| mqcloud.key-store-cert.update | An event is created when you update a certificate in a key store |
| mqcloud.trust-store-cert.create | An event is created when you import a certificate into a trust store |
| mqcloud.trust-store-cert.delete | An event is created when you delete a certificate from a trust store |
| mqcloud.trust-store-cert.update | An event is created when you update a certificate in a trust store |
| mqcloud.admin-credentials.create | An event is created when you create administrator credentials |
| mqcloud.admin-credentials.delete | An event is created when you delete administrator credentials |
| mqcloud.admin-credentials.update | An event is created when you update administrator credentials |
| mqcloud.admin-apikey.create | An event is created when you create an API key for an administrator |
| mqcloud.admin-apikey.update | An event is created when you update an API key for an administrator |
| mqcloud.app-credentials.create | An event is created when you create application credentials |
| mqcloud.app-credentials.delete | An event is created when you delete application credentials |
| mqcloud.app-credentials.update | An event is created when you update application credentials |
| mqcloud.app-apikey.update | An event is created when you update an API key for an application |