Operations | Monitoring | ITSM | DevOps | Cloud

Routine vulnerability fixes are rarely difficult in isolation. The interruption that they cause is the problem: pick up the ticket, trace the dependency, update the package or image, regenerate files, run the checks, open the pull request, then return after deployment to close the loop. That repeated handoff was a good candidate for automation with agentic pipelines. The goal was simple: start the day with a tested pull request instead of another ticket to pick up.

Your status page subscribers can now receive Early Warning Signals in addition to regular outage alerts. Early Warning Signals is our flagship feature that detects outages before providers acknowledge them on their status pages. When we launched this feature two years ago, we had no idea how effective or beloved it would become. StatusGator now regularly detects outages at your most important providers, giving you that edge and answering the question: “Is it everyone? Or is it just me?”.

Giordano “Gyo” Piazza, GitKraken’s Director of Engineering, has spent the past month heads down on the next version of Kepler. When he got on a call to talk through it, he skipped the changelog and went straight to the part he actually wanted to talk about: how agents show their work.

Tuning guardrails can take time. To accelerate this, we combined the power of Claude Code, Coralogix Telemetry and the CX CLI, to build a loop that iterates on guardrails. To test our loop, we built a fictional chat interface for an iGaming operator, that took bets, gave odds on markets and more, but with a catch: this agent was not permitted to make predictions about where the market was going. With our goal in place, we got to work designing our loop.

Database monitoring is the continuous tracking of a database's health, performance, and resource consumption, covering metrics like query latency, throughput, connections, and replication lag. In the AI era, it has expanded to include a fifth dimension: spend. Modern teams monitor not just whether the database is fast, but whether the workload it serves is worth what it costs to run. In May 2025, an engineer named Bohan Zhang stood up at PGConf.dev in Montreal and broke every scaling rule in the book.