Azure Monitor for containers is now available
Published date: 11 December, 2018
Azure Monitor for containers, now generally available, monitors the health and performance of Kubernetes clusters hosted on Azure Kubernetes Service (AKS). Since the launch of the preview of this service at Build (May 2018), there has been a lot of excitement from customers about the new capabilities, such as the ability to enable monitoring as soon as you create an AKS cluster. It’s also now possible to get all the monitoring telemetry in a centralized location in Azure without having to sign into containers or rely on other tools. Since the preview, several new capabilities have been added including:
- Multi-cluster view—The multi-cluster view discovers all AKS clusters across subscriptions, resource group, and workspaces, and provides you a health roll up view. You can even discover clusters that aren’t being monitored and start monitoring them with just few clicks.
- Performance grid view—To investigate further, drill down to performance grid view that shows the health and performance of your nodes, controllers, and containers. From the node view tab, it’s easy to spot the noisy neighbor issue on the pod and drill further to see the controller it’s part of. In addition, see the controller limits, request setting, and actual usage, and determine if you’ve configured your controller correctly. Continue investigating by looking at the Kubernetes event logs associated to that controller.
- Live debugging—With live logs, you get a real time, live stream of your container logs directly in your Azure portal to help you interactively troubleshoot issues. You can pause the live stream and search within the log file for errors or issues. Unlike the Azure Monitor logs, the live stream data is ephemeral and is meant for real time troubleshooting.
- Onboarding—In addition to the Azure portal, there are now more ways for you to automate onboarding Azure Monitor for containers: use Azure CLI (a single command), ARM template, and Terraform.
To learn more, read this blog post and our documentation.