Released on: 2017, February 16 - 14:59—Download
The documentation now makes it clear that errors recorded using
do not obey the
ignore_status_codes configuration value.
- Removed unused
Fixed a bug in normalization rules when replacements do not maintain
Better de-duplication of errors when the same error instance is used
Server-side naming rules are now applied even when user defined ones have
Errors reported outside of a transaction now include their stack trace on
error analytics page.
A potential stack overflow in trace serialization has been removed.
Fixed an issue with our Express and domain instrumentation related to a
of transaction state that could result in incorrect transaction names,
Nested background transactions now report the correct number of metrics.