Tideways automatically detects PHP fatal errors and exceptions and then de-duplicates (or aggregates) them. Error details include the message, stacktrace, and context information. These details help you fix your customer’s bugs as quickly as possible.
Error de-duplication aggregates, or avoids duplicating, errors which happen either at the same place or for the same reason. This functionality helps ensure that you have a more realistic, and less obscured assessment of errors occurring in your application. De-duplication is achieved based on a hash (or fingerprint) of:
The exception class name
All frames in the stacktrace of the exception/error, using only the class/function names, not the file name and the line where the error occurred.
When combined with the Deployment Events feature, then error occurrences since the last release to a production environment are reset to zero, re-triggering "New Exception" notifications, if the error still occurs.
Tideways provides four error-tracking workflow options; these are:
Resolve changes status to "Closed". The error automatically re-opens if/when the error reoccurs.
Ignore changes the error’s status to "Ignored", based on the stacktrace (fingerprint) leading to this error and does not show it again.
- Always Ignore
Always Ignore changes the error’s status to "Ignored", based on the exception class' name, meaning everywhere this exception class is thrown.
- Don’t notify
Don’t notify disables notifications via integrations for this error, based on the stacktrace (fingerprint).