IBM Cloud Docs
Managing events in a new location after Activity Tracker is available

Managing events in a new location after Activity Tracker is available

To manage events from IBM Cloud services that generate auditing events in a new region where the IBM Cloud Activity Tracker service is not available until a later date, complete these instructions.

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 example, the Madrid region opened for business in June 2023. IBM Cloud services that are available and generate auditing events send currently those events to the Frankfurt region. You can manage and monitor interaction with these services in Frankfurt. Auditing events include the field logSourceCRN that specifies the region, location, or datacenter where the resource is available. For example, for Madrid, you can see the location of auditing events set to eu-es.

You cannot control when an IBM Cloud service makes the switch of sending auditing events from one region to another one. However, you can provision an instance in the new region to prepare for that switch.

Data is not sent to both locations, complete the steps before that switch is done by a service to mitigate any loss of data.

Flow of events in a single region
Figure 1. Flow of events in a single region

Complete the following steps to enable the service in the new region:

Step 1. Provision an instance of the service in the new region

As soon as the IBM Cloud Activity Tracker service is available in the new region, for example, Madrid, complete the following steps:

  1. Create a new IBM Cloud Activity Tracker hosted event search instance.

  2. Configure IAM access for the new instance.

Consider the following information:

  • The Schematics service will continue to send events to the Frankfurt region.

  • For Cloud Object Storage buckets, once the service makes the change to send events to Madrid, you will continue to receive events in Frankfurt. To move the events that are gerenared by a bucket to be managed through Madrid, you must use the COS Resource Configuration API to reconfigure the Activity Tracker instance to the one located in Madrid. Otherwise, these events will continue to go to the instance that is configured for the bucket.

Step 2. Configure the new instance

Complete the following steps:

  1. Configure any desired streaming.

  2. On the new instance, configure any desired archiving.

  3. Customize the UI for the new instance as needed.

    If you have queries based on location, update them. For example, you might need to update the location to eu-es for a configuration in the Madrid location.

  4. Create any alerts required for your organization on the new instance.

Step 3. Check the new instance is working

To monitor auditing events, provision an instance of the IBM Cloud Activity Tracker service in the region where events are sent. For more information, see Getting started.