IBM Cloud Docs
Migrating from IBM Log Analysis or IBM Cloud Activity Tracker to IBM Cloud Logs

Migrating from IBM Log Analysis or IBM Cloud Activity Tracker to IBM Cloud Logs

The IBM® Cloud Logs migration tool is a command line tool that you can use to migrate your IBM Log Analysis or IBM Cloud Activity Tracker instance configuration to IBM Cloud Logs.

For full details about the migration process and tooling, see the IBM Cloud Logs documentation, especially the topics in these sections:

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.

If you plan to migrate using the migration tool, you must do so before IBM® Log Analysis and IBM Cloud Activity Tracker are de-provisioned and deleted on 30 March 2025.

Overview of migrating to IBM Cloud Logs
Overview of migrating to IBM Cloud Logs

The tool requires minimal user interaction. Cloud Identity and Access Management authentication and APIs are used to get the details about your current IBM Log Analysis or IBM Cloud Activity Tracker instance.

The migration tool migrates only configuration information. No data is migrated from IBM Log Analysis or IBM Cloud Activity Tracker to IBM Cloud Logs.

You can use the tool to:

  • Migrate IBM Log Analysis and IBM Cloud Activity Tracker instance configurations.

  • Migrate IBM Log Analysis and IBM Cloud Activity Tracker resources such as views, dashboards, alerts, exclusion rules, archiving configuration and more.

  • Migrate IBM Cloud associated resources such as Cloud Identity and Access Management permissions.

  • Migrate the archiving configuration that is enabled in an IBM Log Analysis or IBM Cloud Activity Tracker instance.

The tool generates exception reports that indicate items that cannot be migrated automatically and require more migration steps. Exceptions can include:

  • Resources requiring user validation before migration. Examples of these include custom catalogs and IAM permissions.

  • Migrated resources that require more user tasks, such as regenerating API keys for new IBM Cloud Logs resources.

  • Resources that are not part of the migration tool, such as configuring a cross-account IBM Cloud Object Storage bucket or bucket outside of IBM Cloud.

Terraform artifacts can be created that can be used to create new IBM Cloud Logs instances. Terraform on IBM Cloud enables predictable and consistent creation of IBM Cloud services so that you can rapidly build complex, multitier cloud environments by following Infrastructure as Code (IaC) principles. Similar to using the IBM Cloud CLI or API and SDKs, you can automate the creation, update, and deletion of your IBM Cloud Logs instances by using the HashiCorp Configuration Language (HCL).

For details about migration and the migration tool, see Migrating to IBM Cloud Logs.