AI Analysis
When auralog detects errors in your logs, Claude generates an analysis. Here’s what that looks like.
Reactive analysis
Section titled “Reactive analysis”Every time an error or fatal log arrives, it triggers an analysis. Claude receives:
- The error message and stack trace
- Recent logs from the same project (for context)
- Your source code (if a GitHub repo is connected)
The analysis includes:
- Severity — high, medium, or low based on impact assessment
- Root cause — what Claude thinks went wrong and why
- Recommendations — specific steps to fix the issue
- Affected code — file and line references (when source is available)
Scheduled reviews
Section titled “Scheduled reviews”Claude also runs periodic reviews across your recent logs, looking for:
- Recurring error patterns
- Increasing error rates
- Correlated failures across services
Scheduled reviews surface trends that individual error analysis might miss.
Deduplication
Section titled “Deduplication”If the same error occurs multiple times, auralog deduplicates analyses so you’re not flooded with repeated findings. The first occurrence triggers a full analysis. Subsequent occurrences within the dedup window are grouped.
Viewing analyses
Section titled “Viewing analyses”Open your project on auralog.ai, then navigate to Analyses in the sidebar. Each analysis shows the severity badge, summary, and full Claude assessment. Click into an analysis for the detailed view.