Operations | Monitoring | ITSM | DevOps | Cloud

The rise of platform engineering has put a new team at the center of the developer experience. These teams are tasked with building the "paved road" for developers, which includes providing a robust, self-service observability stack. However, they face a dual mandate: provide a great developer experience and manage the ever-growing costs and complexity of the tools involved.

DNS is one of the most important and most overlooked layers in your client’s infrastructure. As an MSP, you’re often the one who gets blamed when something breaks—whether you control the DNS or not. And while many DNS problems are silent, their consequences are loud: email failures, website outages, and frustrated clients. This DNS security checklist will help you proactively identify and fix DNS risks across all your client domains.

Whether you're keeping a personal blog or manage a corporate site or online storefront, website downtime can cost money and can damage your reputation. Let alone when you're maintaining a bunch of different client sites. And while downtime can't always be prevented, it's really easy to at least keep track of things, and diagnose potential issues from there. So, let’s start with the easy part.

In this latest update, I'll walk you through a few features I added that will make working with uptime checks less noisy, an alerts integration with Teams, and a few behind-the-scenes changes that will finally let me build mobile apps for OnlineOrNot.

Application metrics are structured, quantifiable signals that reflect how your software behaves in production. They capture key aspects of performance, response times, error rates, throughput, and resource usage, giving you a real-time view into the health of your system. Tracking the right metrics helps detect regressions early, surface latent issues before they impact users, and guide optimization decisions based on hard data, not guesswork.

Ivanti’s 2025 State of Cybersecurity Report found something utterly unsurprising: that organizations report a significant preparedness gap (that is, the gap between the perceived threat level and their degree of preparedness) across every threat vector and vulnerability we asked about. While security teams rightfully devote resources to building resilience so they can swiftly respond to and recover from attacks, closing those preparedness gaps requires proactive cybersecurity measures.

"Show me all critical incidents from the last week." "Create an incident for the payment API being down." "What was the root cause of that database incident last Tuesday?" If you've ever wished you could just ask Claude (or any MCP client) to handle incident management tasks instead of context-switching between chat and your incident management dashboard, you're going to like what we built.