You are here
404: Not Found
Included in the Cloud - Azure Opspack
Host Template: Cloud - Azure - Container Service Managed Clusters
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.
This Host Template 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.
This Host Template includes the following Service Checks:
|Service Check Name||Description||Default Thresholds (Warning, Critical)||UOM|
|Azure - Kube Node - Allocatable CPU Cores||Total number of available cpu cores in a managed cluster [Default Timespan = 5mins, Granularity = 5mins]||N/A||N/A|
|Azure - Kube Node - Allocatable Memory||Total amount of available memory in a managed cluster [Default Timespan = 5mins, Granularity = 5mins]||N/A||B|
|Azure - Kube Node - Status Condition||Statuses for various node conditions [Default Timespan = 5mins, Granularity = 5mins]||N/A||N/A|
|Azure - Kube - Pods Ready||Number of pods in Ready state [Default Timespan = 5mins, Granularity = 5mins]||N/A||N/A|
To use this Host Template you will need to provide access to the subscription you wish to monitor
Navigate to the Subscriptions section and select your Subscription.
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
Repeat these steps for each subscription you wish to monitor.
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.
Step 1: Add this Host Template
Add the Cloud - Azure - Container Service Managed Clusters Host Template to your Opsview Monitor host. If the resource you're monitoring has no hostname or public IP, then open the Advanced settings pane and 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 Template
The Service Checks in this Host Template use the following variables, and they will be added to your Opsview Monitor instance when you import the Opspack:
The Value is not used and therefore can be set to anything. Override the arguments with your Azure Credentials.
| Parameter | Position in Variable | Name | Description |
| --subscription-id | Arg1 | Subscription ID | The Subscription ID of your Azure Subscription |
| --client-id | Arg2 | Client ID | The Client ID of your Azure Subscription |
| --secret-key | Arg3 | Secret Key | The Secret Key of your Azure Subscription |
| --tenant-id | Arg4 | Tenant ID | The Tenant ID of your Azure Subscription |
The Value is not used and therefore can be set to anything. Override the arguments with your Azure Resource Details.
|Parameter||Position in Variable||Name||Description|
|--resource-group||Arg1||Resource Group||Name of the Azure resource group to be monitored|
|--resource-name||Arg2||Resource Name||Name of the Azure resource to be monitored|
For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.
For mode-specific help, run the plugin with the
-h -m <mode> flags. This will list the required and optional Variable Arguments for that mode.
The appropriate mode for each Service Check is listed here:
|Service Check Name||Mode|
|Azure - Kube Node - Allocatable CPU Cores||
|Azure - Kube Node - Allocatable Memory||
|Azure - Kube Node - Status Condition||
|Azure - Kube - Pods Ready||
Step 3: Apply changes and the system will now be monitored
ODI-3806 Cloud Azure Opspack
Initial release for Cloud Azure Opspack