As enterprises start using Kubernetes, they would need all the capabilities they leverage today for virtual machines. Starting from discovering the Kubernetes clusters, creating an inventory, defining relationships, and finally collecting all the key metrics and events to provide full visibility.
Some of the key use cases that the vRealize Operations and Kubernetes integration support, are listed here.
Automatic Discovery and Monitoring of Kubernetes Clusters
For administrators, the biggest benefit of this integration is that they can automatically configure monitoring for Kubernetes clusters as they are deployed by the provisioning system such as Tanzu Kubernetes Grid Integrated Service or Tanzu Mission Control. This also takes care of authentication for them and hence there is zero overhead to manage these environments. The clusters get added as they are provisioned and removed as they are decommissioned.
Kubernetes Inventory & Relationships
The integration allows the administrator to quickly get a full inventory of all the key Kubernetes constructs. This includes list of Kubernetes clusters deployed across all the environments, list of Namespaces that are deployed by the developers, a list of Kubernetes nodes and finally a list of replica sets, services, pods, and containers. With the exhaustive inventory that is collected every five minutes, administrators can easily report on this inventory using the powerful reporting capability of vRealize Operations. This inventory is also related automatically to provide a full stack topology from container to disk. With such a topology, administrators can easily correlate applications to infrastructure and find root cause of problems brewing in the environment.
After the inventory and relationships are available all the key metrics are automatically called and published for the administrators to consume. Based on industry best practices, out of the box content such as Alerts, Dashboards, and Reports are supplied with this integration to get started with monitoring of all the KPIs associated with a Kubernetes environment. The metrics collected through this includes both container and pod infrastructure and application metrics from the containers that can be easily ingested into vRealize Operations using the Prometheus integration.
Kubernetes Troubleshooting and Root Cause Analysis
While Kubernetes works based on the desired state configuration and always tries to ensure application performance and availability, there are scenarios where underlying infrastructure and applications mis-behave and results in performance or availability issues. In such a situation, it is important for administrators to have a way to troubleshoot the scope of related objects in a given period of time. vRealize Operations Troubleshooting Workbench allows the administrators to define a scope based on relations and define a time period for troubleshooting that scope. With these inputs, the Workbench automatically finds the potential evidences that are signals one must observe to arrive at the root cause. The scope-based Metric Correlation is another feature within the Workbench that can find the positive and negative correlations to an anomalous metric across a full scope to find the needle in the haystack.