Operations | Monitoring | ITSM | DevOps | Cloud

Gavin joined Kentik’s People Ops team less than a year ago, so when April brought his first team offsite and his first HR conference in San Diego, it was a lot of firsts at once. He writes about meeting his colleagues face to face for the first time, what he took away from HRA 26, and his new appreciation for tapirs.

Modern operations teams work within a constant stream of dashboards, status summaries, and health indicators that turn complex environments into organized visual displays. Large screens show color-coded service conditions. Executive reports quantify uptime. Observability platforms map system dependencies across cloud, hybrid, and distributed architectures. This visual structure creates a sense of order. In environments defined by constant change, that sense of order can feel like control.

OpenTelemetry won the architectural standards battle. At scale, though, telemetry breaks more like plumbing than code. It breaks quietly, across a graph, with a blast radius you don’t understand until it’s expensive. With over 65% of organizations now running more than 10 collectors in production, hybrid deployments across Kubernetes and VMs are accelerating fast. Telemetry standardization is no longer a project milestone. It is a baseline expectation.

Making custom Elastic integrations better with both Automatic Import improvements and Integration Skills Elastic 9.4 shipped two tools for building custom integrations: Both are available today.

How quickly should your team resolve a critical ticket, and what are the consequences when it misses the target? That is exactly where Service Level Agreements (SLAs) come into play. An SLA turns service expectations into measurable commitments by defining clear response and resolution targets. Rather than starting from scratch, an SLA template provides a structured foundation for establishing those commitments and tracking performance against agreed standards. Why does that matter?

A few weeks ago I wrote about a customer’s refund request that stopped halfway through at 11:47 p.m. on a Tuesday night. That post walked through the 40 minutes it took to work out what happened when an agentic application had a problem: a tool retried against a rate-limited payments API, the error responses filled up the context window, and the agent gave up. The whole reason we built Agent Timeline was to turn that 40 minutes into five. To reduce MTTR. To solve the problem and get back to sleep.