OpenNMS monitoring and data collection from the Azure REST API
Description
The Azure cloud platform contains an extensive REST API that provides comprehensive information about all the services and Resources an organisation has deployed to Azure.
Information retrieved from the API is in JSON format.
The Azure REST API has some challenges that would need to be solved:
Every GET/PUT/POST request requires an access token to be passed in as a HTTP header
access token expires after 1 hour and needs to be refreshed
There is an API function to obtain the required access token, but it requires some pre-requisites to be set up in Azure specified in the above link
There is Azure side security considerations for an organisation when setting up the access for OpenNMS as full management functionality is available through the REST API, and access levels for OpenNMS should potentially be limited to read only, unless automated actions to be triggered by OpenNMS. An organisation with multiple subscriptions may want to separate access tokens per Subscription.
Would be a great benefit to be able to import nodes from Azure.
John Blackburn May 14, 2018 at 5:55 AM
Initially, the Metric that is most useful to me is related to Azure B series servers which have a CPU cap, but accumulate credit when their CPU utilisation is below the cap, and they can exceed the cap if they have credit available. So to be able to monitor CPU Credits Consumed, and CPU Credits Remaining, and to have OpenNMS alert on these would be useful.
The Azure cloud platform contains an extensive REST API that provides comprehensive information about all the services and Resources an organisation has deployed to Azure.
Information retrieved from the API is in JSON format.
Azure REST API documentation is located here:
https://docs.microsoft.com/en-us/rest/api/azure/
The Azure REST API has some challenges that would need to be solved:
Every GET/PUT/POST request requires an access token to be passed in as a HTTP header
access token expires after 1 hour and needs to be refreshed
There is an API function to obtain the required access token, but it requires some pre-requisites to be set up in Azure specified in the above link
There is Azure side security considerations for an organisation when setting up the access for OpenNMS as full management functionality is available through the REST API, and access levels for OpenNMS should potentially be limited to read only, unless automated actions to be triggered by OpenNMS. An organisation with multiple subscriptions may want to separate access tokens per Subscription.