The latest News and Information on Containers, Kubernetes, Docker and related technologies.
Overprovisioning or underprovisioning your Kubernetes resources can have significant consequences on both your budget and your app performance. By underprovisioning your Kubernetes infrastructure, you’ll end up with lagging, underperforming, unstable, or non-functional applications. On the opposite end of the spectrum, overprovisioning is a costly issue: Organizations spent almost $500 billion on cloud resources in 2022, yet an estimated 30% of those were wasted.
Nowadays, it is rather common to see companies adopt several monitoring solutions based on Prometheus, but this is not exempt from pain. A huge number of systems, applications, and third-party software are not instrumented to expose Prometheus metrics natively. Here is where Prometheus exporters come into play.
You'll notice that monitoring and logging don't appear on the list of core Kubernetes features. However, this is not due to the fact that Kubernetes does not offer any sort of logging or monitoring functionality at all. It does, but it’s complicated. Kubernetes’ kubectl tells us all about the status of the different objects in a cluster and creates logs for certain types of files. But ideally speaking, you won't find a native logging solution embedded in Kubernetes.