Operations | Monitoring | ITSM | DevOps | Cloud

Qovery unveils its new brand identity, reinforcing its mission to make DevOps simple, intuitive, and powerful. Discover how our DevOps automation platform simplifies infrastructure, scaling, security, and innovation across the full DevOps lifecycle.

As the Senior Manager of Finance & Accounting here at CloudZero, and with a career in FP&A that includes tenures at large public companies, I’ve spent a significant amount of time observing the interactions between the folks who plan the company’s budget and those who spend it. While engineering and operations teams focus on the execution side, my team ensures that the company has the resources required to make each endeavor a success.

An incident’s in progress. Services are slow, customers are frustrated, and your dashboards… look fine. At least, until you search for payment metrics and get 47 different names for the same signal. Suddenly, the real issue isn’t latency — it’s inconsistency. The OpenTelemetry project recently published a three-part series on naming conventions to solve exactly this problem.

Whether it’s streaming video, powering remote work, or supporting smart technologies, the ability to connect local users to the global internet is essential. But behind the scenes, a key infrastructure layer ensures that this digital experience runs smoothly: the middle mile. Middle mile networks serve as the critical bridge between the internet’s backbone and the local networks that deliver service to homes, businesses, and institutions.

Effective monitoring catches problems before users do, and with Promtail, Loki, and LogQL, it’s a lightweight, approachable option for any DevOps team. This guide shows how to monitor Docker itself (pull failures, restarts, health flaps) so you’ve got a baseline on container runtime health.

An essential part of software development, testing helps catch bugs and errors early, improves software quality, and ultimately prevents costly issues from being deployed to production. The effectiveness of software testing will remain uncertain until it can be measured and that is where code coverage comes in. Code coverage is a metric that tells developers what portion of their codebase is executed when specific tests are run.

Any company still running their own CI/CD, such as Jenkins, is paying a price. The question is which one: Each of these is extremely costly, and yet many software teams still host and run their own CI/CD for two reasons: tools like Jenkins are cheap or free, and hosting Jenkins on an AWS EC2 instance is often cheaper per minute than SaaS CI/CD services like Bitbucket Pipelines. Both reasons are true, but they’re also a trap.