Operations | Monitoring | ITSM | DevOps | Cloud

It's been a while since I last updated you on what's new in OnlineOrNot. For the most part, I've continued making it useful for software teams: there's now an MCP server, I've improved the terraform provider significantly, and there's a new TypeScript SDK. You can also (finally?) monitor DNS/TCP with it.

Here’s everything you need to know about incident management.

TL;DR Have you ever set out to push an allegedly 15-minute fix that ended up taking multiple weeks, without even a guarantee that it would actually work? It’s happened to the best of us during our professional journeys, but this time, the story is about Apache Kafka.

Network changes often stall after the design is done. See how Megaport Advanced Services helps teams move from planning to implementation and support. Ask a network team where their last big network change got stuck and you’ll rarely hear “we couldn’t work out the design.” The completed design is usually sitting in a document somewhere, reviewed and signed off. What stalls is everything needed after that. Somebody has to write the runbook. Somebody has to sit in the 2 a.m.

Your AI coding agent can read your code, run your tests, and open a pull request. Until recently it could not see what that code does in production. MCP servers from monitoring vendors close that gap. Connect one, and Claude Code, Cursor, or Copilot can pull the error, the trace, and the slow query behind a bug report without you copying anything out of a dashboard. Most major monitoring vendors now offer an official MCP server. But they aren’t interchangeable. Some only expose errors.