Operations | Monitoring | ITSM | DevOps | Cloud

We are absolutely thrilled to share with you all that Coralogix has been recognized as a Leader in the Gartner Magic Quadrant for Observability Platforms. When we architected Coralogix around in-stream processing, open-format storage, and index-free query, we weren’t optimizing for where observability stood at the time. We were building for the world it was heading toward.

Software systems are getting better at understanding themselves. The mix of richer telemetry, smarter pipelines, and agentic AI is shifting observability from a passive record of events into something more active and useful. That shift is what we mean by context engineering. We recently partnered with O’Reilly on a report by David Beale that introduces the discipline. Before you read it, here are five things worth knowing.

The new Advanced Pipeline Editor went live for all paid plans, we launched a public Blueprints library of ready-made pipeline patterns, we reworked plan pricing and raised the Free tier to 100 GB/day, and the source and processor catalog grew with an AWS Neuron source, an AWS CloudWatch metrics source, and a full set of XML processors. None of these are flashy on their own.

Every on-call engineer has lost an evening to some version of this. Something breaks; the fix is usually somewhere in the logs, and the logs are scattered everywhere: a dozen servers, a few containers, a couple of cloud services, none of them in one place. So, you SSH into one box, grep, get nothing, move to the next, and an hour later there are fifteen terminal tabs open and still no clear sequence of events. Log aggregation tools kill that scramble.

Senior engineers who are fast at diagnosing ActiveMQ incidents share one trait: they know exactly what they are looking for in the broker log before they open it. They know the PFC signature, the OOM warning pattern, the journal recovery sequence, and the connection drop format. For them, the log is not text to search through, it is a structured operational record that maps each entry to a specific broker state.

The Advanced Pipeline Editor is now live for all paid Bindplane plans. It's a rebuilt configuration editing experience that puts your whole config in a single interactive graph: every source, processor, router, and destination, across logs, metrics, and traces, in one view you can search, pan, zoom, and edit directly. If you've ever bounced between pipeline tabs trying to figure out where a processor sits in a config with a dozen sources and three destinations, this release is for you.

AI has changed how software gets built. It hasn't changed how software gets run. Most of the AI money in software has gone into the IDE: code generation, copilots, developer assistants, faster pull requests. That work matters. But writing software is one slice of the lifecycle. The harder problem, and the more expensive one, is running that software in production. Production is where systems fail in ways nobody predicted. Incidents don't stay inside one service.

PagerDuty fires. You open the incident. Title, timestamp, nothing else. Whatever context exists is in someone's head, in a Slack thread from two weeks ago, or in a runbook nobody has touched since the last reorg. We got tired of that. So we put an AURA agent behind a Slack bot and pointed it at our own production environment.