Operations | Monitoring | ITSM | DevOps | Cloud

One of the most expensive failure modes in AI agents is a silent retry loop. An agent hits a rate limit, blindly retries until it succeeds, the user gets a response, and no ticket ever gets filed. Under the hood, tokens are burning, latency is compounding, and a transient error today becomes a sustained outage tomorrow.

Running an agent in your cluster should not mean opening it to the internet. AURA reaches Slack over an outbound socket, so the cluster stays locked down. Jeff Vogt connects an AURA deployment running in Kubernetes to Slack using AURA's direct Slack integration. The setup is a Slack app with an app token and a bot token, plus a few lines added to the deployment's configuration. The Kubernetes MCP server is already deployed and connected to AURA before the video starts.

Bryan Peace Leon Adato break down what exactly security-minded IT folks - whether they work in SRE, dev, networking, or more esoteric disciplines - should do when a new, critical, apocalyptic vulnerability is announced. They walk you step by step through research, analysis, and how to protect your company if a patch isn't out yet. Along the way they muse about the nature of the industry, the sudden spike in CVEs, and where to find the best hard cidr to take the edge off.

The Claude Code extension in the Cursor marketplace was compromised for a short period of time today. Watch this security advisory from Chris Cooney and Hetram Yadav, threat detection and response manager at Coralogix, to understand: How the malicious attack operates How to know if you're affected How Coralogix is supporting customers.

Your AI agent just approved a return it shouldn't have, and nothing threw an error. Here's one agent request as a trace: the agent span, LLM calls, tool calls, and retrieval, with tokens and latency at every step. The fix wasn't the prompt. It was the data.

Cribl gives security teams control over their data: what they collect, where to send it and how much to keep. The rest of the SecOps stack hasn’t kept pace. Detections, parsers and configurations spread across SIEMs, pipelines and data lakes still change by hand, so every cost cut, migration or new source turns into weeks of manual validation, and plenty of planned changes never happen at all. SecOps as Code closes that gap: every change ships like software, with testing, version control and rollback across the entire infrastructure.

Your telemetry data can reduce engineering complexity AND make your software more sustainable - find out how in this episode! Welcome to Episode 5 of Live Laugh Logs, the podcast from the Coralogix Developer Relations team. This week, Annie is joined by Wilco Burggraaf, Principal Lead at HighTech Innovators and host of the Sustainable IT Action Netherlands meetup.