Operations | Monitoring | ITSM | DevOps | Cloud

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.

From the first alert to the root cause, without leaving the page. TL;DR: Investigating an incident is a series of quick questions, each one leading to the next. Until now, Explore made you stop between questions to translate them into syntax, switch modes or rebuild a chart. The new Explore lets you go straight from one question to the next: one workspace, any dataset, any team, any way you like to ask. Here’s what that looks like on a real night on call.

We set out to understand how customers were using Coralogix from outside the web app. Olly answers questions about a system in plain language. Coding agents query logs, examine traces, read metrics and configure the platform through the Coralogix CLI and MCP server. We wanted to see how much of this was becoming part of everyday work. In the week of 20–26 October, 39% of Coralogix sessions included Olly, the CLI or MCP.

We put the same OpenTelemetry data into four backends, Coralogix, ClickHouse, OpenSearch and a Loki, Tempo and Prometheus stack, then set an agent twelve questions against each one, from counting spans to working out what is wrong in a system it has never seen. Then we forced the agents to continue investigating until they got to the right answer. In this experiment, what separated them was the time, tokens, tool calls and turns it took to get there.

The Coralogix migrations team has published what it measured. Since 2023 the team has moved more than 75,000 assets across 300+ migrations and onboardings, including a single migration of about 41,000 alerts. The new Migration Benchmarks page holds the figures by source, a calculator for your own migration and the causes of delay that post-migration reviews name most.

Your coding agent can debug production issues now. Yes… Not just “help you debug.” Actually run the investigation… FOR YOU! In this new era of agentic development, speed matters. And in the old days (you know… last week or so) we used to investigate production bugs ourselves. Manually. Like humans. But for a lot of incidents, we don’t need to do all of that anymore.

With GitOps, you can roll back your cluster with git revert and explain each approved change through a commit log. Routing normal changes through Git and running an in-cluster agent that detects drift from the repository gives infrastructure changes the same review and rollback discipline as application code, and Git preserves their history. This guide covers the four GitOps principles, the pull-based reconciliation workflow, and the tools and practices you need to get started.

Coralogix APM has told you which service is behind the latency. From today, the new APM experience tells you what is behind the service: the release, the environment, or the query one layer down. It watches every service you run from the moment it appears, without anyone writing an alert. And everything you see on the screen, your AI agent can use too: in Olly, from the Coralogix CLI, or through MCP in your IDE. A latency chart shows that something got slow.

Every page view, click, and session your RUM SDK captures lands in Coralogix as a log event under the cx_rum subsystem — the raw data behind how people actually use your product. You can turn it into a shareable report without writing a single query. Just ask your coding agent. Your agent queries that data through the CX CLI and writes the report for you: describe what you want in plain English, get a formatted report back — without leaving the terminal.

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.