---
name: vmwaresolutions-logging
title: Logging for VMware Solutions
description: 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.
last-updated: 2026-01-19
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Logging for VMware Solutions
{: #logging}

As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

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.
{: shortdesc}

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](https://cloud.ibm.com/docs/logs-router?topic=logs-router-about&format=markdown).

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.

## Locations where platform logs are generated
{: #log-locations}

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]{: tag-green}  | [Yes]{: tag-green}     | [Yes]{: tag-green} | [No]{: tag-red}      |
{: caption="Regions where platform logs are generated in Americas locations" caption-side="bottom"}
{: #la-table-1}
{: tab-title="Americas"}
{: tab-group="la"}
{: class="simple-tab-table"}
{: row-headers}

| Tokyo (`jp-tok`)   | Sydney (`au-syd`) | Osaka (`jp-osa`) | Chennai (`in-che`) |
|--------------------|-------------------|------------------|--------------------|
| [Yes]{: tag-green} | [No]{: tag-red}   | [No]{: tag-red}  | [No]{: tag-red}    |
{: caption="Regions where platform logs are generated in Asia Pacific locations" caption-side="bottom"}
{: #la-table-2}
{: tab-title="Asia Pacific"}
{: tab-group="la"}
{: class="simple-tab-table"}
{: row-headers}

| Frankfurt (`eu-de`) | London (`eu-gb`) | Madrid (`eu-es`) |
|---------------------|------------------|------------------|
| [Yes]{: tag-green}  | [No]{: tag-red}  | [No]{: tag-red}  |
{: caption="Regions where platform logs are generated in Europe locations" caption-side="bottom"}
{: #la-table-3}
{: tab-title="Europe"}
{: tab-group="la"}
{: class="simple-tab-table"}
{: row-headers}

### Locations where logs are sent by IBM Cloud Logs Routing
{: #lr-locations}



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]{: tag-green}  | [Yes]{: tag-green}     | [Yes]{: tag-green} | [No]{: tag-red}      |
{: caption="Regions where platform logs are sent in Americas locations" caption-side="bottom"}
{: #lr-table-1}
{: tab-title="Americas"}
{: tab-group="lr"}
{: class="simple-tab-table"}
{: row-headers}

| Tokyo (`jp-tok`)   | Sydney (`au-syd`) | Osaka (`jp-osa`) | Chennai (`in-che`) |
|--------------------|-------------------|------------------|--------------------|
| [Yes]{: tag-green} | [No]{: tag-red}   | [No]{: tag-red}  | [No]{: tag-red}    |
{: caption="Regions where platform logs are sent in Asia Pacific locations" caption-side="bottom"}
{: #lr-table-2}
{: tab-title="Asia Pacific"}
{: tab-group="lr"}
{: class="simple-tab-table"}
{: row-headers}

| Frankfurt (`eu-de`) | London (`eu-gb`) | Madrid (`eu-es`) |
|---------------------|------------------|------------------|
| [Yes]{: tag-green}  | [No]{: tag-red}  | [No]{: tag-red}  |
{: caption="Regions where platform logs are sent in Europe locations" caption-side="bottom"}
{: #lr-table-3}
{: tab-title="Europe"}
{: tab-group="lr"}
{: class="simple-tab-table"}
{: row-headers}

## Viewing logs
{: #log-viewing}

To view logs, start IBM Cloud Logs from the Observability page. For more information, see [Launching the UI through the IBM Cloud UI](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-instance-launch&format=markdown#instance-launch-cloud-ui).

## Fields by log type
{: #log-fields}

For information about fields included in every platform log, see [Fields that are included in platform logs](https://cloud.ibm.com/docs/logs-router?topic=logs-router-about-platform-logs&format=markdown#about-platform-logs-2).

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. |
{: caption="Log record fields" caption-side="bottom"}

## Log messages
{: #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_ |
{: caption="Additional information about message IDs" caption-side="bottom"}