Managing logs in a new location after Log Analysis is available

To manage logs from IBM Cloud services that generate logs in a new region where the IBM Log Analysis 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 logs send currently those logs to the Frankfurt region. You can manage logs from these services in Frankfurt. Platform logs include the field logSourceCRN that specifies the region, location, or data center where the resource is available. For example, for Madrid, you can see the location of logs set to eu-es.

You cannot control when an IBM Cloud service makes the switch to send logs 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.

Figure 1. Flow of logs 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 Log Analysis service is available in the new region, for example, Madrid, complete the following steps:

Create a new IBM Log Analysis hosted event search instance.
Configure IAM access for the new instance.

Step 2. Configure the new instance

Complete the following steps:

Enable platform logs. For more information, see Configuring IBM Cloud platform logs.
Configure any desired streaming.
- To another [IBM Log Analysis instance.]/docs/log-analysis?topic=log-analysis-streaming-configure-l2l)
- To an IBM® Event Streams for IBM Cloud® instance.
On the new instance, configure any desired archiving.
Customize the UI for the new instance as needed.

If you have queries based on location, you must update them. For example, you might need to update the location to eu-es for a configuration in the Madrid location.
Create any alerts required for your organization on the new instance.

Step 3. [Optional] Configure logging agents

If you have logging agents configured to send data from Kubernetes clusters or Openshift clusters, for example, you can update the agents to point to the new instance in the new location (for example, Madrid).

For more information, see:

Step 4. Check the new instance is working

To monitor logs, you must provision an instance of the IBM Log Analysis service in the region where logs are sent. For more information, see Getting started.