Monitoring Kubernetes resources
In the previous section, you learned all about monitoring from an overall observability perspective, in particular setting up certain tools and ensuring that they work for you. Now it’s time to go underneath the Kubernetes hood and begin to think about what can be monitored from a resource perspective. Remember, a Kubernetes resource (sometimes called an object) can be anything, from Services, to Ingress controllers, to Pods. Because of that, there’s a lot to monitor.
Think about it from this perspective. You’re running a Pod that’s running a container inside of the Pod. The Pod itself is running great. The container image works, with no CPU or memory issues, and all of the events state that the Pod is up and running successfully. However, there’s a problem – the binary (the app entry point) running inside of the container may be down, or not working as expected. Because of this, you need a way to truly see...
