at-events.md

copyright	years 2026
lastupdated	2026-06-02
keywords	activity tracker
subcollection	cloud-databases-gen2

{{site.data.keyword.attribute-definition-list}}

Activity tracking events for {{site.data.keyword.databases-for}}

{: #at_events}

[Gen 2]{: tag-purple}

{{site.data.keyword.cloud}} services, such as {{site.data.keyword.databases-for}}, 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 {{site.data.keyword.atracker_full}}, 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 {{site.data.keyword.logs_full}} instance to visualize and alert on events that are generated in your account and routed by {{site.data.keyword.atracker_full_notm}}. {: note}

Locations where activity tracking events are generated

{: #at-locations}

Locations where activity tracking events are sent by {{site.data.keyword.atracker_full_notm}}

{: #atracker-locations}

{{site.data.keyword.databases-for}} sends activity tracking events by {{site.data.keyword.atracker_full_notm}} 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 {{site.data.keyword.databases-for}}

{: #at-enable}

Create an {{site.data.keyword.logs_full_notm}} instance and configure {{site.data.keyword.atracker_full_notm}} by setting the routing rule between the {{site.data.keyword.databases-for}} instance and the {{site.data.keyword.logs_full_notm}} target instance.

Viewing activity tracking events for {{site.data.keyword.databases-for}}

{: #at-viewing}

Deploy an {{site.data.keyword.logs_full_notm}} instance to visualize and alert on events that are generated in your account and routed by {{site.data.keyword.atracker_full_notm}} to an {{site.data.keyword.logs_full_notm}} instance.

Launching {{site.data.keyword.logs_full_notm}} from the {{site.data.keyword.databases-for}} dashboard

{: #log-launch-integrated}

Select your {{site.data.keyword.databases-for}} instance from the databases resource list. Then click on Overview and scroll to the Observability section. Click on {{site.data.keyword.logs_full_notm}} to view your logging instances. Click on Open Dashboard to access the logs.

Launching {{site.data.keyword.logs_full_notm}} from the Observability page

{: #log-launch-standalone}

For information on launching the {{site.data.keyword.logs_full_notm}} UI, see Launching the UI in the {{site.data.keyword.logs_full_notm}} documentation.

List of platform events

{: #at_actions_platform}

The following table lists the activity tracking event actions that {{site.data.keyword.databases-for}} and {{site.data.keyword.cloud_notm}} 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.
<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.
{: caption="List of events and event descriptions by {{site.data.keyword.databases-for}}" caption-side="bottom"}

The service_name field indicates the type of {{site.data.keyword.databases-for}} instance. For example, databases-for-postgresql or messages-for-rabbitmq.

Auditing of global events, such as <service_name>.instance.create, is covered by the {{site.data.keyword.cloud_notm}} global event. For more resource-related global events, see Auditing events for service instances.