We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should be able to control how the exceptions are being grouped.
Out of the box the errors are grouped by name and message. This is not very unique.
I want to be able to provide a proc to generate custom grouping identifiers
get_group_identifier: ->(exception, env, data){ [ exception.name, exception.message, env.ip, exception.backtrace.first, ].join("/") }
Without this feature the error grouping feature seems not very useful for generic use.
The text was updated successfully, but these errors were encountered:
Yes this would be great - we enabled error_grouping and it doesn't seem to do anything. Getting 1000s of emails of the same errors within minutes -.-
@Martin91 I know that you originally implemented this - would it be possible to add options for more specific grouping?
Sorry, something went wrong.
No branches or pull requests
We should be able to control how the exceptions are being grouped.
Out of the box the errors are grouped by name and message. This is not very unique.
I want to be able to provide a proc to generate custom grouping identifiers
Without this feature the error grouping feature seems not very useful for generic use.
The text was updated successfully, but these errors were encountered: