Activity tracking events for App Configuration

IBM Cloud services, such as App Configuration, 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

App Configuration sends activity tracking events to IBM Cloud Activity Tracker hosted event search 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	No	No

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

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

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

App Configuration 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	No	No

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

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

Viewing activity tracking events for App Configuration

Events that are generated by App Configuration are automatically forwarded to the IBM Cloud Activity Tracker service instance available in the same location.

IBM Cloud Activity Tracker can have only one instance per location. To view events, you must access the web UI of the IBM Cloud Activity Tracker service in the same location where your service instance is available.

Create a service instance of IBM Cloud Activity Tracker.
Start the IBM Cloud Activity Tracker web console to access your events.

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 data events

The following list of App Configuration events is sent to IBM Cloud Activity Tracker.

Actions that generate data events
Action	Description
`apprapp.segments.create`	Created a segment or failed to create
`apprapp.segments.update`	Updated a segment or failed to update
`apprapp.segments.delete`	Deleted a segment or failed to delete
`apprapp.segments.list`	Called the list of segments or failed to list
`apprapp.segments.read`	Retrieved segment details or failed to retrieve
`apprapp.environments.create`	Created an environment or failed to create
`apprapp.environments.update`	Updated an environment or failed to update
`apprapp.environments.delete`	Deleted an environment or failed to delete
`apprapp.environments.list`	Called the list of environments or failed to list
`apprapp.environments.read`	Retrieved environment details or failed to retrieve environment details
`apprapp.features.create`	Created feature or failed to create
`apprapp.features.update`	Updated feature or failed to update
`apprapp.features.updatevalues`	Updated feature details or failed to update details
`apprapp.features.delete`	Deleted feature or failed to delete
`apprapp.features.list`	Called the list of features or failed to list
`apprapp.features.read`	Retrieved feature details or failed to retrieve the details
`apprapp.features.evaluate`	Evaluated feature at the SDK or failed to evaluate
`apprapp.features.toggle`	Toggled feature or failed to toggle
`apprapp.properties.create`	Created a property or failed to create
`apprapp.properties.update`	Updated property or failed to update
`apprapp.properties.updatevalues`	Updated property details or failed to update
`apprapp.properties.delete`	Deleted property or failed to delete
`apprapp.properties.list`	Called the list of properties or failed to list
`apprapp.properties.read`	Retrieved details of property or failed to retrieve property details
`apprapp.properties.evaluate`	Evaluated property at the SDK or failed to evaluate
`apprapp.collections.create`	Created a collection or failed to create
`apprapp.collections.update`	Updated a collection or failed to update
`apprapp.collections.delete`	Deleted a collection or failed to update
`apprapp.collections.list`	Called the list of collections or failed to list
`apprapp.collections.read`	Retrieved collection details or failed to retrieve collection details
`apprapp.snapshots.create`	Created a snapshot configuration or failed to create
`apprapp.snapshots.update`	Updated a snapshot configuration or failed to update
`apprapp.snapshots.delete`	Deleted a snapshot configuration or failed to delete
`apprapp.snapshots.list`	Called the list of snapshot configuration or failed to list
`apprapp.snapshots.read`	Retrieved snapshot configuration details or failed to retrieve snapshot configuration details
`apprapp.snapshots.promote`	Created or updated the chosen configuration to GitHub based on the snapshots configuration.
`apprapp.snapshots.restore`	Writes or updates the chosen snapshot configuration from the GitHub to App Configuration instance.
`apprapp.originconfigs.update`	Updated the allowlist of origins or failed to update
`apprapp.originconfigs.list`	Called the allowlist of origins or failed to list
`apprapp.workflowconfigs.list`	Get the workflow configurations or failed to list
`apprapp.workflowconfigs.create`	Create a workflow configuration or failed to create
`apprapp.workflowconfigs.update`	Update a workflow configuration or failed to update
`apprapp.workflowconfigs.delete`	Delete a workflow configuration or failed to delete
`apprapp.changerequest.create`	Creates the Change Request for workflow integration or failed to create
`apprapp.changerequest.update`	Captures the change of events in the Change Request of Service Now for workflow or failed to update
`apprapp.config.import`	Import a instance configuration.
`apprapp.config.export`	Export instance configuration.
`apprapp.config.action`	Promotes or Restores a Snapshot configuration to or from GitHub respectively.
`apprapp.config-aggregator-settings.update`	Updates the configuration aggregator recording set-up and allows to either enable or disable the feature or failed to update
`apprapp.config-aggregator-settings.list`	Called to view the settings configuration or failed to list
`apprapp.config-aggregator-status.list`	Called to view status and time when the last configuration got updated or failed to list.
`apprapp.config-aggregator.query`	Called to list the resource configurations.

If an unauthorized request is made for any of the actions in table 3, a management event with reason code 403 is emitted.