IBM Cloud services that generate IBM Log Analysis logs by location

List of locations where IBM Cloud services are enabled to send logs to IBM® Log Analysis. You monitor these logs that you monitor through the Log Analysis instance that is configured to receive platform services logs. Learn more about enabling service platform logs.

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.

Analytics services

The following table list the locations where automatic collection of analytics service logs is enabled. You can monitor logs through the Log Analysis instance that is available in the same location as your analytics service instance.

Table 1. Analytics services
Service	`Dallas (us-south)`	`Washington (us-east)`
Planning Analytics as a Service

Table 1. Analytics services
Service	`Tokyo (jp-tok)`	`Sydney (au-syd)`
Planning Analytics as a Service

Table 1. Analytics services
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
Planning Analytics as a Service

Compute serverless services

Table 2. Compute serverless services integration in America locations
Service	`Dallas (us-south)`	`Washington (us-east)`
Code Engine

Table 2. Compute serverless services integration in AP locations
Service	`Tokyo (jp-tok)`	`Sydney (au-syd)`
Code Engine

Table 2. Compute serverless services integration in Europe locations
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
Code Engine

Container services

IBM Cloud Container Registry: IBM Cloud Container Registry generates platform services logs that are displayed in your logging instances. For informataion about the locations where the automatic collection of Container Registry service logs is enabled, see Analyzing logs for Container Registry.
IBM Cloud Kubernetes Service: You can choose the logging instance where you want to collect IBM Cloud Kubernetes Service service logs.
IBM Cloud Satellite: You can monitor IBM Cloud Satellite® service logs through the logging instance that is configured with service platform logs in the same region that your Satellite location is managed from.
Red Hat OpenShift on IBM Cloud: You can choose the logging instance where you want to collect Red Hat® OpenShift® on IBM Cloud® service logs.

Database services

The following tables list the locations where automatic collection of database service logs is enabled. You can monitor logs through the Log Analysis instance that is available in the same location as your database resources, if you enable 1 instance in this location to host service platform logs. For locations where you can provision a service instance but the IBM Log Analysis service is not available, specific detail about the location where you can monitor those logs is provided in each case.

Table 3. Database services
Service	`Dallas (us-south)`	`Washington (us-east)`
IBM Cloudant
IBM Cloud Databases for EnterpriseDB
IBM Cloud Databases for DataStax
IBM Cloud Databases for Elasticsearch
IBM Cloud Databases for etcd
IBM Cloud Databases for MongoDB
IBM Cloud® Databases for MySQL
IBM Cloud Databases for PostgreSQL
IBM Cloud Messages for RabbitMQ
IBM Cloud Databases for Redis
IBM® Db2® on Cloud
IBM Db2 Warehouse on Cloud
Watson Query

Table 3. Database services
Service	`Tokyo (jp-tok)`	`Sydney (au-syd)`	`Chennai 01 (che01)`
IBM Cloudant
IBM Cloud Databases for EnterpriseDB
IBM Cloud Databases for DataStax
IBM Cloud Databases for Elasticsearch
IBM Cloud Databases for etcd
IBM Cloud Databases for MongoDB
IBM Cloud® Databases for MySQL
IBM Cloud Databases for PostgreSQL
IBM Cloud Messages for RabbitMQ
IBM Cloud Databases for Redis
IBM® Db2® on Cloud
IBM Db2 Warehouse on Cloud
Watson Query

Table 3. Database services
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
IBM Cloudant
IBM Cloud Databases for Elasticsearch
IBM Cloud Databases for etcd
IBM Cloud Databases for MongoDB
IBM Cloud® Databases for MySQL
IBM Cloud Databases for PostgreSQL
IBM Cloud Messages for RabbitMQ
IBM Cloud Databases for Redis
IBM® Db2® on Cloud
IBM Db2 Warehouse on Cloud
Watson Query

Developer tools

The following table shows the locations where automatic collection of developer tools logs are enabled. You can monitor these logs through the IBM Log Analysis instance that is configured with the developer tools logs in the same location where the developer tools resource is available.

Table 4. Developer tools in America
Service	`Dallas (us-south)`
IBM Cloud® Event Notifications

Table 4. Developer tools in Asia Pacific
Service	`Sydney (au-syd)`
IBM Cloud® Event Notifications

Table 4. Developer tools in Europe
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
IBM Cloud® Event Notifications

Integration services

Table 5. Integration services
Service	`Dallas (us-south)`	`Washington (us-east)`
MQ on Cloud

Table 5. Integration services
Service	`Tokyo (jp-tok)`	`Sydney (au-syd)`
MQ on Cloud

Table 5. Integration services
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
MQ on Cloud

Networking services

Table 6. Networking services
Service	`Dallas (us-south)`	`Washington (us-east)`
IBM Cloud® Load Balancer `[1]`
Dedicated host
Flow Log Collector
VPN		`Logs are available through the logging US-South instance`

Table 6. Networking services
Service	`Tokyo (jp-tok)`	`Sydney (au-syd)`
IBM Cloud® Load Balancer `[1]`
Dedicated host
Flow Log Collector
VPN

Table 6. Networking services
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
IBM Cloud® Load Balancer `[1]`
Dedicated host
Flow Log Collector
VPN

[1] Data logs are only sent if your Softlayer and IBM Cloud® accounts are linked.

Security services

The following tables list the locations where automatic collection of security service logs is enabled. You can monitor logs through the Log Analysis instance that is available in the same location as your security resources, if you enable 1 instance in this location to host service platform logs. For locations where you can provision a service instance but the IBM Log Analysis service is not available, specific detail about the location where you can monitor those logs is provided in each case.

Table 7. Security services
Service	`Dallas (us-south)`	`Washington (us-east)`	`Toronto (ca-tor)`	`Sao Paulo (br-sao)`
IBM Cloud® Secrets Manager

Table 7. Security services
Service	`Tokyo (jp-tok)`	`Sydney (au-syd)`	`Osaka (jp-osa)`
IBM Cloud® Secrets Manager

Table 7. Security services
Service	`Frankfurt (eu-de)`	`London (eu-gb)`	`Madrid (eu-es)`
IBM Cloud® Secrets Manager