Notice about Important Change: Exception Tracking and Environments
We have recently modified the Exception Tracking fingerprint method used for deduplication of errors to differentiate by environment for all tracked exceptions.
This means that errors appearing in an environment other than „production“, will get a different fingerprint, leading to a new entry in the list, with an empty occurrences counter and its own notification trigger status.
For exceptions in the „production“ environment the fingerprint will stay the same for backwards compatibility reasons, that means no new notifications are triggered and the occurrences counter keep their historical values.
For exceptions in other environments this can trigger notifications on the configured channels such as E-Mail, Slack or Microsoft Teams messages.
This change to the fingerprinting is still behind a feature flag, you can opt into this change going to the „Beta Features“ section of your organization settings screen.
On October 1st, 2022 this feature will be enabled for all customers automatically.
About the author
I am the founder and CEO of Tideways. I started the company over 10 years ago with the mission to move the PHP ecosystem forward, starting with performance. As managing director, I work across product, strategy, and the day-to-day of building a developer-focused SaaS business.
I’m a core contributor to the Doctrine open-source project and a founding board member of the PHP Foundation, which reflects my long-standing commitment to the PHP ecosystem. I particularly enjoy working at the intersection of application performance, developer experience, and the open-source community that makes PHP what it is. Outside of work, I enjoy board games, hiking, and coffee.