Activity tracking events for Cloud Databases

Gen 2

IBM Cloud® services, such as Cloud Databases, generate activity tracking events that capture changes to the state of a service. These events help you identify critical actions, investigate unusual activity, and support audit and compliance efforts.

With IBM Cloud® Activity Tracker Event Routing, you can direct these events to specific destinations by configuring targets and routes, giving you control over how auditing data is collected and where it is sent. This enables timely investigation of abnormal activity, supports security and compliance needs, and helps meet regulatory audit requirements.

You need an IBM® Cloud Logs instance to visualize and alert on events that are generated in your account and routed by IBM Cloud Activity Tracker Event Routing.

Locations where activity tracking events are generated

Locations where activity tracking events are sent by IBM Cloud Activity Tracker Event Routing

Cloud Databases sends activity tracking events by IBM Cloud Activity Tracker Event Routing in the regions that are indicated in the following table.

Regions where activity tracking events are sent in Americas locations
Dallas (`us-south`)	Washington (`us-east`)	Toronto (`ca-tor`)	Sao Paulo (`br-sao`)
Yes	Yes	Yes	Yes

Regions where activity tracking events are sent in Asia Pacific locations
Tokyo (`jp-tok`)	Sydney (`au-syd`)	Osaka (`jp-osa`)	Chennai (`in-che`)
Yes	Yes	Yes	Yes

Regions where activity tracking events are sent in Europe locations
Frankfurt (`eu-de`)	London (`eu-gb`)	Madrid (`eu-es`)	Paris (`eu-par01`)
Yes	Yes	Yes	No

Enabling activity tracking events for Cloud Databases

Create an IBM Cloud Logs instance and configure IBM Cloud Activity Tracker Event Routing by setting the routing rule between the Cloud Databases instance and the IBM Cloud Logs target instance.

Viewing activity tracking events for Cloud Databases

Deploy an IBM Cloud Logs instance 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 Cloud Databases dashboard

Select your Cloud Databases instance from the databases resource list. Then click on Overview and scroll to the Observability section. Click on IBM Cloud Logs to view your logging instances. Click on Open Dashboard to access the logs.

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 Cloud Databases and IBM Cloud generate.

List of events and event descriptions by Cloud Databases
Action name	Legacy action name	Description
`<service_name>.deployment-backup.create`	`<service_id>.backup-ondemand.create`	A backup of your instance was created. The message contains the database version along with size, id, status and type of the backup.
`<service_name>.deployment-backup.delete`	`<service_id>.backup-ondemand.delete`	A backup of your instance was deleted. The message contains the type of the database.
`<service_name>.restore.hydrate`	`<service_id>.restore-ondemand.hydrate`	A restore of a backup to a new service instance was created. The message contains the status of the hydration of the restored instance.

The service_name field indicates the type of Cloud Databases instance. For example, databases-for-postgresql or messages-for-rabbitmq.

Auditing of global events, such as <service_name>.instance.create, is covered by the IBM Cloud global event. For more resource-related global events, see Auditing events for service instances.