Overview

Operation AI Investigation runs an agentic root-cause analysis on a single operation in Operations Monitoring. The agent analyzes both the success rate and the latency of the operation. It surfaces focused investigations for each failure mode (errors, timeouts, abandonment), for latency regressions, and for sustained high latency, so you can see at a glance why the operation is degraded.

Prerequisites

• RUM without Limits must be enabled in your organization.

Launch an investigation

1. Open the Operations page for your application from Operations Monitoring.
2. Select an operation.
3. The Operations page surfaces two elements:
   • A summary at the top with a plain-language overview of the operation’s health across success rate and latency.
   • A ranked list of recommendation cards — one per failure mode (errors, timeouts, abandonment), one for latency regression, and one for sustained high latency. Each card is tagged with a priority badge (P0, P1, or P2) reflecting relative severity.
4. Click Investigate on a card to open a detailed analysis.

What the agent investigates

The agent looks at several modes of failure or degradation for the operation:

• Errors: Operations that ended with an error.
• Timeouts: Operations that did not complete within their expected duration.
• Abandoned: Operations that the user gave up on.
• Performance regression: Operations whose latency degraded compared to the historical baseline.
• Latency: Operations that are consistently slow, independent of a recent regression.

For each card, the findings are grouped into three root-cause categories:

When applicable, the agent surfaces frontend and backend error groups together with the affected endpoints and code locations.

Read the results

When you launch an investigation, a side panel streams the analysis as it runs. Once complete, the panel shows the inferred root cause and a ranked list of findings.

Root cause

The agent categorizes the root cause as Frontend, Backend, or Network, with a confidence level of High, Medium, or Low.

Ranked findings

Each finding includes:

• Summary: A description of the failure or degradation pattern.
• Code locations: File path, line number, and surrounding snippet when source maps are available.
• Correlated APM endpoints: Each with a View trace link that opens the matching trace in APM.
• Error groups: Affected session count, whether the error first appeared in a recent application version, and a View Sample Session link that opens the session in the RUM Explorer.

Take action

After an investigation completes, you can act on findings without leaving the panel:

• Fix with Bits: Opens the Bits AI dev assistant with the investigation context pre-filled to generate a code fix from your IDE.
• Copy Investigation Prompt: Copies the agent’s prompt to your clipboard so you can rerun, refine, or share it.
• View trace on a correlated endpoint: Opens the matching trace in APM.
• View Sample Session on an error group: Opens the session in the RUM Explorer.

Further reading

Additional helpful documentation, links, and articles:

AI InvestigationsDOCUMENTATION Operations MonitoringDOCUMENTATION Single-View AI InvestigationDOCUMENTATION