Skip to main content

Azure Container Registry


Azure Container Registry is a managed, private Docker registry service based on the open-source Docker Registry 2.0. Create and maintain Azure Container Registries to store and manage your private Docker container images and related artifacts.

The Centreon Plugin Azure Container Registry can rely on Azure API or Azure CLI to collect the metrics related to the ACR service.

Pack Assets​

Monitored Objects​

Available indicators and metrics:

  • Azure Container Registries
    • Storage-usage

Discovery rules​

The Centreon Pack Azure Container Registry includes a Host Discovery provider to automatically discover the Azure instances of a given subscription and add them to the Centreon configuration. This provider is named Microsoft Azure Container Registry:


This discovery feature is only compatible with the 'api' custom mode. 'azcli' is not supported. More information about the Host Discovery module is available in the Centreon documentation: Host Discovery

Collected metrics​

Metric NameDescriptionUnit usedB


To get data from Azure Services, the following methods are available:

* Azure API ('api') 
* Azure CLI ('azcli')

Centreon recommends to use the API instead of the CLI for the following reasons:

* the API is much more efficient because it avoids CLI binary execution
* the API supports application authentication while CLI does not (yet)

To use the 'api' custom mode, make sure to obtain the required information using the how-to below. Keep it safe until including it in a Host or Host Template definition.

  • Create an application in Azure Active Directory:

    • Log in to your Azure account.
    • Select Azure Active directory in the left sidebar.
    • Click on App registrations.
    • Click on + Add.
    • Enter Centreon as the application name (or any name of your choice), select application type (api) and sign-on-url.
    • Click on the Create button.
  • Get Subscription ID

    • Log in to your Azure account.
    • Select Subscriptions in the left sidebar.
    • Select whichever subscription is needed.
    • Click on Overview.
    • Copy the Subscription ID.
  • Get Tenant ID

    • Log in to your Azure account.
    • Select Azure Active directory in the left sidebar.
    • Click on Properties.
    • Copy the directory ID.
  • Get Client ID

    • Log in to your Azure account.
    • Select Azure Active directory in the left sidebar.
    • Click on Enterprise applications.
    • Click on All applications.
    • Select the application previously created.
    • Click on Properties.
    • Copy the Application ID.
  • Get Client secret

    • Log in to your Azure account.
    • Select Azure Active directory in the left sidebar.
    • Click on App registrations.
    • Select the application previously created.
    • Click on All settings.
    • Click on Keys.
    • Enter the key description and select the duration.
    • Click on Save.
    • Copy and store the key value. You won't be able to retrieve it after you leave this page.

Please make sure to assign the Monitoring Reader role to the application.


  1. Install the Centreon Plugin package on every Centreon poller expected to monitor Azure Container Registry resources:
yum install centreon-plugin-Cloud-Azure-Storage-ContainerRegistry-Api
  1. On the Centreon Web interface, install the Azure Container Registry Pack on the Configuration > Plugin Packs > Manager page.



  • Log into Centreon and add a new Host through "Configuration > Hosts".

  • In the IP Address/FQDN field, set the following IP address: ''.

  • Select the Cloud-Azure-Storage-ContainerRegistry-custom template to apply to the Host.

  • Once the template applied, some Macros marked as 'Mandatory' hereafter have to be configured. These mandatory Macros differ regarding the custom mode used.

Two methods can be used to set the Macros:

  • full ID of the Resource (/subscriptions/<subscription_id>/resourceGroups/<resourcegroup_id>/providers/Microsoft.ContainerRegistry/registries/<resource_name>) in AZURERESOURCE
  • Resource Name in AZURERESOURCE associated with Resource Group (in AZURERESOURCEGROUP) and Resource Type (in AZURERESOURCETYPE)
XAZURERESOURCEID or name of the Container Registry resource
AZURERESOURCEGROUPAssociated Resource Group if resource name is used

How to check in the CLI that the configuration is OK and what are the main options for ?​

Once the Plugin is installed, log into your Centreon Poller CLI using the centreon-engine user account (su - centreon-engine) and test the Plugin by running the following command:

/usr/lib/centreon/plugins/ \
--plugin=cloud::azure::storage::acr::plugin \
--mode=storage-usage \
--custommode='api' \
--subscription='xxxxxxxxx' \
--tenant='xxxxxxxxx' \
--client-id='xxxxxxxxx' \
--client-secret='xxxxxxxxx' \
--resource='ACR001ABCD' \
--aggregation='Total' \
--timeframe='3600' \
--interval='PT1H' \
--warning-storage-used='80000000000' \

Expected command output is shown below:

OK: Instance 'ACR001ABCD' Statistic 'total' Metrics Storage used: 74.86GB |

The command above checks the storage usage of an Azure Container Registry instance using the 'api' custom-mode (--plugin=cloud::azure::storage::acr::plugin --mode=storage-usage --custommode=api). This instance is identified by its id (--resource='ACR001ABCD') and its associated group (--resource-group='RSG1234'). The authentication parameters to be used with the custom mode are specified in the options (--subscription='xxxxxxxxx' --tenant='xxxxxxx' --client-id='xxxxxxxx' --client-secret='xxxxxxxxxx').

The fetched values are the total values (--aggregation='Total') of a single sample based on a 3600 seconds / 1 hour period (--timeframe='3600' --interval='PT1H').

This command would trigger a WARNING alarm if the storage usage is reported as over 80GB (--warning-storage-used='80000000000') and a CRITICAL alarm over 90GB (--critical-item-errors='90000000000').

All the available options for a given mode can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/ \
--plugin=cloud::azure::storage::acr::plugin \
--mode=storage-usage \


Please find all the troubleshooting documentation for the API-based Plugins in the dedicated chapter of the Centreon documentation.