You are here
404: Not Found
Cloud - Azure - Container Service Managed Clusters Opspack
Azure Container Service Managed Clusters allow you to quickly deploy production ready Kubernetes, DC/OS and Docker Swarm clusters. Azure Container Service manages hosted environments, making it quick and easy to deploy and manage containerised applications. It also eliminates the difficulty of ongoing operations and maintenance by provisioning, upgrading and scaling resources on demand without taking applications offline.
What You Can Monitor
This Opspack allows you to monitor all the metrics you need to efficiently run Azure Container Service Managed Clusters on Microsoft Azure. After installation, you'll be able to check the number of pods in the Ready state, the status of nodes, as well as the allocatable memory and CPU cores in the managed cluster.
|Host Template||Service Check||Description|
|Cloud - Azure - Container Service Managed Clusters||Azure - Kube Node - Allocatable CPU Cores||Total number of available cpu cores in a managed cluster [Default Timespan = 5mins, Granularity = 5mins]|
|Cloud - Azure - Container Service Managed Clusters||Azure - Kube Node - Allocatable Memory||Total amount of available memory in a managed cluster [Default Timespan = 5mins, Granularity = 5mins]|
|Cloud - Azure - Container Service Managed Clusters||Azure - Kube Node - Status Condition||Statuses for various node conditions [Default Timespan = 5mins, Granularity = 5mins]|
|Cloud - Azure - Container Service Managed Clusters||Azure - Kube - Pods Ready||Number of pods in Ready state [Default Timespan = 5mins, Granularity = 5mins]|
Opsview Monitor Version 6.0.0 (released 07 September 2018) or newer. Check Opsview Release Notes for the latest version of Opsview Monitor.
Setup Azure for Monitoring
To monitor your Azure environment, you need to configure it for monitoring. This requires Administrator access on Azure.
You need to retrieve the following credentials, which will allow Opsview Monitor access to the metrics for your Azure VM:
- Subscription ID
- Tenant/Directory ID
- Client/Application ID
- Secret Key
Follow the below steps to retrieve this information.
Step 1: Find Subscription ID
The Subscription ID can be found in the Subscriptions section under the All services section from the Azure dashboard.
Step 2 : Find the Tenant/Directory ID
The Tenant/Directory ID can be found in the Azure Active Directory under the Properties section from the Azure dashboard.
Step 3: Find the Client/Application ID for your application
You need to create and register your application if you haven't already. Use the following documentation from Microsoft: Create an Azure Active Directory application
The Client/Application ID can be found in Azure Active Directory under the App registrations section from the Azure dashboard.
Step 4: Generate the Secret Key for your application
You will need to create a Secret Key for your application, once this has been created its value will be hidden so save the value during creation.
To create the Secret Key, select your application from the list, select the Settings within your application and then select the Keys option.
There you can create a new key by adding the description and expiration period and the value will be generated.
Step 5: Provide access to the subscription you wish to monitor
Navigate to the Subscriptions section and select the Subscription you selected before.
In the Subscription to be monitored, click Access Control (IAM).
Then click the Add button, select the required role and select the application, once for each of the following roles: * Reader
If you are running more than one subscription these steps will need to be done for each one you wish to monitor.
Setup and Configuration
To configure and utilize this Opspack, you simply need to add the 'Cloud - Azure - Container Service Managed Clusters' Opspack to your Opsview Monitor system.
Step 1: Add the Host Template
Add the relevant Host Template (as listed in the Service Checks table above). If this is a resource that is applicable for a host check (has a valid hostname or IP) then you can fill in the Primary Hostname/IP field with this, and then open the Advanced section at the bottom and change the Host Check Command type to TCP Port 80 (HTTP). If the resource has no hostname or public IP, then change Host Check Command to Always assumed to be UP.
For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.
Step 2: Add and configure variables required for this host
Add 'AZURE_CREDENTIALS' to the host, then override the Subscription ID, Client ID, Secret Key and Tenant ID to match the values retrieved earlier.
You will require the following additional variable:
|Host Template||Variable Required|
|Cloud - Azure - Container Service Managed Clusters||AZURE_RESOURCE_DETAILS|
These can be filled out as follows:
For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.
Step 3: Apply changes and the system will now be monitored
Please note, it can take a long time for all the associated metrics to be made available via Azure. This means that these Service Checks may not return results if the Cluster resource was created recently. For some of the Cluster Metrics you may have to wait over 6 hours after creation.
ODI-3136 Re-release Azure opspacks
ODI-2057 Fixes and Improvements to Parameter handling
Improvements to user input verification and errors.
ODI-1747 Fixes and Improvements to Authentication Process
Improvements to Azure authentication error handling
ODI-1453 Initial Release of Azure Opspacks for Opsview Monitor 6.0
Initial release of Opspack to work with Opsview Monitor 6.0