Kubernetes has become a crucial tool in DevOps for scaling operations of containerized microservice architecture. However, managing deployment, scaling, upgrading, and updating of these services is not trivial, making automation essential. InfluxDB Cloud 2.0 adopted Kubernetes as part of its microservices architecture, but monitoring became an issue due to the ever-growing number of endpoints exposed by SREs and developers. The answer lies in sidecar deployment, where a scraper is contained within a pod, isolating its impact on other workloads. This approach solved the scaling issue without adding complexity or burden to operations. Additionally, Telegraf, a lightweight metrics collection agent deployed as a sidecar, monitors all exposed metrics by the application, service, or microservice, ensuring no impact on IT Operations or developers' needs for metrics. Furthermore, Telegraf's self-watch feature allows it to monitor its own performance and detect missing metrics, while its ability to limit tags and configure runtime settings empowers developers with observability and predictability. The key lesson learned is that scaling monitoring should not add complexity but rather empower developers with tools like Telegraf, ensuring monitoring does its job without burdening operations.