Operations | Monitoring | ITSM | DevOps | Cloud

Latest releases, resources, and events focused on Microsoft SCOM and modern ITOps & DataOps.

This month, we’ve added more control over Website and Ping alerts, expanded audit logs, and new ways to get outage reports through the API and webhooks. There’s also an Intercom AI connection to help with customer outage questions, and we’ve passed 12,000 monitored services! Here’s a closer look at what’s new.

Your Playwright test clicks Next page, waits for the item list, and times out. Now you’re digging through a trace to find out whether the page broke or an API call failed. Traditional browser-testing workflows focus on clicks, page state and UI assertions. Those checks tell you whether a user journey works, but investigating a failure also means understanding the APIs behind the page.

When we launched Bits Investigation in December 2025, our goal was to give teams an always-on agent that could investigate every alert and reduce mean time to resolve (MTTR). Since then, we’ve focused on making Bits faster, more cost effective, and even more accurate. At launch, the average investigation cost $25 and took 11 minutes.

Kepler has picked up a lot over the last few releases. So much, in fact, that Gyo, GitKraken’s Director of Engineering, had to trim his list before walking us through it. We sat down with Gyo and Jonathan, our Product Advocate, to go through the highlights. Gyo explained what shipped and why. Jonathan put the features to work live, building themes, cleaning up tasks, and forking a session from Claude to Codex. Here’s what we learned.

You call your ISP because calls keep dropping and the Internet crawls every afternoon. Support asks you to restart the modem. Then they test the line from their side, see nothing wrong, and tell you everything looks fine on their end. By the time a technician shows up, the problem is gone, and the ticket gets closed. The issue usually isn't that your ISP doesn't care. First-line support is trained to rule out the customer's network first, and most complaints arrive with nothing they can check.

Explore how the $6.36B Binance breach exposed critical gaps in identity, DevOps, and signing security - and what engineering teams can learn from it. The October 29, 2026 theft from Binance is best read as a failure of identity and release-path trust, not a failure of cryptography. Binance's early findings point to a compromised DevOps engineer's laptop that gave an attacker a route into a service container and the ability to submit unauthorized withdrawals.