New Features in 9.1
Symfony 4 support added.
- Web transactions that use the Symfony 4 framework will now be automatically named based on the route or controller name.
- When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either
high_security: trueor the appropriate
Requests handled by PHP-FPM that result in a 404 error because the script does not exist, or a 403 error because PHP-FPM does not have permission to access the script, will now result in a transaction called
403, respectively, rather than being named after the request URI. This change was made to prevent metric grouping issues, particularly when sites are being probed by potential attackers.
If you wish to capture the actual request URI for analysis, it can be attached to the transaction event under the
request.uriattribute using the following configuration setting:
In version 9.0, Guzzle and Predis execution time could be double counted on application overview and transaction charts in APM, as time could be attributed to both PHP execution and the external or datastore time, respectively. This has been fixed, and charts should now revert back to their previous behavior.
Restarting a transaction from within a Drupal or WordPress hook could result in a segfault. This has been fixed.
Known issues and workarounds
- Potential memory exhaustion for long running transactions. See description under Known issues and workarounds in the PHP 188.8.131.52 release notes.