Operations | Monitoring | ITSM | DevOps | Cloud

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

Sponsored Post

5 AWS Logging Tips and Best Practices

If you're an Amazon Web Services (AWS) user, you're probably familiar with some of Amazon's native services available for logging and monitoring, such as CloudWatch and CloudTrail. With that said, log management can get complicated quickly, especially if you're dealing with a high volume of logs from AWS Lambda functions or a multi-cloud/hybrid cloud environment. In this blog, we'll introduce the basics of AWS logging along with five tips and best practices for optimizing your log management in AWS.

Filebeat filestream configs that pass test config but still fail

A Filebeat config can print Config OK and still exit on start, ship your multiline settings as event data, or send a whole log file to your stack twice. We found most of these while testing the Filebeat configs on our integration pages, then rebuilt each mistake, plus the migration traps around them, on Filebeat 8.19.23 and 9.5.5 to see exactly what happens.

AI-assisted log investigation on Logit.io today: Hosted OpenSearch MCP and onboarding AI prompts

On 8 October 2026 Elastic announced the private preview of Elastic nightshift AI SRE, an AI agent built into Elastic Observability that detects and investigates issues and shows its reasoning. It is a sign of where observability tooling is heading: more of the first hour of an incident handled by an assistant that reads your telemetry. Short answer: Logit.io does not offer an autonomous AI SRE agent.

Reading your ingestion history: hourly log counts, the partial hour and 7-day trends

The ingestion card on your Logit.io dashboard has a 24h / 7d toggle for Logs and Metrics, hourly log counts built from counter increases and a dotted line for the hour that is still filling in. Those three changes decide whether a dip on the chart is a real problem or just the clock.

Threat Advisory - Trojanized Claude Code Extension: SSH Backdoor

A tampered build of the Claude Code editor extension (anthropic.claude-code 2.1.313) was published on the Open VSX store used by Vs code,Cursor and similar editors, quietly gives attackers persistent remote access to any computer that runs it, while the extension keeps working normally. Researchers don’t yet know how it was published (the listing belongs to an Anthropic employee) or who is behind it. They found no evidence that Anthropic’s official Marketplace release was affected.

Run AURA in Slack without opening a single inbound port

Making an SRE agent available in Slack sounds straightforward until you start thinking about what that agent can access. If it's connected to Kubernetes, you need to consider how Slack communicates with the agent, what infrastructure the agent can inspect, and who can ask it to do something. Making operational tools easier to use shouldn't mean exposing another service or giving everyone unrestricted access to production.

Dataset Curation: Turn Production Failures Into Test Datasets | Splunk Agent Observability

Your agent breaks in production. You fix it and move on. But the input that actually broke it is gone and two months later the same failure quietly comes back, because there was never anything to test against. That's not a debugging problem. It's a missing dataset. This demo turns low-scoring production traces into a regression suite you can run against every prompt and model change, without writing a single test case by hand.

Pre-Push Eval Gate: Block AI Agent Regressions Before They Ship | Splunk Agent Observability

Every engineering team has unit tests. They tell you the code still works. They tell you nothing about what the model started saying. This demo wires a single eval gate script into a git pre-push hook, so Splunk Agent Observability scores every agent's output before the push is allowed through. Luna, an on-premise small language model, runs as a synchronous judge against fixed thresholds. Fail one, and the push is blocked.

Agent Control Demo: Steer, Block, and Audit AI Agents | Splunk Agent Observability

Most teams keep an agent from regressing by hardcoding checks into its logic, an if-statement here, a regex there. Every new rule then becomes a code change, a review, and a deploy, and the person who spots the problem in production is rarely the person who can ship the fix. Agent Control moves those rules out of the code and into one hub. Steer, block, and validate agent behavior in real time, with rules any team member can update without touching the codebase.

Find the Retry Loop Burning Your AI Agent Budget with Tracing | Splunk Agent Observability

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.