Analyzing logs for Container Registry

IBM Cloud® Container Registry generates platform services logs that are displayed in your logging instances.

For more information about how to configure logging instances to receive platform services logs, see Configuring IBM Cloud platform logs. For more information about IBM Cloud Log Analysis, see Getting started with IBM Cloud Log Analysis.

Most of the time when you work with IBM Cloud Container Registry you're pushing, pulling, or managing images. These interactions output results that either you or your automation, tools, or runtime receive; IBM Cloud Container Registry doesn't generate platform logs for them. IBM Cloud Activity Tracker provides a comprehensive list of events for auditing these interactions, see Auditing events for Container Registry.

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.

Locations of platform services logs

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, see Where to look for IBM Log Analysis logs.

For more information about the locations where IBM Cloud services are enabled to send platform logs to IBM Log Analysis, see IBM Cloud services that generate IBM Log Analysis logs by location.

Where to look for IBM Log Analysis logs

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)`