Operations | Monitoring | ITSM | DevOps | Cloud

Being on call is an essential part of operating reliable distributed systems, but it comes with real human costs such as alert fatigue, sudden wakeups in the middle of the night, and the ongoing anxiety of what the next notification might bring. Many engineers know the feeling: Your phone lights up, a sound cuts through the silence, and your heart rate spikes before you’re even fully awake.

ClickHouse is widely used for large-scale analytics, but once it is running in production, it can be difficult to understand how query activity translates into resource usage. Engineers investigating performance issues often struggle to determine which queries consume the most memory, run most frequently, or cause spikes in load. In practice, engineers are left querying system.query_log, tailing server logs, and piecing together information after an incident.

March signified a very important period for the Konstruct team, where we were able to focus on something we’ve heard consistently from teams: reduce the time to value without compromising control. In the previous post, we walked through how Konstruct 0.1–0.3 established the core platform model, introduced templates, and expanded GitOps into something that can represent both infrastructure and applications. With 0.4, we’re taking a more opinionated step forward.

Secure messaging apps for healthcare workers are platforms designed to enable HIPAA-compliant communication, real-time collaboration and coordination, and urgent alerting across clinical teams for timely response. In modern hospitals, communication is no longer just about sending messages. It’s about ensuring the right person receives the right information and acts on it quickly.

At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.

We’ve spent the last few months listening to how teams are running InfluxDB 3 in the wild. The feedback was clear: as you scale, you need less “guesswork” and more control. Today’s release of InfluxDB 3.9 is our answer to that. As more teams move InfluxDB 3 into production, our focus has shifted toward the operational experience: how you manage the database at scale, how you ensure it remains secure, and how you provide a seamless experience for users.

The reason why I like writing recap articles is because AIs don’t have enough context to write them for us. You have to be there, in person, listen to sessions, interact in the hallways with the community, and absorb as much new knowledge as possible. That’s what I did last week in Amsterdam at KubeCon + CloudNativeCon Europe ‘26. Well, at least I tried to. Let me break down what I consider the most interesting topics were last week.

If you’ve ever run a pipeline, you’ve certainly encountered the following situation: The pipeline fails halfway through, and the cleanup script you needed at the end to tear down test infrastructure or archive the logs never gets to run. Until now, there was no built-in way in Bitbucket Pipelines to guarantee that a step always executes at the end of your pipeline, regardless of what happened before it. Today, we’re fixing that.

Your status page is only useful if the right people get the right notifications at the right time. A page that blasts every incident to every subscriber will train people to ignore your emails, or worse, unsubscribe entirely. A page that notifies too slowly will leave customers finding out about your outages from Twitter before they hear from you. I'm Leo, founder of Hyperping.

Updated April 02, 2026 Most on-call guides are written for companies with 50+ engineers, dedicated SRE teams, and budgets for tools that cost $21 per user per month before you even add a second escalation tier. If you have 5 people and a product that needs to stay up, that advice doesn't apply to you. I'm Leo, founder of Hyperping.