Operations | Monitoring | ITSM | DevOps | Cloud

AI adoption is accelerating across enterprises, but governance isn't necessarily keeping pace. As AI becomes part of everyday business workflows and applications, organizations need to understand where it is being used, what data it can access, and who is responsible for managing the risks. ManageEngine's shadow AI researchhighlights this challenge.

A funnel can tell you that 40% of users dropped off between checkout and payment. What it can’t tell you is what those users did instead, such as return to an earlier form field, leave the flow for a support page, encounter an error, or take another route entirely. Because actions and views between funnel steps don’t affect the conversion calculation, two very different experiences can produce the same funnel result.

Today we’re taking our partnership with Chris Oliver (founder of Hatchbox and GoRails) one step further. With AppSignal, you can already store enriched telemetry about your applications, services, and infrastructure, along with your user context, in your AppSignal context store. You can use that context store for traditional observability reporting and workflows, or connect it to your agents over MCP or the CLI. AppSignal’s context store is what our Intelligence features are built on.

Alert routing often starts simple. A team creates a few contact points, adds some label matchers, and builds a notification policy tree that sends each alert to the right destination. But alerting configurations rarely stay simple. As an organization grows, its notification policy tree must accommodate more teams, services, and routing requirements. Changes for one team still require editing a global configuration, making ownership less clear and independent provisioning harder.

You're producing more trace data than you want to pay to store, so you sample. A fixed 1-in-100 rate cuts your bill, but it's blind. It keeps 1% of your errors, 1% of the requests to that rarely-hit route, and 1% of the health checks, all at the same rate. The noisy traffic you care about least dominates what you keep while the traces you need during an incident are the ones most likely to be gone.

Helping federal agencies reduce digital friction, strengthen mission continuity, and make better use of limited resources.

Why do the same complaints about call quality and slow file transfers keep coming back after the network has been checked and declared healthy? Packet loss is usually the answer, and it survives investigation because it degrades the services people use without taking anything offline. That combination makes it expensive. Equipment gets rebooted, cables get replaced, and tickets go to the internet service provider, often with nobody knowing which segment of the path is discarding traffic.

Most networks were never designed. They were extended, one switch and one VLAN at a time, until a single core failure took the site down and nobody could find the diagram. According to the Uptime Institute Annual Outage Analysis 2026, 57 percent of organizations said their most recent major outage cost more than $100,000. Network design is how you stop paying that bill. You decide the network topology, the addressing and the hardware on purpose, before the cabling goes in.

During a recent Agent Hackweek, an internal Sentry event that gives us a week to build any AI or agent project we want, a colleague pitched me on writing the Laravel AI integration. The goal was to give agents built with Laravel AI the same Agent Tracing support we already have for other frameworks. I liked the idea, he built Sentry’s Agent Tracing for Python based agents before which meant he already had domain knowledge.

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.