Operations | Monitoring | ITSM | DevOps | Cloud

Bullshit and nonsense. But let’s take it from the beginning. The industry’s story goes something like this: Then, in the same breath: You see the contradiction already, right? The same industry that tells you “collect less, simplify, trust the experts” is also the industry where: This isn’t an observability strategy. It’s observability by hindsight. Right. Good. Now we’re having fun.

Cover letters are supposed to help you shine, but most of them blur together into the same polite, forgettable paragraphs. The intention is good (“I want them to notice me!”), but the execution… not so much. So, here’s a simple, honest guide to writing a cover letter that actually works, especially if you’re applying to Checkly. Spoiler: shorter is better. And authenticity in this AI era is better than perfect polished perfection.

Datadog is a popular monitoring platform, and one of its key components is DogStatsD which is a customized extension of the original open-source StatsD protocol. DogStatsD adds powerful features like tagging, histograms, and distributions, but it also introduces vendor lock-in. This is because DogStatsD metrics follow a specific wire format that many other monitoring platforms do not natively support.

Continuing my adventure to have Monitive being run by AI Agents, I had some brainstorming sessions with... well... AI. I was impressed about the maturity of the discussions one can have with ChatGPT 5.1 Pro and Claude Code Opus 4.5.

Your app feels slow, users complain… but your dashboard says response time is totally fine! But the real pain is revealed when looking at percentiles. In this post, we’ll break down why the 95th percentile response time metric is useful, plus how to work with it in practice. ‍

As the year winds down, I find that most cybersecurity and compliance teams are focused on closing projects, hitting targets, and maybe even planning a well-earned break. But regulators? They don’t take holidays. FCA, PRA, GDPR – they remain vigilant, and so should you. For IT leaders, this season often feels like walking a tightrope: balancing operational demands with the relentless need for compliance.

Today’s engineering organizations are built around service ownership. Service owners are accountable for keeping their services reliable, performant, and ready to scale. But no service operates in isolation; every team depends on others, and those dependencies form a complex web that can be hard to see, let alone understand. To truly deliver reliable systems, you need visibility not only into how your own service performs, but also how it affects others.

Modern business functions are based on the promise of smooth and seamless experience, without the need for downtime or long waits for backend processes to finish. For such digital operations, timely execution of business processes—like financial closings, order fulfilment, report generation—is non-negotiable.