Skip to main content

Azure Event Grid

Overview​

Azure Event Grid Service simplifies event-based apps by managing routing of all events from any source to any destination. Designed for high availability, consistent performance, and dynamic scale, Event Grid lets clients focus on their app logic rather than infrastructure.

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

Monitoring Connector Assets​

Monitored Objects​

  • Azure Event Grid instances

Discovery rules​

The Centreon Monitoring Connector Azure Event Grid 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 Event Grid:

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​

Metric nameDescription
eventgrid.matched.events.countNumber of matched Events
eventgrid.unmatched.events.countNumber of unmatched Events
eventgrid.dropped.events.countNumber of dropped Events
eventgrid.deadlettered.events.countNumber of dead Lettered Events

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 Event Grid resources:
yum install centreon-plugin-Cloud-Azure-Integration-EventGrid-Api
  1. On the Centreon Web interface, install the Azure Event Grid 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-Integration-EventGrid-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 Event Grid instance
XAZURERESOURCETYPEType of the Event Grid 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_integration_eventgrid_api.pl \
    --plugin=cloud::azure::integration::eventgrid::plugin \
    --mode=events \
    --custommode=api \
    --subscription='xxxxxxxxx' \
    --tenant='xxxxxxxxx' \
    --client-id='xxxxxxxxx' \
    --client-secret='xxxxxxxxx' \
    --resource='EVENT01' \
    --resource-group='xxxxxxxxx'
    --resrouce-type='domains' \
    --aggregation='Total' \
    --timeframe='900' \
    --interval='PT5M' \
    --warning-matched-events='80' \
    --critical-matched-events='90'

Expected command output is shown below:

OK: Instance 'EVENT01' Statistic 'total' Metrics Matched Events: 0.00, Dead Lettered Events: 0.00, Dropped Events: 0.00 | 'EVENT01~total#eventgrid.matched.events.count'=0.00;0:80;0:90;0; 'EVENT01~total#eventgrid.deadlettered.events.count'=0.00;;;0; 'EVENT01~total#eventgrid.dropped.events.count'=0.00;;;0;

The command above checks the events of an Azure Event Grid instance using the 'api' custom-mode (--plugin=cloud::azure::integration::eventgrid::plugin --mode=events --custommode=api). This Event Grid instance is identified by its id (--resource='EVENT01'), its type (--resrouce-type='domains') 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 total (--aggregation='total') of values on 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 matched events count is reported as over 800 (--warning-matched-events='80') and a CRITICAL alarm over 900 (--critical-matched-events='90').

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_integration_eventgrid_api.pl \
    --plugin=cloud::azure::integration::eventgrid::plugin \
    --mode=events \
    --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.