Skip to main content

Azure Front Door

Overview​

Azure Front Door is a global, scalable entry-point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications. With Front Door, you can transform your global consumer and enterprise applications into robust, high-performing personalized modern applications with contents that reach a global audience through Azure.

The Centreon Monitoring Connector Azure Front Door can rely on Azure API or Azure CLI to collect the metrics related to the Front Door service.

Monitoring Connector Assets​

Monitored Objects​

  • Azure Front Door instances
    • Backend-Health
    • Health
    • Latency
    • Requests
    • Size

Discovery rules​

The Centreon Monitoring Connector Azure Front Door 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 Front Door:

image

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

More information about the Host Discovery module is available in the Centreon documentation: Host Discovery

Collected metrics & status​

Metric NameDescriptionUnit
frontdoor.backend.health.percentageBackend Health Percentage%

Prerequisites​

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

Setup​

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

Configuration​

Host​

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

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

  • Select the Cloud-Azure-Network-FrontDoor-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:

MandatoryNomDescription
XAZURECUSTOMMODECustom mode 'api'
XAZURESUBSCRIPTIONSubscription ID
XAZURETENANTTenant ID
XAZURECLIENTIDClient ID
XAZURECLIENTSECRETClient secret
XAZURERESOURCEId of the Front Door instance

FAQ​

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

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

/usr/lib/centreon/plugins/centreon_azure_network_frontdoor_api.pl \
    --plugin=cloud::azure::network::frontdoor::plugin \
    --mode=latency \
    --custommode=api \
    --subscription='xxxxxxxxx' \
    --tenant='xxxxxxxxx' \
    --client-id='xxxxxxxxx' \
    --client-secret='xxxxxxxxx' \
    --resource='FRT001ABCD' \
    --resource-group='RSG1234' \
    --timeframe='900' \
    --interval='PT5M' \
    --aggregation='Average' \
    --warning-total-latency='800' \
    --critical-total-latency='900'

Expected command output is shown below:

OK: Instance 'FRT001ABCD' Statistic 'average' Metrics Total Latency: 24.31ms, Backend Request Latency: 17.46ms |
'FRT001ABCD~average#frontdoor.latency.total.milliseconds'=24.31ms;0:800;0:900;0; 'FRT001ABCD~average#frontdoor.latency.backend.milliseconds'=17.46ms;;;0;

The command above checks the latency of an Azure Front Door instance using the 'api' custom-mode (--plugin=cloud::azure::network::frontdoor::plugin --mode=latency --custommode=api). This Front Door instance is identified by its id (--resource='FRT001ABCD'), its associated group (--resource-group='RSG1234') and 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 calculated metrics are the average values (--aggregation='Average') of a 900 secondes / 15 min period (--timeframe='900') with one sample per 5 minutes (--interval='PT5M').

This command would trigger a WARNING alarm if the total latency time is reported as over 800ms (--warning-total-latency='800') and a CRITICAL alarm over 900ms (--critical-total-latency='900').

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

/usr/lib/centreon/plugins/centreon_azure_network_frontdoor_api.pl \
    --plugin=cloud::azure::network::frontdoor::plugin \
    --mode=latency \
    --help

Troubleshooting​

The Azure credentials have changed and the Plugin does not work anymore​

The Plugin is using a cache file to keep connection information and avoid an authentication at each call. If some of the authentication parameters change, you must delete the cache file.

The cache file can be found within /var/lib/centreon/centplugins/ folder with a name similar to azureapi<md5>_<md5>_<md5>_<md5>.

UNKNOWN: Login endpoint API returns error code 'ERROR_NAME' (add --debug option for detailed message)​

When I run my command I obtain the following error message: UNKNOWN: Login endpoint API returns error code 'ERROR_NAME' (add --debug option for detailed message).

It means that some parameters used to authenticate the API request are wrong. The 'ERROR_NAME' string gives some hints about where the problem stands.

As an example, if my Client ID or Client Secret are wrong, 'ERROR_DESC' value will be 'invalid_client'.

UNKNOWN: 500 Can't connect to login.microsoftonline.com:443​

This error message means that the Centreon Plugin couldn't successfully connect to the Azure Login API. Check that no third party device (such as a firewall) is blocking the request. A proxy connection may also be necessary to connect to the API. This can be done by using this option in the command: --proxyurl='http://proxy.mycompany:8080'.

UNKNOWN: No metrics. Check your options or use --zeroed option to set 0 on undefined values​

This command result means that Azure does not have any value for the requested period. This result can be overriden by adding the --zeroed option in the command. This will force a value of 0 when no metric has been collected and will prevent the UNKNOWN error message.