---
name: Registry-registry_monitor
title: Monitoring metrics for Container Registry
description: You can use IBM Cloud® Monitoring to monitor platform metrics of IBM Cloud® Container Registry usage for your account and to create alerts based on these metrics.
last-updated: 2026-05-18
---

> ## 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.

# Monitoring metrics for Container Registry
{: #registry_monitor}

You can use IBM Cloud® Monitoring to monitor platform metrics of IBM Cloud® Container Registry usage for your account and to create alerts based on these metrics.
{: shortdesc}

Platform metrics for Container Registry must be enabled in each Container Registry region that you want to monitor, see [Enabling metrics for Container Registry](#registry_enable_platform_metrics). For more information about IBM Cloud Monitoring, see [Monitoring in IBM Cloud](https://cloud.ibm.com/docs/monitoring?topic=monitoring-about-monitor&format=markdown).

## Enabling metrics for Container Registry
{: #registry_enable_platform_metrics}

You must enable Container Registry metrics in each region that you want to see metrics.
{: note}

You can create a Monitoring instance in the region that you want to monitor and enable platform metrics for it. Alternatively, you can enable platform metrics on an existing Monitoring instance in that region.

Complete the following steps to create and configure platform metrics for Container Registry.

1. Create and configure an IBM Cloud Monitoring instance that is configured with platform metrics in the region that you want to monitor, see [Getting started with IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started&format=markdown).

   For more information about the locations where Container Registry is enabled for monitoring, see [Locations of platform metrics](#registry_monitor_locations).

2. Log in to IBM Cloud.

    ```txt
    ibmcloud login
    ```
    {: pre}

3. Target the [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#registry_regions) where you want to enable metrics by running the [`ibmcloud cr region-set`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_region_set) command. Replace `REGION` with the name of the [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#registry_regions_local).

    ```txt
    ibmcloud cr region-set REGION
    ```
    {: pre}

4. Check whether metrics are already enabled for your account by running the following [`ibmcloud cr platform-metrics`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#ic_cr_platform_metrics) command. This command also displays the registry that the result applies to.

    ```txt
    ibmcloud cr platform-metrics --status
    ```
    {: pre}

5. Enable platform metrics by running the following `ibmcloud cr platform-metrics` command. It can take up to 30 minutes for your metrics to become effective.

    ```txt
    ibmcloud cr platform-metrics --enable
    ```
    {: pre}

    If you want to target a different [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#registry_regions), run the [`ibmcloud cr region-set`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_region_set) command.

## Locations of platform metrics
{: #registry_monitor_locations}

You can configure one monitoring instance in each region to collect platform metrics for IBM Cloud Container Registry. The following tables list the locations where metrics can be collected if you enable collection of Container Registry service metrics in that region.

| Locations in Americas | Platform metrics 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 metrics in Americas locations" caption-side="bottom"}
{: #table_registry_monitor_collect_service_metrics_americas}

| Locations in Asia Pacific | Platform metrics 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 metrics in Asia-Pacific locations" caption-side="bottom"}
{: #table_registry_monitor_collect_service_metrics_ap}

| Locations in Europe | Platform metrics 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 metrics in Europe locations" caption-side="bottom"}
{: #table_registry_monitor_collect_service_metrics_europe}

| Location for Global | Platform metrics available |
| ------------------- | -------------------------- |
| `Global` | [Yes]{: tag-green} |
{: caption="The automatic collection of Container Registry service metrics for Global" caption-side="bottom"}
{: #table_registry_monitor_collect_service_metrics_global}

For more information about where to see Container Registry metrics, see [Where to look for metrics](#registry_monitor_ui).

For more information about the locations where IBM Cloud services are enabled to send metrics to IBM Cloud Monitoring, see [IBM Cloud services by location](https://cloud.ibm.com/docs/monitoring?topic=monitoring-cloud_services_locations&format=markdown).

## Where to look for metrics
{: #registry_monitor_ui}

### Monitoring metrics
{: #registry_monitor_ui_at}

The [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&format=markdown#registry_regions) in which a Container Registry or a Vulnerability Advisor metric is available corresponds to the region of the Container Registry that generated the metric.

The following table shows the location of Monitoring metrics.

| Region for your account's registry | Region that was formerly known as | Domain name of your registry | Location of Monitoring metrics |
| ---------------------------------- | --------------------------------- | ---------------------------- | --------------------------------------------------- |
| `au-syd` | `ap-south` | `au.icr.io` | `Sydney (au-syd)` |
| `br-sao` | Not applicable | `br.icr.io` | `Sao Paulo (br-sao)` |
| `ca-mon` | Not applicable | `ca2.icr.io` | `Montreal (ca-mon)` |
| `ca-tor` | Not applicable | `ca.icr.io` | `Toronto (ca-tor)` |
| `eu-de` | `eu-central` | `de.icr.io` | `Frankfurt (eu-de)` |
| `eu-es` | Not applicable | `es.icr.io` | `Madrid (eu-es)` |
| `eu-gb` | `uk-south` | `uk.icr.io` | `London (eu-gb)` |
| `in-che` | Not applicable | `in.icr.io` | `Chennai - Airtel (in-che)` |
| `in-mum` | Not applicable | `in2.icr.io` | `Mumbai - Airtel (in-mum)` |
| `jp-osa` | Not applicable | `jp2.icr.io` | `Osaka (jp-osa)` |
| `jp-tok` | `ap-north` | `jp.icr.io` | `Tokyo (jp-tok)` |
| `us-south` | Not applicable | `us.icr.io` | `Dallas (us-south)` |
{: caption="Location of Monitoring metrics" caption-side="bottom"}
{: #table_registry_monitor_metrics_location}

The following table shows the location of global registry Monitoring metrics.

| Registry | Global registry | Location of Monitoring metrics |
| -------- | --------------- | --------------------------------------------------- |
| `Global` | `icr.io` | `Washington DC (us-east)` |
{: caption="Location of global registry Monitoring metrics" caption-side="bottom"}
{: #table_registry_monitor_metrics_location_global}

## Viewing metrics
{: #registry_view_metrics}

To monitor Container Registry metrics, you must start the Monitoring UI instance that is enabled for platform metrics in the region where you are using Container Registry.
{: important}

### Starting the Monitoring UI from the Observability page
{: #registry_view_metrics_opt2}

To start the Monitoring UI from the Observability page, complete the following steps:

1. [Start the Monitoring UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown).
2. Select **DASHBOARDS**.
3. In the **Default Dashboards** section, expand **IBM**.
4. Choose the Container Registry dashboard from the list. Available dashboards are **Container Registry Usage** and **Container Registry Quota Usage**. For more information about predefined dashboards, see [Predefined dashboards](#registry_dashboards_dictionary).

Next, change the scope or make a copy of the Default dashboard so that you can monitor your account in Container Registry. For more information, see [Working with dashboards](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboards&format=markdown).

## Predefined dashboards
{: #registry_dashboards_dictionary}

The following table outlines the predefined monitoring dashboards that you can use to monitor Container Registry metrics.

| Dashboard name | Description | Default dashboard |
| -------------- | ----------- | ----------------- |
| Container Registry Usage | A dashboard that you can use to visualize the traffic usage and storage usage. Traffic usage is the sum of bytes from image pulls from your Container Registry namespaces in the current billing period. Storage usage is the sum of bytes of images in your Container Registry namespaces. | [Yes]{: tag-green} |
| Container Registry Quota Usage | A dashboard that you can use to visualize the traffic usage and storage usage and compare the data to your quotas, if set. Visible only to those accounts that have finite quotas. The **Container Registry Quota Usage** dashboard is available only if you enable metrics and you have both a storage and a traffic quota set. | [No]{: tag-red} |
{: caption="Predefined dashboards" caption-side="bottom"}
{: #table_registry_monitor_dashboards_predefined}

The predefined dashboards can't be changed. You can copy any predefined dashboard so that you can change it to suit your requirements. For more information, see [Working with dashboards](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboards&format=markdown).
{: important}

When you start your dashboard, some metrics might display a `Data Load Error` warning icon. This warning is because more time is required to create the data. When data is available, the warning sign goes away, and the metric is populated. You might also need to change the resolution period.
{: note}

## Platform metrics
{: #metrics}

| Metric Name | Information |
| ----------- | ----------- |
| [`Pull Traffic`](#ibm_containerregistry_pull_traffic) | The account's pull traffic in the current month. |
| [`Pull Traffic Quota`](#ibm_containerregistry_pull_traffic_quota) | The account's pull traffic quota. |
| [`Storage Quota`](#ibm_containerregistry_storage_quota) | The account's storage quota. |
| [`Storage`](#ibm_containerregistry_storage) | The account's storage usage. |
{: caption="Metrics available by plan names" caption-side="bottom"}
{: #table_registry_monitor_metrics_plan}

### `Pull Traffic`
{: #ibm_containerregistry_pull_traffic}

The account's pull traffic in the current month.

| Metadata | Description |
| -------- | ----------- |
| `Metric Name` | `ibm_containerregistry_pull_traffic` |
| `Metric Type` | `gauge` |
| `Value Type` | `byte` |
{: caption="Pull Traffic metric metadata" caption-side="bottom"}
{: #table_registry_monitor_metrics_pull_traffic}

### `Pull Traffic Quota`
{: #ibm_containerregistry_pull_traffic_quota}

The account's pull traffic quota.

| Metadata | Description |
| -------- | ----------- |
| `Metric Name` | `ibm_containerregistry_pull_traffic_quota` |
| `Metric Type` | `gauge` |
| `Value Type` | `byte` |
{: caption="Pull Traffic Quota metric metadata" caption-side="bottom"}
{: #table_registry_monitor_metrics_pull_traffic_quota}

### `Storage Quota`
{: #ibm_containerregistry_storage_quota}

The account's storage quota.

| Metadata | Description |
| -------- | ----------- |
| `Metric Name` | `ibm_containerregistry_storage_quota` |
| `Metric Type` | `gauge` |
| `Value Type` | `byte` |
{: caption="Storage Quota metric metadata" caption-side="bottom"}
{: #table_registry_monitor_metrics_storage_quota}

### `Storage`
{: #ibm_containerregistry_storage}

The account's storage usage.

| Metadata | Description |
| -------- | ----------- |
| `Metric Name` | `ibm_containerregistry_storage` |
| `Metric Type` | `gauge` |
| `Value Type` | `byte` |
{: caption="Storage metric metadata" caption-side="bottom"}
{: #table_registry_monitor_metrics_storage}