Skip to main content

Azure Traffic Manager

Pack Assets​


The Centreon Monitoring Connector Azure Traffic Manager brings 2 different host templates:

  • Cloud-Azure-Network-TrafficManager-custom
  • generic-dummy-host-custom

It brings the following service templates:

Service AliasService TemplateService DescriptionDefault
Endpoint-StatusCloud-Azure-Network-TrafficManager-EndpointStatus-ApiCheck Endpoints state for an Azure Traffic Manager ProfileX
HealthCloud-Azure-Network-TrafficManager-Health-ApiCheck Traffic Manager Profile availabilityX
QueriesCloud-Azure-Network-TrafficManager-Queries-ApiCheck queries number per second per Endpoint for a Azure Traffic Manager ProfileX

Discovery rules​

The Centreon Monitoring Connector Azure Traffic Manager 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 Traffic Manager Profile:


This discovery feature is only compatible with the api custom mode. azcli is not supported.

More information about discovering hosts automatically is available on the dedicated page.

Collected metrics & status​

Metric NameUnit


Please find all the prerequisites needed for Centreon to get information from Azure on the dedicated page.


  1. Install the package on every Centreon poller expected to monitor Azure Traffic Manager resources:
yum install centreon-plugin-Cloud-Azure-Network-TrafficManager-Api
  1. On the Centreon web interface, on page Configuration > Monitoring Connector Manager, install the Azure Traffic Manager Centreon Monitoring Connector.



  • Log into Centreon and add a new host through Configuration > Hosts.
  • In the IP Address/DNS field, set the following IP address:
  • Aplly the Cloud-Azure-Network-TrafficManager-custom template to the host.
  • Once the template is applied, fill in the corresponding macros. Some macros are mandatory. These mandatory macros differ depending on 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/XXXXX/XXXXX/<resource_name>) in AZURERESOURCE
  • Resource name in the AZURERESOURCE macro, and resource group name in the AZURERESOURCEGROUP macro.
XAZURERESOURCEID or name of the Azure Traffic Manager resource
XAZURERESOURCEGROUPResource group name 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's 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::network::trafficmanager::plugin \
--mode=queries \
--custommode='api' \
--resource='' \
--resource-group='' \
--subscription='' \
--tenant='' \
--client-id='' \
--client-secret='' \
--proxyurl='' \
--filter-metric='' \
--filter-dimension='' \
--timeframe='900' \
--interval='PT5M' \
--aggregation='Total' \
--warning-queries-persecond='' \
--critical-queries-persecond='' \

The expected command output is shown below:

OK: Queries per second By Endpoint : 9000 | 'trafficmanager.queries.persecond'=9000;;;0; 

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

/usr/lib/centreon/plugins// \
--plugin=cloud::azure::network::trafficmanager::plugin \
--mode=queries \

All available modes can be displayed by adding the --list-mode parameter to the command:

/usr/lib/centreon/plugins// \
--plugin=cloud::azure::network::trafficmanager::plugin \


Please find the troubleshooting documentation for the API-based plugins in this chapter.