---
name: cloud-databases-gen2-at-events
title: Activity tracking events
description: 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.
last-updated: 2026-06-22
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-databases-gen2?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Activity tracking events
{: #at_events}

[Gen 2]{: tag-purple}


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.
{: shortdesc}

With [IBM Cloud® Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker?topic=atracker-about&format=markdown), 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](https://cloud.ibm.com/observability/logging) instance to visualize and alert on events that are generated in your account and routed by IBM Cloud Activity Tracker Event Routing.
{: note}

## Locations where activity tracking events are generated
{: #at-locations}



### Locations where activity tracking events are sent by IBM Cloud Activity Tracker Event Routing
{: #atracker-locations}



Cloud Databases 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]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} |
{: caption="Regions where activity tracking events are sent in Americas locations" caption-side="top"}
{: #atracker-table-1}
{: tab-title="Americas"}
{: tab-group="atracker"}
{: class="simple-tab-table"}
{: row-headers}

| Tokyo (`jp-tok`)    | Sydney (`au-syd`) |  Osaka (`jp-osa`) | Chennai (`in-che`) | Mumbai (`in-mum`) |
|---------------------|------------------|------------------|--------------------|--------------------|
| [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} |
{: caption="Regions where activity tracking events are sent in Asia Pacific locations" caption-side="top"}
{: #atracker-table-2}
{: tab-title="Asia Pacific"}
{: tab-group="atracker"}
{: class="simple-tab-table"}
{: row-headers}

| Frankfurt (`eu-de`)  | London (`eu-gb`) | Madrid (`eu-es`) |  Paris (`eu-par01`) |
|---------------------------------------------------------------|---------------------|------------------|------|
| [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} |  [No]{: tag-red}
{: caption="Regions where activity tracking events are sent in Europe locations" caption-side="top"}
{: #atracker-table-3}
{: tab-title="Europe"}
{: tab-group="atracker"}
{: class="simple-tab-table"}
{: row-headers}

## Enabling activity tracking events for Cloud Databases
{: #at-enable}






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
{: #at-viewing}



Deploy an [IBM Cloud Logs](https://cloud.ibm.com/observability/logging) 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
{: #log-launch-integrated}



Select your [Cloud Databases](https://cloud.ibm.com/databases-overview/resources) 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
{: #log-launch-standalone}



For information on launching the IBM Cloud Logs UI, see [Launching the UI in the IBM Cloud Logs documentation.](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-instance-launch&format=markdown)

## List of platform events
{: #at_actions_platform}



The following table lists the activity tracking event actions that Cloud Databases and IBM Cloud generate.

| 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. Applicable only for coupled backups. |
| `<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. Applicable only for coupled backups. |
| `<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. Not applicable for Databases for MySQL. |
{: caption="List of events and event descriptions by Cloud Databases" caption-side="bottom"}

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](https://cloud.ibm.com/docs/atracker?topic=atracker-at_events_rc&format=markdown).