Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Log Management, Log Analytics and related technologies.

Microlesson: Using Mobot for Log Analysis

This video demonstrates how to use Mobot to investigate issues, interpret its findings, and identify recommended next steps. Follow along as Mobot responds to a prompt by understanding your intent, gathering relevant data, performing multi-step analysis, reasoning across data sources, surfacing insights, and recommending next steps.

Run an AI SRE Agent Entirely Inside AWS with Bedrock and S3: AURA

An on-call question returns the threshold and the escalation owner from your own runbooks, and the answer comes back without a call to anyone outside. AURA runs against Bedrock as its model provider, using Claude Sonnet 5 served by AWS in the same region. Authentication is the normal AWS credential chain: a profile on a laptop, an IAM role in EKS.

What is going wrong with AI coding? Live Laugh Logs ep. 4

Welcome to Episode 4 of Live Laugh Logs, the podcast from the Coralogix Developer Relations team. This week, Chris Cooney joins Annie to share five key DevOps skills that have become even more important in the age of agentic code development, and gives you five key actions you can do today to start levelling up these skills. Subscribe to our channel for more insights into observability and AI.

Builder in the loop: what production agents were missing before AURA

Builder in the loop is a Mezmo interview series with the engineers, product leaders, and operators shaping AURA. Each installment looks past the product layer to explore the decisions, tradeoffs, and lessons involved in building agents for real production work. This installment features Mike Shearer, the engineer who built AURA and, until recently, its only developer. AI agents are easy to believe in when the task is small.

What an AI SRE agent actually finds when you point it at a broken Kubernetes cluster

‍ Most of the AI features that shipped into observability tools this year summarize alerts. You get a paragraph that restates the dashboard you were already looking at, and the agent never reads the cluster itself, because giving it cluster access is a security conversation nobody wanted to start. This walkthrough starts it.

No Custom Adapter: AI SRE Agent AURA Debugs Product Catalog in Dash0

The platform shows you which service is failing and which paths it touches, and stops there. Point AURA at the same telemetry and the cause comes back too. Dash0 shows the product catalog service in a failed state across the selected window, with errors on the path from the frontend service.

Kubernetes AI SRE Agent Finds a Crash Loop Nobody Asked About: AURA

You ask for a routine health check and expect a clean baseline. What came back was a pod that had restarted 788 times, unrelated to the question. AURA is connected to a Kubernetes cluster and to Prometheus through read-only MCP servers, running as one coordinator with two specialized workers. The prompt is one sentence: check the health of the cluster, and confirm whether all the pods are running. What comes back is not a baseline. AURA names the state as CrashLoopBackOff and attaches the restart count to it.