Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Frum%2Fproduct-features%2Fanalyze-errors-with-olly-mini.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Frum%2Fproduct-features%2Fanalyze-errors-with-olly-mini.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Analyze errors with Olly mini

Use [Olly mini](https://coralogix.com/docs/docs/user-guides/olly/olly-mini/.md) in [RUM Error Tracking](https://coralogix.com/docs/docs/user-guides/rum/product-features/error-tracking-user-manual/.md) to quickly understand errors and identify next debugging steps.

Olly mini analyzes an error and provides a structured explanation of the likely cause, along with investigation guidance.

## What you can do[​](#what-you-can-do "Direct link to What you can do")

With Olly mini, you can:

* Understand why an error likely occurred
* Review suggested debugging steps
* Identify recommended next actions
* Investigate referenced functions directly from the analysis

Olly mini helps you move from stack trace to investigation faster.

## Where Olly mini appears[​](#where-olly-mini-appears "Direct link to Where Olly mini appears")

Olly mini is available in the error template drilldown view in **Error Tracking**, positioned above the graph in the error template drilldown view.

[![error-drilldown](/docs/assets/images/error-drilldown-e47e4dc5bce771c4d1bafc6ed43a3f0b.webp)](https://coralogix.com/docs/docs/assets/images/error-drilldown-e47e4dc5bce771c4d1bafc6ed43a3f0b.webp)

Olly mini is available in the **error template drilldown** view in **Error Tracking**.

It appears as a collapsed bar above the error graph.

**Let Olly analyze your root cause**

Select this bar to open the Olly mini analysis panel.

Olly mini analyzes a **single error occurrence** from the selected error template.

## Analyze an error[​](#analyze-an-error "Direct link to Analyze an error")

1. Go to **Error Tracking**.
2. Select an error template.
3. In the drilldown view, select **Analyze**.
4. Review the analysis in the Olly mini panel.

The analysis is generated using the error stack trace, error message, and available runtime context.

## How Olly mini analyzes crashes[​](#how-olly-mini-analyzes-crashes "Direct link to How Olly mini analyzes crashes")

When you run an analysis, Olly mini evaluates:

* Stack trace
* Error message
* Crash template identifiers
* Runtime metadata such as browser, OS, version, URL, and release (when available)

## Understand the analysis results[​](#understand-the-analysis-results "Direct link to Understand the analysis results")

When expanded, Olly mini provides a structured explanation of the error, including the possible cause, debugging steps, and recommended next actions.

[![ai-output](/docs/assets/images/olly-mini-output-597e96c810837f4cf853a885db35bf56.webp)](https://coralogix.com/docs/docs/assets/images/olly-mini-output-597e96c810837f4cf853a885db35bf56.webp)

Olly mini presents results in four sections.

**Possible cause**: Explains the most likely reason for the error based on the stack trace and runtime context.

**Debugging instructions**: Suggests investigation steps to help confirm the root cause.

**Actionable next steps**: Provides recommended actions or mitigations to resolve the issue.

<!-- -->

## Copy the analysis[​](#copy-the-analysis "Direct link to Copy the analysis")

You can copy the full Olly mini analysis.

Use this to:

* Share findings with your team
* Add investigation notes to tickets
* Document debugging progress

## Provide feedback[​](#provide-feedback "Direct link to Provide feedback")

Select the thumbs up or thumbs down icon to indicate whether the analysis was helpful.

This feedback helps improve analysis quality over time.

## Scope and limitations[​](#scope-and-limitations "Direct link to Scope and limitations")

Olly mini error analysis:

* Does not perform full incident root cause analysis
* Does not analyze recurring patterns across multiple crashes
* Provides probabilistic guidance
* Does not guarantee correctness

Always verify analysis results using your code and logs.