Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

An agent that only speaks when spoken to is a tool you have to remember to use. Olly has run on a schedule for a while now, working a saved prompt hourly, daily, weekly, or monthly and writing its findings into a chat with its own run history. Those scheduled tasks are now wired into the Coralogix Notification Center, so Olly delivers that output itself, allowing Olly to reach out to Slack or email, out of the box.