Operations | Monitoring | ITSM | DevOps | Cloud

AI Engineering at incident.io

Working on AI in incident management means there's no playbook. No million blogs. Just building at the forefront of what's possible with AI models.In this video, Martha, Product Engineer on our AI team, talks about what it's really like working with AI that helps engineers respond to incidents faster. This covers the shift from traditional engineering, learning the personalities of different AI models, and why you need to embrace constant change when new models drop all the time.

N-central 2026.1 Release Notes

Join Paul Kelly, Head Nerd at N-able, for a deep dive into the N-central 2026.1 release. This update focuses on three core pillars: usability, compliance, and platform experience to help your team manage environments with greater efficiency and confidence. Key Highlights: · CMMC Ready Version: A brand-new, on-premise version of N-central designed to meet US Department of Defense cybersecurity requirements. This supports organizations requiring CMMC Level 2 compliance and handles Controlled Unclassified Information (CUI) and Federal Contract Information (FCI).

Simultaneous multi-cloud deployment to AWS and GCP with CircleCI

AWS recently experienced a significant outage. The outage took down major services, including parts of McDonald’s mobile ordering system, some Netflix features, and many other applications that relied solely on AWS infrastructure. This event perfectly illustrates why relying on just one cloud platform can be risky.

Who Watches the Vibe Coder?

AI didn’t replace developers. It replaced the part where you were forced to understand what you just shipped. Now you can prompt your way to a feature, skim the diff, and merge something that “seems reasonable.” And then production does what production always does: finds the one weird browser + one slow network + one user flow that turns your “reasonable” code into a bonfire. So who watches the vibe coder?

React Native SDK 8.0.0 is here

We just released React Native SDK 8.0.0, here's what's new, and what's changed. It's been a while since the last major version. The last major release, 7.0.0, shipped on September 2, 2025. After 13 minor and 2 patch releases, it's finally time for a new major version to land: 8.0.0. This version is a maintenance and capability major. This means we: It should be straightforward to upgrade, but check the migration guide for your setup.

Reliability Has Outgrown the Systems Supporting It

Service reliability has outgrown uptime checks and component-level tools, creating friction that slows response, increases toil, and wears teams down. Uptime checks can pass, high availability can be in place, and users still can’t complete basic actions. Pages load slowly, latency spikes, and requests stall — all without a single system flagged as down. Availability measures whether a service is running.

What is OpenTelemetry and Why Do Organizations Use it?

Mining for information about environments is like trying to find gold. Looking for gold can be sifting through silty waters or blasting through a mine. In some cases, the gold nuggets are so small as to be almost invisible, some things look like gold but aren’t, and others are larger nuggets where the miner strikes it rich. Trying to understand how a distributed system works means sifting through vast amounts of telemetry, looking for patterns.

The Next Era of Observability: Founders' Reflections - Additional Q&A

What happens when the people who helped define observability take a hard look at AI? That’s what Honeycomb co-founders Christine Yen (CEO) and Charity Majors (CTO) dug into during this webinar, starting with the early days of observability (back when it wasn’t even a category yet).

The 2025 Wake-Up Call for Engineering Teams

For years, organizations tried to solve operational pain by collecting more data, adding more dashboards, and consolidating more tools. But 2025 exposed a deeper mismatch. Systems had become more distributed, AI-assisted, and interdependent than ever before, while teams had shrunk and on-call pressure had intensified. This wasn’t a tooling failure. It was an architectural and cognitive one.