Star us on GitHub
Star
Welcome to highlight.io
Company
Mission & Values
Compliance & Security
Open Source
Getting Started
Overview
Fullstack Mapping
Backend / Server
Frontend / Client
Fullstack Frameworks
Product Features
Session Replay
Error Monitoring
General Features
Logging
Integrations
Integrations Overview
Amplitude Integration
ClickUp Integration
Discord Integration
Electron Support
Front Integration
Height Integration
Intercom Integration
Linear Integration
Mixpanel Integration
Segment Integration
Slack Integration
Vercel Integration
Tips
Content-Security-Policy
Local Development
Monkey Patches
Performance Impact
Proxying Highlight
Session Search Deep Linking
Troubleshooting
Upgrading Highlight
Highlight.io Changelog
Changelog 12 (02/17)
Menu
Docs / Highlight Docs / Product Features / Error Monitoring / Grouping Errors

Grouping Errors

Highlight groups errors together based on their error message and stack trace. When an error is thrown, Highlight finds the closest matching error and adds the new error instance to it.

An error is matched if:

  • It has the same error message OR

  • It has the same top stack frame and 3 of the next 4 stack frames are the same (in any order)

  • A stack frame is matched if:

  • It has the same filename, function name, line number, and column number OR

  • It has the same source code and context (if sourcemaps are enabled)

  • If there is no match with an existing error, a new error group is created instead.

    Grouping Rules

    If your errors are in JSON form, you can add JSONPath expressions in your project settings to select parts of your errors that you want to group on. For example, if your errors look like:

    { "type": "StackOverflowError", "user": "alice", "message": "Oh no! You got an error on line 41!!" } { "type": "StackOverflowError", "user": "bob", "message": "Oh no! You got an error on line 50!!" }
    Copy

    They would not be grouped together since the errors are not an exact match and since they were thrown at different lines in your code. In this case, if you wanted to group all errors of the same type into the same error group, you can add an expression $.type in your project settings.