Operations | Monitoring | ITSM | DevOps | Cloud

If you’re already running or are familiar with Home Assistant, you’ve likely worked with integrations, maybe a few automations, and possibly MQTT as a way to wire devices together. But webhooks add another layer of flexibility that lets you level up your smart home into a fully-customized, intelligent network. Instead of relying on built-in integrations and being confined to the same local network, you can let external devices and services push events directly into Home Assistant.

A customer pings support: “I tried to check out twice this morning and got a 500 each time, but it works fine for everyone else.” The session ID is in the email. You have full request/response capture in your environment, you have Datadog Synthetics already running browser checks against the same flow, and you still spend the next two hours grepping logs because none of those tools let you say “show me just this user’s requests, in order, and re-run them.”

We’ve upgraded the Reports page in StatusGator to give you more insight directly inside the StatusGator dashboard. Previously, reporting was limited to exports you could use to calculate your own uptime percentages and trends. Now, in addition to exported reports, you can view key reports and metrics without needing to download anything. We’ve also added a one-click download of the most commonly requested report: Uptime percentage by monitor.

Keeping track of your Microsoft 365 services just got easier. We’ve rolled out an update to the Microsoft 365 integration that removes manual setup and improves visibility. All services in your account can now automatically appear as components, so you can monitor them right away.

If you've spent any time wiring AI coding agents into developer platforms over the last year, you've probably reached for MCP. We did too. And after enough sessions watching context windows balloon and tool calls misfire, we started looking for something different. This is the story of what we built instead — a native AI skill for the Bindplane CLI — and the engineering decisions behind it.

The promise of AI in IT service management has been circulating for years. Chatbots that deflect tickets. Virtual agents that answer FAQs. Automation that routes requests. These are useful, but probably not the dream-state you were originally sold. What's different today is the arrival of agentic AI: systems that don't just respond to instructions but reason, act, and adapt across multi-step workflows with real consequences. The question for IT leaders is no longer whether to adopt agentic ITSM.

The question for enterprise AI in 2026 is no longer just which model. It’s which harness. An agent harness is the system around the model. It decides what the agent remembers, what context it sees, what tools it can call, what it is allowed to do, and what happens when it is wrong. The model provides intelligence. The harness provides control. This is where the real engineering is happening.

TLDR: Today, Harness is introducing the Harness Cursor Plugin, bringing the power of the Harness AI-native software delivery platform directly into Cursor. This integration, along with the Harness Secure AI Coding hook for Cursor, allows developers and AI agents to move from code changes to vulnerability detection, CI/CD execution, security validation, approvals, deployments, and operational insight without leaving the editor. AI has completely changed how we write code.

If service-centric observability provides the control layer, the next question becomes more urgent. What happens when organizations pair context with automation that operates inside clear defined boundaries? During conversations at Nexus Live 2025, leaders did not describe automation as a futuristic aspiration. They described it as a necessary progression. However, the distinction they drew was important. Automation without context accelerates activity.

Not every incident alert needs the same kind of response. One incident may need to wake someone up right away. Another may simply need to be picked up when the team starts work in the morning. Without a clear way to tell them apart, every incident feels equally urgent. That usually adds noise and makes incident response decisions harder than they need to be. This is where two questions help: In this guide, we’ll discuss what those questions mean and the four combinations that follow.