Operations | Monitoring | ITSM | DevOps | Cloud

Master Kubernetes management in 2026. Discover how Agentic Automation resolves Day-2 Ops, eliminates configuration drift, and cuts cloud spend on vanilla EKS/GKE/AKS.

New models, new agents, new capabilities. It seems like every week there’s a new must-have AI function. It’s no surprise that leaders are feeling pressure to move quickly. At a PagerDuty on Tour event, a customer joked that they couldn’t fathom having a five-year AI strategy; it makes way more sense to have a five-minute one. There’s truth in that comment.

Many alerting processes still rely heavily on manual work. In some situations, this is necessary – for example, when human approval is required. However, in many operational and incident-response scenarios, manual handling is simply the result of outdated workflows. In these cases, automation can significantly improve response times, efficiency, and reliability.

Battery energy storage systems (BESS) play a critical role in modern energy infrastructure. Utilities rely on these systems to balance renewable generation, stabilize grid operations, and respond to changing electricity demand. As deployments scale in size and complexity, operators require continuous insight into battery health, system performance, and grid interaction. Operators rely on telemetry generated across several operational platforms.

Every year, NVIDIA GTC offers a glimpse into the future of computing. But this year felt different. The conversations from the past few days point to something bigger than faster GPUs or larger models. The industry is shifting its mindset entirely. GTC 2026 made it clear that the goalposts for AI haven't just moved, they’ve been uprooted. We’re past the point of talking about "faster chips." Everything points to a total shift in the industry's DNA.

Your first NOG meeting doesn't have to be daunting. Here's what to expect, how to prepare, and how to make the most of every session and conversation. Co-authored by Rob Parker and Gavin Tweedie If you’re trying to optimize your organization’s peering and Internet Exchange (IX) traffic engineering as your network grows, you may be searching for more ways to improve your network or customer experience.

This is a guest post from Kellyn Gorman. Kellyn Gorman is a Database and AI Advocate and Engineer at Redgate She's the previous director of Data and AI at Silk, and the Oracle SME in Azure at Microsoft. With a robust background in cloud technology and a passion for promoting its merits and potential, I am thrilled to spearhead conversations and actions that help shape the future of this industry.

For more than a decade, organizations invested in tools and telemetry with the belief that more visibility would create more control. Monitoring expanded across cloud, application, network, and infrastructure layers. Observability platforms entered the mainstream. Automation tools promised faster detection and improved coordination. Yet despite these advancements, incidents are not easier to understand. War rooms still fill with conflicting interpretations. Signals generate more questions than answers.

Session Replay. Structured logs. AI monitoring. Automatic OpenTelemetry tracing. Feature flag tracking. If you haven't seen these in your Sentry dashboard, your SDK version is probably the reason. Whether you're on @sentry/react, @sentry/nextjs, @sentry/vue, @sentry/angular, @sentry/sveltekit, or any other @sentry/* package, they all version together. When we say v10, we mean all of them.

In the modern cloud infrastructure landscape, we don’t have a data problem; we have an actionable interpretation gap. Engineering teams are often drowning in metrics that describe a crisis without providing a clear path to remediation. Traditional FinOps, SRE, and DevOps work has become a reactive loop of dashboard-watching and manual firefighting.