---
name: Registry-registry_logs
title: Logging for Container Registry
description: Container Registry generates platform logs that you can route and analyze to investigate abnormal activity, audit critical actions, and troubleshoot problems.
last-updated: 2026-08-11
---

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

Container Registry generates platform logs that you can route and analyze to investigate abnormal activity, audit critical actions, and troubleshoot problems.
{: shortdesc}

IBM Cloud Logs Routing is a platform service. You can use IBM Cloud Logs Routing to route the platform logs in your account to your choice of destination by configuring a tenant that defines where the 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}

IBM Cloud Container Registry generates platform logs that are displayed in your logging instances. The following tables list the locations where the automatic collection of Container Registry service logs is enabled.

| Locations in Americas | Are platform services logs available? |
| --------------------- | ------------------------------------- |
| `Dallas (us-south)` | [Yes]{: tag-green} |
| `Montreal (ca-mon)` | [Yes]{: tag-green} |
| `Sao Paulo (br-sao)` | [Yes]{: tag-green} |
| `Toronto (ca-tor)` | [Yes]{: tag-green} |
{: caption="The automatic collection of Container Registry service logs in the Americas locations" caption-side="bottom"}
{: #table_registry_logs_service_americas}

| Locations in Asia Pacific | Are platform services logs available? |
| ------------------------- | ------------------------------------- |
| `Chennai - Airtel (in-che)` | [Yes]{: tag-green} |
| `Mumbai - Airtel (in-mum)` | [Yes]{: tag-green} |
| `Osaka (jp-osa)` | [Yes]{: tag-green} |
| `Sydney (au-syd)` | [Yes]{: tag-green} |
| `Tokyo (jp-tok)` | [Yes]{: tag-green} |
{: caption="The automatic collection of Container Registry service logs in the Asia-Pacific locations" caption-side="bottom"}
{: #table_registry_logs_service_ap}

| Locations in Europe | Are platform services logs available? |
| ------------------- | ------------------------------------- |
| `Frankfurt (eu-de)` | [Yes]{: tag-green} |
| `London (eu-gb)` | [Yes]{: tag-green} |
| `Madrid (eu-es)` | [Yes]{: tag-green} |
{: caption="The automatic collection of Container Registry service logs in the Europe locations" caption-side="bottom"}
{: #table_registry_logs_service_europe}

| Location for Global | Are platform services logs available? |
| ------------------- | ------------------------------------- |
| `Global` | [Yes]{: tag-green} |
{: caption="The automatic collection of Container Registry service logs for Global" caption-side="bottom"}
{: #table_registry_logs_service_global}

For more information about where to see Container Registry service logs if you're using IBM Cloud Logs Routing, see [Locations where logs are sent by IBM Cloud Logs Routing](#lr-locations).

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

Container Registry sends logs by IBM Cloud Logs Routing in the regions that are indicated in the following table.

| Dallas (`us-south`) | Montreal (`ca-mon`) | Sao Paulo (`br-sao`) | Toronto (`ca-tor`) | Washington DC (`us-east`) |
| ------------------- | ------------------- | -------------------- | ------------------ | ------------------------- |
| [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} (`global`) |
{: caption="Regions where platform logs are sent in Americas locations" caption-side="top"}
{: #logr-table-1}
{: tab-title="Americas"}
{: tab-group="lr"}
{: class="simple-tab-table"}
{: row-headers}

| Chennai - Airtel (`in-che`) | Mumbai - Airtel (`in-mum`) | Osaka (`jp-osa`) | Sydney (`au-syd`) | Tokyo (`jp-tok`) |
| --------------------------- | -------------------------- | ---------------- | ----------------- | ---------------- |
| [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} | [Yes]{: tag-green} |
{: caption="Regions where platform logs are sent in Asia-Pacific locations" caption-side="top"}
{: #logr-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} | [Yes]{: tag-green} | [Yes]{: tag-green} |
{: caption="Regions where platform logs are sent in Europe locations" caption-side="top"}
{: #logrr-table-3}
{: tab-title="Europe"}
{: tab-group="lr"}
{: class="simple-tab-table"}
{: row-headers}

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

IBM Cloud Container Registry generates platform services logs that are displayed in your logging instances for the following specific cases:

- When IBM Cloud Container Registry runs scheduled retention policies for namespaces in your account.
- When IBM Cloud Container Registry calculates your account's registry traffic and average storage usage per hour for a region.

## Viewing logs
{: #log-viewing}

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

For more information about starting 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 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"}
{: #table_at_log_records}



## Log messages
{: #log_messages}

An example of a billing log in the `message.message` field is:

```text
For the period starting 2026-01-07 06:00:00 +0000 UTC, and ending 2026-01-07 07:00:00 +0000 UTC, this account used 0.00GB traffic, and used an average of 157.90GB storage
```
{: screen}

## Analyzing Container Registry logs
{: #cloud-logs}

You can use the following queries to analyze Container Registry logs:

- A Lucene query for Container Registry platform logs: `message.serviceName:"container\-registry"`
- A DataPrime query for Container Registry platform logs: `filter $d.message.serviceName ~ 'container-registry'`