Azure Functions
Overviewβ
Azure functions is a serverless plateform that allows to easily write and deploy code reacting to events occuring in any Azure or 3rd party services.
The Centreon Monitoring Connector Azure Functions can rely on Azure API or Azure CLI to collect the metrics related to the Functions service.
Monitoring Connector Assetsβ
Monitored Objectsβ
- Azure Functions instances
Discovery rulesβ
The Centreon Monitoring Connector Azure Functions 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 Functions:
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β
- App-Usage
- Cpu-Time
- Data
- Executions
- File-System
- Gc-Usage
- Health
- Http-Requests
- IO-Operations
- Memory
- Response-Time
- Status
Metric Name | Description | Unit |
---|---|---|
appservice.connections.count | The number of bound sockets existing in the sandbox | Count |
appservice.assemblies.current.count | The current number of assemblies loaded across all AppDomains in this application | Count |
appservice.handle.count | The total number of handles currently open by the app process | Count |
appservice.thread.count | The number of threads currently active in the app process | Count |
appservice.appdomains.count | The current number of AppDomains loaded in this application | Count |
appservice.appdomains.unloaded.count | The total number of AppDomains unloaded since the start of the application | Count |
Metric Name | Description | Unit |
---|---|---|
appservice.cpu.consumed.seconds | The amount of CPU consumed by the app in seconds | s |
Metric Name | Description | Unit |
---|---|---|
appservice.data.in.bytes | The amount of incoming bandwidth consumed by the app | B |
appservice.data.out.bytes | The amount of outgoing bandwidth consumed by the app | B |
Metric Name | Description | Unit |
---|---|---|
functions.executions.count | The number of function exectution | Count |
functions.executions.units.count | The number of functon execution units | Count |
Metric Name | Description | Unit |
---|---|---|
appservice.filesystem.usage.bytes | Filesystem quota consumed by the app | B |
Metric Name | Description | Unit |
---|---|---|
appservice.gc.gen0.count | The number of times the generation 0 objects are garbage collected since the start of the app process | Count |
appservice.gc.gen1.count | The number of times the generation 1 objects are garbage collected since the start of the app process | Count |
appservice.gc.gen2.count | The number of times the generation 2 objects are garbage collected since the start of the app process | Count |
Status Name | Description |
---|---|
status | Current operational status |
summary | Last related status message |
Metric Name | Description | Unit |
---|---|---|
appservice.http.request.count | The total number of requests regardless of their resulting HTTP status code | Count |
appservice.http.request.queue.count | The number of requests in the application request queue | Count |
appservice.htpp.request.XXX.count | The count of requests resulting in an HTTP status code = XXX | Count |
Metric Name | Description | Unit |
---|---|---|
appservice.bytes.other.bytespersecond | The rate at which the app process is issuing bytes to I/O operations that don't involve data | B/s |
appservice.operations.other.bytespersecond | The rate at which the app process is issuing I/O operations that aren't read or write operations | B/s |
appservice.bytes.read.bytespersecond | The rate at which the app process is reading bytes from I/O operations | B/s |
appservice.operations.read.bytespersecond | The rate at which the app process is issuing read I/O operations | B/s |
appservice.bytes.write.bytespersecond | The rate at which the app process is writing bytes to I/O operations | B/s |
appservice.operations.write.bytespersecond | The rate at which the app process is issuing write I/O operations | B/s |
Metric Name | Description | Unit |
---|---|---|
appservice.memory.average.usage.bytes | The average amount of memory used by the app | B |
appservice.memory.usage.bytes | The current amount of memory used by the app | B |
appservice.memory.privatebytes.usage.bytes | The amount of memory allocated allocated by the app process that can't be shared with other processes | B |
Metric Name | Description | Unit |
---|---|---|
appservice.http.response.time.seconds | The time taken for the app to serve requests | s |
Metric Name | Description | Unit |
---|---|---|
appservice.status.count | Health check status | Count |
Prerequisitesβ
To get data from Azure Services, following methods are available:
- Azure API ('api')
- Azure CLI ('azcli')
Centreon recommends to use the API instead of the CLI for the following reasons:
- API is much more efficient by avoiding CLI binary execution
- API supports application authentication while CLI does not (yet)
- Azure Monitor API
- Azure AZ CLI
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.
To use the 'azcli' custom mode, install the required packages on every Centreon poller expected to monitor Azure Resources using CLI:
- The CLI needs at least Python version 2.7 (https://github.com/Azure/azure-cli/blob/dev/doc/install_linux_prerequisites.md).
On RPM-Based distributions, use the command below to install it using root or 'sudo':
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
sudo echo -e "[azure-cli]\nname=Azure CLI\nbaseurl=https://packages.microsoft.com/yumrepos/azure-cli\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" > /etc/yum.repos.d/azure-cli.repo
sudo yum install azure-cli
Then, use the centreon-engine account to obtain a token using command below:
su - centreon-engine
az login
The shell will output this message including an authentication code:
*To sign in, use a web browser to open the page https://microsoft.com/devicelogin*
*and enter the code CWT4WQZAD to authenticate.*
Go to https://microsoft.com/devicelogin and enter the code.
Connect using a monitoring service account, as a result, the shell should prompt information below:
[
{
"cloudName": "AzureCloud",
"id": "0ef83f3a-d83e-2039-d930-309df93acd93d",
"isDefault": true,
"name": "N/A(tenant level account)",
"state": "Enabled",
"tenantId": "0ef83f3a-03cd-2039-d930-90fd39ecd048",
"user": {
"name": "email@mycompany.onmicrosoft.com",
"type": "user"
}
}
]
Credentials are now stored locally in the .accessTokens.json file so the Plugin can use it.
Setupβ
- Online License
- Offline License
- Install the Centreon package on every Centreon poller expected to monitor Azure Functions resources:
yum install centreon-plugin-Cloud-Azure-Compute-Functions-Api
- On the Centreon Web interface, install the Azure Functions Centreon Monitoring Connector on the Configuration > Monitoring Connectors Manager page
- Install the Centreon package on every Centreon poller expected to monitor Azure Functions resources:
yum install centreon-plugin-Cloud-Azure-Compute-Functions-Api
- Install the Centreon Monitoring Connector RPM on the Centreon Central server:
yum install centreon-pack-cloud-azure-compute-functions.noarch
- On the Centreon Web interface, install the Azure Functions Centreon Monitoring Connector on the Configuration > Monitoring Connectors 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-Compute-Functions-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:
- Azure Monitor API
- Azure AZ CLI
Mandatory | Nom | Description |
---|---|---|
X | AZURECUSTOMMODE | Custom mode 'api' |
X | AZURESUBSCRIPTION | Subscription ID |
X | AZURETENANT | Tenant ID |
X | AZURECLIENTID | Client ID |
X | AZURECLIENTSECRET | Client secret |
X | AZURERESOURCE | Id of the Functions instance |
Mandatory | Nom | Description |
---|---|---|
X | AZURECUSTOMMODE | Custom mode 'azcli' |
X | AZURESUBSCRIPTION | Subscription ID |
X | AZURERESOURCE | Id of the Functions 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_compute_functions_api.pl \
--plugin=cloud::azure::compute::functions::plugin \
--mode=cpu-time \
--custommode=api \
--subscription='xxxxxxxxx' \
--tenant='xxxxxxxxx' \
--client-id='xxxxxxxxx' \
--client-secret='xxxxxxxxx' \
--resource='APP01' \
--resource-group='xxxxxxxxx' \
--timeframe='900' \
--interval='PT5M' \
--aggregation='Total' \
--warning-cpu-time='1' \
--critical-cpu-time='2'
Expected command output is shown below:
OK: Instance 'APP01' Statistic 'total' Metrics CPU Time: 0.08s | 'APP01~total#appservice.cpu.consumed.seconds'=0.08s;;;0;
The command above checks the Cpu-Time of an Azure Functions instance using the 'api' custom-mode
(--plugin=cloud::azure::compute::functions::plugin --mode=cpu-time --custommode=api
).
This Functions instance is identified by its id (--resource='APP01'
) 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 Cpu-time is reported as over 1
(--warning-cpu-time='1'
) and a CRITICAL alarm over 2 (--critical-cpu-time='2'
).
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_compute_functions_api.pl \
--plugin=cloud::azure::compute::functions::plugin \
--mode=cpu-time \
--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.