Operations | Monitoring | ITSM | DevOps | Cloud

Recent industry research shows that AI is accelerating code creation, but having mixed results downstream. They also show that better platforms and pipelines yield better outcomes for teams adopting AI for coding. Every engineering leader I talk to is asking the same questions about AI coding assistants: How much faster can we ship? How much more productive can my developers be? On the surface, the answers look pretty good.

Building a catalog used to be a project. It meant months of tracking down owners, untangling dependencies, and manually piecing together a picture of your architecture. It was a tedious, thankless process that delayed the value of your Internal Developer Portal (IDP) before you even got started. Now, it’s a coffee break. We’re excited to introduce Magellan, our new AI-powered data engine designed to build your catalog and get your IDP live in minutes.

Here's a scenario every on-call engineer knows too well: a critical incident fires for a service you’ve never seen before. Your first ten minutes are a frantic scramble across wikis and Slack channels just to answer the most basic questions: Who owns this? What does it do? Where are the runbooks? By the time you’re oriented, the incident has escalated.

Let’s not mince words; there’s a special place in hell for the password reset ticket. It’s the most boring, most avoidable, and arguably the most expensive waste of time on your service desk. And yet, in 2025, most enterprises still treat password resets like it’s 2005. They route them through manual queues, bury IT teams, and frustrate users who just want to log back in. Even when the password reset is finally resolved, nobody comes away from the experience feeling like a winner.

Stay in the loop on key incidents with Auto-Watch and ensure data consistency at every milestone with Required Fields by Incident Type.

If you’re building high-performance systems, Golang has probably earned a spot in your stack. Its speed, lightweight concurrency, and quick compile times make it ideal for scalable APIs, microservices, and distributed systems. But those same qualities that make Go powerful can make performance monitoring tricky. Goroutines run fast and in parallel, which means a simple CPU or memory graph doesn’t always tell you what’s slowing things down.

Downtime is brutally expensive and damaging. Enterprises can lose about $9,000 every minute systems are down, while smaller businesses lose hundreds of dollars per minute. A single outage can often cost over $100,000, and nearly a third of companies lose customers due to downtime. That’s why many organizations turn to platforms like SolarWinds to maintain reliable systems and minimize the risk of costly disruptions.