Migrating to IBM Cloud Logs

How does this announcement affect you?

You might need to:

• Migrate the IBM Cloud Activity Tracker architecture.

  If you use IBM Cloud Activity Tracker to collect and manage activity tracking events that are generated by IBM Cloud services, you will need to configure IBM Cloud Activity Tracker Event Routing to send your activity tracking events to another destination such as IBM Cloud Logs.

• Migrate the IBM® Log Analysis architecture.

  If you use IBM® Log Analysis to collect and manage logs that run in IBM Cloud or outide the IBM Cloud, you will need to configure your hosts, services, or applications to send data to IBM Cloud Logs. For example, you will have to deploy a new agent to send logs from your Kubernetes clusters.

• Migrate the platform logs architecture.

  If you use IBM® Log Analysis to collect and manage platform logs that are generated by IBM Cloud services, you will need to configure IBM Cloud Logs Routing to send your platform logs to IBM Cloud Logs.

• Migrate the IBM Cloud Activity Tracker Event Routing configuration.

  If you use IBM Cloud Activity Tracker Event Routing to configure the routing of activity tracking events to IBM Cloud Activity Tracker instances, you will need to configure the service to route the activity tracking events to IBM Cloud Logs ddestinations.

• Reconfigure sources to send data to the new IBM Cloud Logs instances. For example, you must deploy new agents to send logs from Kubernetes clusters.

• Update IAM permissions in the account.

• Modify run books.

• Update your disaster recovery process.

• Provision the IBM Cloud Event Notifications service.

  In IBM Cloud Logs, alerts are triggered through the IBM Cloud Event Notifications service. If you do not currently use the service and have alerts configured in your IBM Cloud Activity Tracker instances, you must provision an instance of the IBM Cloud Event Notifications service. For more information, see Enabling event notifications for IBM Cloud Logs.

The data format of activity tracking events and platform logs does not change.

Migrating your IBM Cloud Activity Tracker architecture

To migrate IBM Cloud Activity Tracker instances, you must provision 1 or more IBM Cloud Logs instances to replace the existing IBM Cloud Activity Tracker instances, and configure IBM Cloud Activity Tracker Event Routing to define the routing rules in the account that determine where the events that are generated are routed. For more information, see Migrating IBM Cloud Activity Tracker instances.

Migrating your IBM Cloud Activity Tracker Event Routing architecture

If you have IBM Cloud Activity Tracker Event Routing configured in the account, see Migrating IBM Cloud Activity Tracker Event Routing.

Migrating your IBM Log Analysis architecture

To migrate IBM Log Analysis instances that collect only operational and application logs, you must provision IBM Cloud Logs instances in the account to replace the existing IBM Log Analysis instances. You must also configure your data sources to send data to these IBM Cloud Logs instances. Your data sources can be located in IBM Cloud, on-prem, or running in another cloud. For example, you can configure an IBM Cloud Logs Routing agent on supported platforms such as Kubernetes clusters, Red Hat OpenShift clusters, and Linux servers, or send data directly to IBM Cloud Logs by using the public or private ingress endpoint. For more information, see Migrating IBM Log Analysis instances.

To migrate IBM Log Analysis instances that collect platform logs, you must configure IBM Cloud Logs Routing and provision 1 or more IBM Cloud Logs instances in the account to replace the existing IBM Log Analysis instances that are configured to collect platform logs. For more information, see Migrating instances that collect platform logs.