Issue Grouping
Errors grouped by location, related issues linked automatically
Issue Grouping
Section titled “Issue Grouping”Same error 1000 times? One issue with a count.
Three-Tier Grouping
Section titled “Three-Tier Grouping”| Level | Groups by | Example |
|---|---|---|
| Exact location | class + message + file + line | ConnectionError at cache.go:23 |
| Same file | class + message + file | ConnectionError anywhere in cache.go |
| Same error | class + message | ConnectionError: connection refused anywhere |
Falls back to class + message when file/line aren’t available. SDKs extract everything automatically.
Related Issues
Section titled “Related Issues”ConnectionError at cache.go:23 and pubsub.go:12 are different issues, same root cause. LogNorth links them on the issue detail page.
Issue Detail
Section titled “Issue Detail”- Error class, file, line, caller
- Occurrence count, first/last seen
- Frequency heatmap
- Stack trace
- Related issues
Status
Section titled “Status”Active = occurrences in last 24 hours. Everything else = stale. No manual triage.
Mute an issue to stop notifications. It still tracks occurrences.