Logging for Container Registry

IBM Cloud services, such as IBM Cloud® Container Registry, 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 About 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 migration planning.

Locations where platform logs are generated

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.

Table 1. The automatic collection of Container Registry service logs in the Americas locations
Locations in Americas	Are platform services logs available?
`Dallas (us-south)`	Yes
`Sao Paulo (br-sao)`	Yes
`Toronto (ca-tor)`	Yes

Table 2. The automatic collection of Container Registry service logs in the Asia Pacific locations
Locations in Asia Pacific	Are platform services logs available?
`Osaka (jp-osa)`	Yes
`Sydney (au-syd)`	Yes
`Tokyo (jp-tok)`	Yes

Table 3. The automatic collection of Container Registry service logs in the Europe locations
Locations in Europe	Are platform services logs available?
`Frankfurt (eu-de)`	Yes
`London (eu-gb)`	Yes
`Madrid (eu-es)`	Yes

Table 4. The automatic collection of Container Registry service logs for Global
Location for Global	Are platform services logs available?
`Global`	Yes

For more information about where to see Container Registry service logs if you are using IBM Cloud Logs Routing, see Locations where logs are sent by IBM Cloud Logs Routing.

Deprecated For more information about where to see Container Registry service logs if you are using IBM Log Analysis, see Locations where logs are sent to IBM Log Analysis.

Locations where logs are sent to IBM Log Analysis

The region in which an IBM Cloud Container Registry or a Vulnerability Advisor log entry is available corresponds to the region of the IBM Cloud Container Registry that generated the log, except for ap-south. Logs for ap-south show in Tokyo (jp-tok).

The following table shows the location of IBM Log Analysis logs.

Table 5. Location of IBM Log Analysis logs
Region for your account's registry	Domain name of your registry	Location of IBM Log Analysis logs
`ap-south`	`au.icr.io`	`Tokyo (jp-tok)`
`ap-north`	`jp.icr.io`	`Tokyo (jp-tok)`
`br-sao`	`br.icr.io`	`Sao Paulo (br-sao)`
`ca-tor`	`ca.icr.io`	`Toronto (ca-tor)`
`eu-central`	`de.icr.io`	`Frankfurt (eu-de)`
`eu-es`	`es.icr.io`	`Madrid (eu-es)`
`jp-osa`	`jp2.icr.io`	`Osaka (jp-osa)`
`uk-south`	`uk.icr.io`	`London (eu-gb)`
`us-south`	`us.icr.io`	`Dallas (us-south)`

The following table shows the location of global registry IBM Log Analysis logs.

Table 6. Location of global registry IBM Log Analysis logs
Registry	Global registry	Location of IBM Log Analysis logs
Global	`icr.io`	`Dallas (us-south)`

Locations where logs are sent by IBM Cloud Logs Routing

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

Table 7. Regions where platform logs are sent in Americas locations
Dallas (`us-south`)	Washington (`us-east`)	Toronto (`ca-tor`)	Sao Paulo (`br-sao`)
Yes	Yes (`global`)	Yes	Yes

Table 7. Regions where platform logs are sent in Asia Pacific locations
Tokyo (`jp-tok`)	Sydney (`au-syd`)	Osaka (`jp-osa`)
Yes	Yes	Yes

Table 7. Regions where platform logs are sent in Europe locations
Frankfurt (`eu-de`)	London (`eu-gb`)	Madrid (`eu-es`)
Yes	Yes	Yes

Platform logs that are generated

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

Launching IBM Cloud Logs from the Observability page

For more information about launching the IBM Cloud Logs UI, see Launching the UI in the IBM Cloud Logs documentation.

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.

Table 8. Log record 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.