Operations | Monitoring | ITSM | DevOps | Cloud

datadog

Monitor warehouse data quality beyond pipeline health

Oct 1, 2026 By Datadog In Datadog
You get a Slack message from the VP of Sales: They have asked an AI agent connected to Snowflake for the past quarter’s revenue and the numbers look wrong. First, you verify the agent’s query and, when that looks fine, check the pipelines that populate the underlying table. All jobs completed, the data is recently refreshed. Then it’s time to check the logs for errors. Nothing.
Read Post
canonical

Android belongs in your CI/CD pipeline

Oct 1, 2026 By Bertrand Boisseau In Canonical
How on-demand Android environments turn validation into a repeatable pipeline stage In the first article, we looked at automation: how Android environments can be created and managed programmatically. In the second, we looked at scaling: how shared infrastructure can make those environments available to more developers, tests, and workloads. This third article looks at the next step: integrating those environments directly into CI/CD.
Read Post
honeycomb

Dr. Cat Hicks on the Psychology of Software Teams

Oct 1, 2026 By Rox Williams In Honeycomb
What happens when a software engineer who has put their entire identity into being the resident expert of an obscure technology or language with ten years of experience and who knows the codebase like the back of their hand now has to compete with AI? Psychologically speaking, according to Dr. Cat Hicks, author of The Psychology of Software Teams and founder of Catharsis, that's called identity threat, and it's a surefire way to feel unsafe. We were honored Dr.
Read Post
onlineornot

OnlineOrNot updates from June through August 2026

Oct 1, 2026 By Max Rozen In OnlineOrNot
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.
Read Post
megaport

Megaport Advanced Services: From Network Design to Deployment

Oct 1, 2026 By Megaport In Megaport
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.
Read Post
scout

Best Monitoring Tools With MCP Servers for AI Coding Agents (2026)

Oct 1, 2026 By Scout APM In Scout
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.
Read Post
icinga

How to Make Claude Your UI Design Companion

Oct 1, 2026 By Florian Strohmaier In Icinga
When I first tried Claude Design, shortly after it was released, I wasn’t impressed. As an every day Figma user, I missed the option to manipulate elements directly, especially for fine tuning details. What I overlooked at that point was the fact that it is really good at generating different options efficiently. Most of them aren’t usable, but getting these options suggested helps when exploring and combining different approaches and ideas.
Read Post
Your On-Call Rotation Has a Single Point of Failure, and It Gets the Flu Every Winter

Your On-Call Rotation Has a Single Point of Failure, and It Gets the Flu Every Winter

Oct 1, 2026 By OpsMatters In OpsMatters
Most teams design on-call for the failures they can see in a dashboard. A region goes down, a deploy goes sideways, a certificate expires at 2 a.m. The rotation exists so that someone is always there to catch it. Far fewer teams design for the failure that takes out the catcher: the on-call engineer wakes up with a fever, and the plan for that is usually a Slack message and hope. Treat a sick engineer the way you would treat any other dependency outage. It is predictable, it is seasonal, and it has a blast radius that grows with every shortcut in the rotation design.
Read Post

Copyright © 2026 OpsMatters™. All rights reserved.