---
name: databases-for-postgresql-logging
title: Logging for Cloud Databases
description: IBM Cloud® services, such as Cloud Databases, generate platform logs that you can use to investigate abnormal activity and critical actions in your account, and troubleshoot problems.
last-updated: 2026-07-28
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/databases-for-postgresql?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 Cloud Databases
{: #logging}

IBM Cloud® services, such as Cloud Databases, 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 [About 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}



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



Cloud Databases 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} | [Yes]{: tag-green} |
{: caption="Regions where platform logs are sent in Americas locations" caption-side="top"}
{: #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} | [Yes]{: tag-green} | [Yes]{: tag-green} | [No]{: tag-red} |
{: caption="Regions where platform logs are sent in Asia Pacific locations" caption-side="top"}
{: #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`) |  Paris (`eu-par01`) |
|---------------------------------------------------------------|---------------------|------------------|-------|
| [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} |  [No]{: tag-red}  |
{: caption="Regions where platform logs are sent in Europe locations" caption-side="top"}
{: #lr-table-3}
{: tab-title="Europe"}
{: tab-group="lr"}
{: class="simple-tab-table"}
{: row-headers}

## Platform logs that are generated
{: #log-platform}



Cloud Databases generates platform logs for the severity types debug, error, info, warning, and critical.

Platform logs from your database instances can be routed to any region supported as per the previous table. Logs from Chennai (`in-che`) and Osaka (`jp-osa`) are routed to Tokyo (`jp-tok`) and logs from Paris (`eu-par01`) are routed to Frankfurt (`eu-de`).



## Enabling logging
{: #log-enable}









Create IBM Cloud Logs and configure routing by setting the target between source location to target instance.

## Viewing logs
{: #log-viewing}



Cloud Databases logs can be viewed in on the IBM Cloud Logs instance created. Go to the [Logging instance page](https://cloud.ibm.com/observability/logging){:external} and click on _Dashboard._

### Launching IBM Cloud Logs from the Cloud Databases page
{: #log-launch-integrated}



Users can visit the Cloud Databases instance. Click on _Overview_ and scroll to the _Observability_ section. Click on *IBM Cloud Logs* to view your logging instances. Click on _Dashboard_ to access the logs.

### Launching IBM Cloud Logs from the Observability page
{: #log-launch-standalone}



For more information about launching the IBM Cloud Logs UI, see [Launching the UI in the IBM Cloud Logs documentation](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-instance-launch&format=markdown).

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



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










Cloud Databases logs include the following fields.

| 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. |
| `messageID`       | Required   | ID of the log that is generated. |
{: caption="Log record fields" caption-side="bottom"}

Cloud Databases sends audit events as platform logs. For more information, see [Activity tracking for Cloud Databases](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-at_events&format=markdown).






## Analyzing Cloud Databases logs
{: #cloud-logs}



In the IBM Cloud Logs Dashboard, users can filter based on _Application_, _Subsystem_, _Severity_  to find logs specific to an instance. Users can also create a custom dashboard, view logs or write a query to search for a log data. example label.region:"us-south"

They can also create _alerts_ in the IBM Cloud Logs.