More than anything else, Kubernetes troubleshooting relies on the ability to quickly contextualize the problem with what’s happening in the rest of the cluster. As complicated as this may sound, SPEED is really the name of the game. After all, more often than not, you will be conducting your investigation under the glow of fires burning bright in production.
Getting relevant context quickly and seeing things holistically is exactly what Komodor was created for. It is also the reason why we keep expanding our roster with new features that offer on-hand access to new kinds of valuable troubleshooting insights.
Komodor’s ‘Node Status’ view is our latest feature, built to easily pinpoint correlations between service or deployment issues and changes in the underlying node infrastructure. With this new view you will be able to:
- Instantly see service-to-node associations
- Correlate service and node health issues (e.g., in case of service degradation)
- Be aware of node capacity allocations, restrictions, and limitations
- Identify “noisy neighbors” that use up cluster resources
- Keep track of changes in managed clusters (e.g., EKS scale down)
- Have historical node-level event data (unresponsive, deleted, etc) to discover and future-proof against deep and recurring issues
Get node-level information for each running service
Having access to this additional information adds a new dimension to the understanding of application-level issues. More importantly, having it available just a click away speeds up the remediation, allowing responders to quickly identify infrastructure-related issues.