How It Works
Every Opensolr cluster server continuously parses its Solr log files. Each ERROR, WARNING, and CRITICAL entry is automatically extracted, classified, enriched with a human-readable explanation, and indexed into a dedicated search index. This happens in the background — there is nothing to enable, configure, or maintain.
What gets captured for each error:
The Error Audit Dashboard
Open any index in your Control Panel and click Error Audit in the left sidebar. The dashboard loads your error history instantly.
Summary Cards
At the top, four cards give you an at-a-glance breakdown: Critical, Errors, Warnings, and Total counts for the currently filtered view. These update dynamically as you change filters.
Error Rate Chart
A bar chart shows error frequency over the past 7 days, broken down by hour. Spot patterns immediately — recurring errors at specific times, sudden spikes after deployments, or a clean flat line when things are running smoothly.
Filters & Search
Errors Table
The main table shows every error in reverse chronological order. Each row displays the timestamp, level badge, error type, severity score, a truncated message, and which server it came from. Click any row to open the full detail view.
Error Detail View
Click any error in the table to open the detail modal. Everything you need to understand and fix the issue, in one place:
Below the explanation, you get the full technical breakdown:
- Timestamp — exact time of the error
- Server — which cluster server logged it
- Level / Type / Severity — color-coded badges
- Error Message — the raw message from the log
- Root Cause — the deepest exception
- First Log Line — the original line from solr.log
- Stack Trace — compacted and syntax-highlighted, with Exception, Error, and Caused-by keywords highlighted in red for quick scanning
Error Types & Severity Levels
Every error is automatically classified into a type based on the exception class:
| Type | What It Means | Common Cause |
|---|---|---|
| SOLR | Internal Solr processing error | Schema mismatch, bad config, corrupt index |
| MEMORY | Out of memory / heap exhaustion | Very large result sets, complex queries, large documents |
| I/O | Disk read/write failure | Disk full, permissions, corrupt file |
| TIMEOUT | Query or operation took too long | Expensive wildcard queries, unoptimized index |
| PARSING | Malformed query or document | Invalid query syntax, bad XML/JSON in updates |
| CONNECTION | Network connectivity issue | Temporary network blip, DNS resolution failure |
| SECURITY | Access denied | Authentication failure, IP restriction |
| GENERAL | Uncategorized error | Various — check the stack trace for specifics |
Severity levels:
Error Audit vs Tail Error Log
Opensolr now has two error views. They serve different purposes:
Use Tail when you need to see errors as they happen, right now. Use Audit when you need to find errors from the past, search for specific exceptions, or understand error trends.
Getting Started
- Log into your Opensolr Control Panel
- Select any of your Solr indexes
- Click Error Audit in the left sidebar
- Your error history loads automatically — use the filters, search, and chart to investigate
No setup, no configuration, no extra cost. Error Audit is included with every Opensolr account and works for every index across all plans.