Operations | Monitoring | ITSM | DevOps | Cloud

As IT organizations enter 2026, many of the assumptions around monitoring and observability have already been tested. Throughout 2025, infrastructure teams made it clear that visibility alone is not enough. Alerts without context, short data retention, and fragmented tools limited teams’ ability to explain behavior, validate changes, and plan with confidence. This article looks at what emerged from those experiences and how observability expectations continue to shift.

In this article, we’ll show how easy it is to send custom application metrics directly to MetricFire's public carbon endpoint. We’ll build a small Flask application, emit a handful of practical metrics, and generate local traffic to demonstrate how quickly meaningful data can flow from your code to your dashboards.

Serverless platforms have revolutionized the way developers build and deploy APIs, eliminating the need to manage servers or underlying infrastructure. With serverless, you can focus entirely on your application logic and let the platform handle scaling, availability, and maintenance. Scaleway Serverless Functions is a flexible serverless platform that makes it easy to deploy lightweight APIs and background jobs in the cloud.

There’s a moment every engineer knows. An AI suggests a fix, it looks reasonable,maybe even obvious, but production is on the line and you hesitate before clicking execute. There’s a big difference between an AI that can recommend an action and one you’re willing to let take that action. All it takes is one bad call, one kubectl command that makes things worse, and suddenly every automated suggestion is a potential liability instead of a help.

Have you ever asked yourself, what is the fastest way to turn a harmless Infrastructure as Code change into a production incident and an awkward postmortem? We did, and found that usually, it's from letting it through without any guardrails. Infrastructure guardrails in Infrastructure as Code (IaC) were once a nice-to-have. Today, they’re essential. Without clear boundaries and safety mechanisms, even well-designed IaC workflows can turn small mistakes into fast-moving, high-impact problems.