Logging for VMware Solutions
IBM Cloud® services, such as IBM Cloud® for VMware Solutions generate platform logs that you can use to investigate abnormal activity and critical actions in your account, and troubleshoot problems.
You can use IBM Cloud Logs Routing, a platform service to route platform logs in your account to a destination of your choice by configuring a tenant that defines where platform logs are sent. For more information, see Learning about IBM Cloud Logs Routing.
You can use IBM Cloud Logs to visualize and alert on platform logs that are generated in your account and routed by IBM Cloud Logs Routing to an IBM Cloud Logs instance.
As of 28 March 2024, the IBM Log Analysis service is deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to IBM Cloud Logs before 30 March 2025. During the migration period, customers can use IBM Log Analysis along with IBM Cloud Logs. Logging is the same for both services. For information about migrating from IBM Log Analysis to IBM Cloud Logs and running the services in parallel, see Migrating to IBM Cloud Logs.
Locations where platform logs are generated
IBM Cloud for VMware Solutions generates platform logs in the regions that are indicated in the following table.
Dallas (us-south) |
Washington (us-east) |
Toronto (ca-tor) |
Sao Paulo (br-sao) |
|---|---|---|---|
| Yes | Yes | Yes | No |
Tokyo (jp-tok) |
Sydney (au-syd) |
Osaka (jp-osa) |
Chennai (in-che) |
|---|---|---|---|
| Yes | No | No | No |
Frankfurt (eu-de) |
London (eu-gb) |
Madrid (eu-es) |
|---|---|---|
| Yes | No | No |
Locations where platform logs are sent to IBM Log Analysis
VMware Solutions sends platform logs to IBM Log Analysis in the regions indicated in the following table.
Dallas (us-south) |
Washington (us-east) |
Toronto (ca-tor) |
Sao Paulo (br-sao) |
|---|---|---|---|
| Yes | Yes | Yes | No |
Tokyo (jp-tok) |
Sydney (au-syd) |
Osaka (jp-osa) |
Chennai (in-che) |
|---|---|---|---|
| Yes | No | No | No |
Frankfurt (eu-de) |
London (eu-gb) |
Madrid (eu-es) |
|---|---|---|
| Yes | No | No |
Locations where logs are sent by IBM Cloud Logs Routing
VMware Solutions sends logs by IBM Cloud Logs Routing in the regions that are indicated in the following table.
Dallas (us-south) |
Washington (us-east) |
Toronto (ca-tor) |
Sao Paulo (br-sao) |
|---|---|---|---|
| Yes | Yes | Yes | No |
Tokyo (jp-tok) |
Sydney (au-syd) |
Osaka (jp-osa) |
Chennai (in-che) |
|---|---|---|---|
| Yes | No | No | No |
Frankfurt (eu-de) |
London (eu-gb) |
Madrid (eu-es) |
|---|---|---|
| Yes | No | No |
Viewing logs
To view logs, start IBM Cloud Logs from the Observability page. For more information, see Launching the UI through the IBM Cloud UI.
Fields by log type
For information about fields included in every platform log, see Fields that are included in platform logs.
The following fields are included in the log record:
| Field | Type | Description |
|---|---|---|
logSourceCRN |
Required | Defines the account and flow log instance where the log is published. |
saveServiceCopy |
Required | Defines whether IBM saves a copy of the record for operational purposes. |
message |
Required | Description of the log that is generated. |
Log messages
The following tables list the message IDs that are generated and additional information available about these messages.
| Message ID | Type | Learn More |
|---|---|---|
is.flow-log-collector.00001E |
Error | Failed to write a Flow log file for the past 24 hours. Dropping flow log for Virtual Server ServerName |