Operations | Monitoring | ITSM | DevOps | Cloud

TL;DR “AI observability” now describes two different jobs. One is watching the LLM apps and AI agents your team ships: prompts, tool calls, token spend, and output quality. The other is putting AI agents to work on your production telemetry so incidents are already being investigated by the time an engineer logs in. Most engineering orgs in 2026 need both, and very few tools cover the two well.

TL;DR: OrionIQ AI agents, available inside the logz.io platform, now learn from your feedback. Rate any agent run, thumbs up or thumbs down, say why, and the agent re-reads its own run, finds the decision behind the outcome, and writes a lesson. The next run of that agent in your account starts with the lesson in hand. It works for every OrionIQ AI agent, from Alert AI Analysis to scheduled and marketplace agents. Lessons never cross accounts or agents, and you control what the agent keeps.

Open 360 AI chat can now do more than investigate and explain. With new Logz.io API skills, the agent can create and manage Open 360 and Cloud SIEM objects, such as alerts and dashboards, directly from the conversation. Find an error pattern worth watching? Ask the agent to create the alert. Need a view of a service you just investigated? Ask for the dashboard. The insight and the follow-through now happen in the same place.

AI agents are only as effective as the context they can access. The problem is that most of that context lives outside your observability platform.

OrionIQ’s agentic investigation is now built into Logz.io Open 360 AI. Ask a question and OrionIQ investigates across your telemetry, shows its work as it goes, links every finding back to the exact query behind it, and tells you how much to trust the answer. Today we’re bringing OrionIQ Chat into Open 360 AI. This is the first OrionIQ product to ship inside the Logz.io platform, and it’s the same agent that powers the standalone OrionIQ app, now available right where you already work.

When an alert fires at 2 a.m., responders need context more than another dashboard. A suspicious authentication event may begin in an identity provider, touch a cloud control plane, appear in an application log, and end with an unusual data transfer. If each signal lives in a separate tool, analysts spend the first part of the incident rebuilding a timeline instead of containing the threat.

Ask ten engineering leaders how far their organization has actually gotten with autonomous AI, and most will admit the same thing once the marketing language drops away: not nearly as far as it looks from the outside. That was the undercurrent of a roundtable Logz.io and Twingate hosted on July 22, 2026, bringing together VPs of engineering, CTOs, senior security directors, and several product leaders across different industries and company stages.

TL;DR: Prometheus’s biggest structural weakness has always been cardinality. A stable feature years in the making is finally addressing it, and the rest of the observability market is already responding. Native histograms allow for more efficient metrics storage, reducing cardinality strain and enabling faster, more cost-effective AI-powered observability. Ready to see how AI-powered observability can simplify your monitoring? Book a demo of the Open 360 platform.

TL;DR: This is the engineering companion to our announcement post, Upgraded Alert AI Analysis: Automated Incident Investigation, read that one for what the new generation does for your team; read on for how it works under the hood. Interested in hearing more? Book a demo to see the Alert AI Analysis Agent live. Root cause analysis is one of the harshest tests you can give an AI.

TL;DR: OrionIQ has launched the next generation of its Alert AI Analysis agent within the Open 360 AI platform, designed to automate and accelerate incident investigation. Key features of this evolution include: Agent-Based Investigation: Instead of relying on a single prompt, the system coordinates specialized AI agents to correlate data across diverse sources like logs, metrics, deployments, and tickets.