# Monitoring Kubernetes in Production
URL:: https://sysdig.com/blog/monitoring-kubernetes/
Author:: Carlos Arilla
## Highlights
> As described on [Site Reliability Engineering – How Google Runs Production Systems](https://landing.google.com/sre/book/chapters/practical-alerting.html), “We need monitoring systems that allow us to alert for high-level service objectives, but retain the granularity to inspect individual components as needed.” ([View Highlight](https://read.readwise.io/read/01gyw7hqsfzakjpfr232zbr1yx))
> It’s hard to see what’s inside containers ([View Highlight](https://read.readwise.io/read/01gyw7hyg4twg3a4t7z7jj4vd9))
> Containers are ephemeral, meaning once the container dies everything inside is gone. You cannot SSH or look at logs, and most of the tools you’re used to using for troubleshooting are not installed. They are great for operations as we can package and isolate applications to deploy them in a consistent way everywhere, but at the same time, this makes them blackboxes which are hard to troubleshoot. This is why monitoring tools that provide granular visibility through system calls tracing allow you to see down to every process, file or network connection that happened inside a container to troubleshoot issues faster. ([View Highlight](https://read.readwise.io/read/01gyw7j6trs2zt0wac18hgqbtq))
---
Title: Monitoring Kubernetes in Production
Author: Carlos Arilla
Tags: readwise, articles
date: 2024-01-30
---
# Monitoring Kubernetes in Production
URL:: https://sysdig.com/blog/monitoring-kubernetes/
Author:: Carlos Arilla
## AI-Generated Summary
This monitoring Kubernetes how-to guide breaks down the details involved with monitoring applications running on Kubernetes in production.
## Highlights
> As described on [Site Reliability Engineering – How Google Runs Production Systems](https://landing.google.com/sre/book/chapters/practical-alerting.html), “We need monitoring systems that allow us to alert for high-level service objectives, but retain the granularity to inspect individual components as needed.” ([View Highlight](https://read.readwise.io/read/01gyw7hqsfzakjpfr232zbr1yx))
> It’s hard to see what’s inside containers ([View Highlight](https://read.readwise.io/read/01gyw7hyg4twg3a4t7z7jj4vd9))
> Containers are ephemeral, meaning once the container dies everything inside is gone. You cannot SSH or look at logs, and most of the tools you’re used to using for troubleshooting are not installed. They are great for operations as we can package and isolate applications to deploy them in a consistent way everywhere, but at the same time, this makes them blackboxes which are hard to troubleshoot. This is why monitoring tools that provide granular visibility through system calls tracing allow you to see down to every process, file or network connection that happened inside a container to troubleshoot issues faster. ([View Highlight](https://read.readwise.io/read/01gyw7j6trs2zt0wac18hgqbtq))