San Francisco, CA, USA
2014
  |  By Ofri Grushka
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.
  |  By Chris Cooney
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.
  |  By Chris Cooney
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.
  |  By Andre Scott
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.
  |  By Shai Reznik
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.
  |  By Peter Hammond
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.
  |  By Coralogix Team
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.
  |  By Coralogix Team
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.
  |  By Chris Cooney
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.
The OpenTelemetry Operator changed how teams approach telemetry collection in Kubernetes. The core appeal of zero-code instrumentation is that you can bring up telemetry inside application containers to collect traces, metrics, and logs without touching your source code or rebuilding your container images. However, if you follow the default OpenTelemetry Operator documentation, you quickly run into a heavy operational prerequisite: the Instrumentation CRD.
  |  By Coralogix
Go from tracking metrics to understanding users: see what they click, follow their journeys, and watch exactly where they get stuck, all alongside your telemetry.
  |  By Coralogix
5 things you can do with Olly right now, from instant answers to root causes to scheduled reports.
  |  By Coralogix
5 things you can do with the new Coralogix APM, no alerts to write and no database agent to install.
  |  By Coralogix
Thousands of agent sessions last month. But what did they actually ship? Vendor consoles show you tokens, Coralogix shows you impact, repo by repo, session by session. No vendor lock-in, no data limits.
  |  By Coralogix
Do you know how much of your AI agent spend goes to repos your company doesn't even manage? Olly makes it one question away.
  |  By Coralogix

#observability #ai #agenticcoding

  |  By Coralogix
Watch the full episode: MCP vs CLI: Does it even make a difference? Live Laugh Logs ep. 3.
  |  By Coralogix

#claudecode #optimization #aicoding #observability

  |  By Coralogix

#aicoding #theoryofconstraints

  |  By Coralogix

#claudecode #anthropic #devops

  |  By Coralogix
There are numerous types of logs in AWS, and the more applications and services you run in AWS, the more complex your logging needs are bound to be. Learn how to manage AWS log data that originates from various sources across every layer of the application stack, is varied in format, frequency, and importance.

Coralogix helps software companies avoid getting lost in their log data by automatically figuring out their production problems:

  • Know when your flows break: Coralogix maps your software flows, automatically detects production problems and delivers pinpoint insights.
  • Make your Big Data small: Coralogix’s Loggregation automatically clusters your log data back into its original patterns so you can view hours of data in seconds.
  • All your information at a glance: Use Coralogix or our hosted Kibana to query your data, view your live log stream, and define your dashboard widgets for maximum control over your data.

Our machine learning powered platform turns your cluttered log data into a meaningful set of templates and flows. View patterns and trends, and gain valuable insights to stay one step ahead at all times!