Operations | Monitoring | ITSM | DevOps | Cloud

Alert rules are great for the failures you can predict, but they fall short on the ones you can't. With the advent of modern AI, you might think the solution is to swarm your stack with agents that monitor every last detail, but that can quickly lead to astronomical bills. And those are the gaps Watchers fill: catching what alerts miss while keeping costs in control. Generally Available as of ObservabilityCON 2026, Watchers are always-on agents in Grafana Assistant.

AlloyScan 26.11 brings a redesigned Site health widget, Microsoft Intune integration, and easier ways to set up and use data views. Take a look at what’s new.

When a JavaScript error reaches Sentry, the stack trace points at minified code. Sentry finds the source map that was uploaded for that build to be able to show you the original file and line. Source maps are uploaded in artifact bundles. There are two ways to find the right one: Symbolicator, our open-source symbolication service, does the lookup when it processes an event.

We’re happy to announce that you can set up Third party service monitoring from the UptimeRobot API, MCP server and CLI too, and get alerted when a service your product depends on has an outage. Add a provider from your deploy pipeline, ask your AI assistant whether Stripe had an incident last night, or check a provider’s status from your terminal.

Open source website monitoring tools give organizations greater control over how they monitor websites, servers, applications, and infrastructure. They can reduce licensing costs, offer extensive customization, and integrate with existing workflows, but they also require more time to deploy, maintain, and scale than managed alternatives. We’ll compare some of the best open source website monitoring tools available today, from lightweight uptime monitors to enterprise-grade observability platforms.

IT operations teams need more than a shared calendar to manage after-hours incidents. When a server goes down, a network fails, or a critical application becomes unavailable, the right technician needs to be notified immediately. However, managing on-call coverage through spreadsheets, manual call trees, and disconnected notification systems can create gaps in coverage, missed alerts, and delayed incident response.

More and more, we are hearing how artificial intelligence is transforming how we build, secure, and share software. But as AI models become more powerful, questions around openness, security, and digital sovereignty are becoming harder to ignore. Can open models really be controlled? Is AI putting open-source communities under pressure? What does genuine technological independence look like? And who decides who gets access?

Agent-written pull requests need a running environment before anyone can review them. What a full-stack preview environment needs (services, databases, seed data, scoped secrets, cleanup, cost caps), how Vercel, Netlify, Argo CD ApplicationSets, homegrown GitHub Actions + Terraform and Qovery compare, and how to run it on your own cluster for free. Romaric founded Qovery to make Kubernetes accessible to every engineering team.

Set up anthropics/claude-code-action so @claude turns issues into branches and pull requests, then let Qovery preview environments deploy each Claude PR to its own full-stack environment on your Kubernetes cluster, post the URL on the PR, and delete it on merge. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.