Removing deprecated IBM Log Analysis instances with platform logs enabled

Review the IBM Cloud Logs Routing configuration and verify that your platform logs are routed to your cloud_logs targets.

Check that your IBM Log Analysis instances across all regions are migrated.

Get the details of each IBM Log Analysis instance in your account by running the following command: resource service-instance --id InstanceCRN -o JSON

For alerting, check the integration between each IBM Cloud Logs instance and the IBM Cloud Event Notifications instance that you use for alerting. For more information, see Test your connection.

Check that permissions on the new IBM Cloud Logs instances are in place and working for your requirements.

In IBM Cloud Logs Routing, for each region where you operate, remove the Log Analysis target configured for the region.

If you have other sources, such as Linux services or Kubernetes clusters, for each source that is configured to send logs to IBM Log Analysis in the account, remove the configuration. For example,

• Remove logDNA agents from sources.

• Clean up your rsyslog configuration.

• Modify your custom apps that send logs directly by using the REST API.

In IBM Cloud® Identity and Access Management (IAM), remove the policies that grant permissions to work with IBM Log Analysis instances in the account.

• Remove policies from access groups.

• Remove policies from users.

• Remove policies from service IDs.

• Remove policies from trusted profiles.

Delete the IBM Log Analysis instances.