IBM Cloud Docs
Collecting events

Collecting events

In IBM Cloud® Activity Tracker, events are collected automatically for most Activity Tracker-enabled services. However, some services might require an upgrade of the service plan, a configuration setting, or both, for you to be able to collect and analyze their events.

As of 28 March 2024 the IBM Log Analysis and IBM Cloud Activity Tracker services are deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to IBM Cloud Logs, which replaces these two services, prior to 30 March 2025. For information about IBM Cloud Logs, see the IBM Cloud Logs documentation.

Activity Tracker routes location-based auditing events to an Activity Tracker instance in the region where they are generated and routes global auditing events to the Activity Tracker instance that is provisioned in Frankfurt.

To collect and monitor activity in your account, you must configure the Activity Tracker service in your account.

In Activity Tracker, you can differentiate events by scope as global or location-based events, and by operational impact as either management or data events.

  • The scope is determined from where an event is collected.

  • Collection of management events is automatic for Activity Tracker-enabled services, except for Watson services which require a paid plan.

  • Collection of data events is also automatic with the exception of some services where you must opt-in to collect those events. To opt-in, you might need to configure the service, upgrade the service plan, or both. For more information, see Data events.

Collecting global events

Global events are available through the Activity Tracker instance in Frankfurt.

To collect and view global events, you must provision an instance of the Activity Tracker service in Frankfurt. Learn more.

Collecting location-based events

Location-based events are available through the Activity Tracker instance that is available in the same region as the service. Learn more.