Operations | Monitoring | ITSM | DevOps | Cloud

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.

Coralogix Real User Monitoring has spent years collecting full-fidelity user sessions: every session and event processed in stream, without sampling and without prior indexing, at rest in cloud object storage you own. Today that data does a second job. Product Analytics brings heatmaps, funnels, and pathways to the RUM sessions you already send, with no second SDK to install. One dataset now answers what your users did and why it happened.

FinOps spent a decade making cloud spend predictable, and teams now point the same discipline at a workload that behaves nothing like a virtual machine. In the FinOps Foundation’s State of FinOps 2026 survey, drawn from 1,192 practitioners representing more than $83 billion in annual cloud spend, 98% now manage AI spend, up from 31% two years earlier. The main driver for this was agents.