---
name: cephaas-at-events-cephaas
title: Activity tracker events for IBM Storage Ceph as a Service
description: IBM Cloud services, such as IBM® Storage Ceph® as a Service, generate activity tracking events.
last-updated: 2026-06-30
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cephaas?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 tracker events for IBM Storage Ceph as a Service
{: #at_events_cephaas}

IBM Cloud services, such as IBM® Storage Ceph® as a Service, generate activity tracking events.
{: shortdesc}

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 from your account to destinations of your choice, by configuring targets and routes, that define where activity tracking events are sent. For instructions, see [Configuring an IBM Cloud Logs target](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-target-cloud-logs&format=markdown){: external}.

For more information, see [About IBM Cloud Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker?topic=atracker-about&format=markdown){: external}.

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

IBM® Storage Ceph® 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]{: tag-green} | [No]{: tag-red} | [No]{: tag-red} | [No]{: tag-red} |
{: 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`) |
|------------------|-------------------|------------------|---------------------|
| [No]{: tag-red} | [No]{: tag-red} | [No]{: tag-red} | [No]{: tag-red} |
{: 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`) |
|---------------------|------------------|------------------|
| [Yes]{: tag-green} | [No]{: tag-red} | [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}



## Viewing activity tracking events
{: #at-viewing}

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
{: #at-events-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){: external}.


## List of management events
{: #at_actions}

The following table lists the IBM Storage Ceph as a Service actions that generate an event.

| Action             | Description      |
|--------------------|------------------|
| software-defined-storage.instance.create       | The service instance was created.   |
| software-defined-storage.instance.update       | The Service instance was updated. |
| software-defined-storage.instance.delete       | The Service instance was deleted.  |
| software-defined-storage.certificate.inspect   | The certificate status was retrieved. |
| software-defined-storage.certificate.update    | The certificate was updated. |
| software-defined-storage.certificate.create    | The certificate was created. |
| software-defined-storage.certificate.delete    | The certificate was deleted. |
| software-defined-storage.s3-credential.create  | The S3 credential was created. |
| software-defined-storage.s3-credential.delete  | The S3 credential was deleted. |
| software-defined-storage.s3-credential.get     | One or more S3 credentials were retrieved. |
| software-defined-storage.volume.create         | The volume was created. |
| software-defined-storage.volume.read           | One or more volumes were retrieved. |
| software-defined-storage.volume.update         | The volume was updated. |
| software-defined-storage.volume.delete         | The volume was deleted. |
| software-defined-storage.host.create           | The host was created. |
| software-defined-storage.host.read             | One or more hosts were retrieved. |
| software-defined-storage.host.update           | The host was updated. |
| software-defined-storage.host.delete           | The host was deleted. |
| software-defined-storage.host.unmap            | The host was unmapped. |
| software-defined-storage.host.map              | The host was mapped. |
{: caption="Actions that generate management events" caption-side="bottom"}