Operations | Monitoring | ITSM | DevOps | Cloud

Gartner recognizes Last9 in their latest Cool Vendor report for unified telemetry and agentic SDK—moving teams from reactive monitoring to proactive ops. Founder at Last9. Loves building dev tools and listening to The Beatles.

Rolling out a powerful AI tool like GitHub Copilot is a big win for any engineering leader. But because it’s such a significant investment, leadership will inevitably ask if it was worth the cost. Until now, answering this was nearly impossible. While GitHub provides adoption stats, connecting that data to real-world performance metrics like cycle time or code quality has been a manual, frustrating process. We built the Cortex AI Impact Dashboard to provide a clear answer.

Every engineering organization measures success differently. A dashboard that’s perfect for one team might be meaningless for another. While out-of-the-box views for DORA are a great starting point, leaders need the ability to define and share the specific combination of metrics that matter most to their business. Without this, you're either forcing your teams to conform to generic reports or wasting time rebuilding the same views every week.

You see MTTR creeping up, but you don’t know why. You could ask your teams, but that means meetings, pulling people off projects, and waiting days for answers. What if you could just…ask? We’re excited to introduce the new strategic AI chief of staff for engineering leadership, powered by the Cortex MCP. By connecting your Engineering Intelligence data with your scorecards and standards, the MCP allows you to have a strategic conversation about your organization’s performance.

A slow checkout request. A background job stuck waiting on another service. A log message that looks fine — until performance drops. In a Node.js microservices setup, these are the moments that test your observability. You know something's wrong, but tracing the request across dozens of services feels impossible. Distributed tracing changes that. It connects every span in the request's journey, showing exactly where time is spent and where things start to break down.

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.

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.