중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- Fixed a SIGSEGV that happened when Zend Guard encoded files were encountered
- Corrected the way we were determining the domain names of external services that was causing a Transaction Traces display problem (500 error)
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- Fixes up a problem in our SQL parser that was causing Magento app segfaults when accessing admin pages
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- QDrupal support.
- SQL parsing fixes.
- Framework auto-detection when multiple frameworks in use is working now.
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- We now support reporting to multiple applications simultaneously.
- We had a bug where a large data string could cause a segmentation fault.
- A few bug fixes around Wordpress RUM, CakePHP transaction names, and auto-detecting the Zend Framework.
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- RUM and Web Transaction data is available a lot earlier. You no longer need to drive specific amounts of load to get RUM data to appear and early WT's are now recorded.
- Thread safety in the agent has been considerably improved. While we do not officially support the worker MPM, this change will make the agent behave correctly when using a ZTS (Zend Thread Safety) enabled PHP host.
- We can now change the agent log file and log level on the fly, without forcing you to restart your web server just to debug a problem. This is a considerable improvement in the user experience if things go awry and you need to contact support.
- A few minor bugs in the installer script were fixed, most notably creating
/etc/newrelicif it did not exist. - The PHP agent data reporting has been verified to be UTF-8 safe.
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- There was a bug in the
newrelic-installscript that under some circumstances would cause the script to use 100% of the CPU when installed via aptyum. This has been fixed. - The particular User-Agent that was used when a slow transaction is recorded will now be displayed in the "Parameters" drop-down when viewing a transaction trace.
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- Previously, auto-RUM did not work when certain Drupal modules were used (for example the ajax module). All fixed up now.
중요
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes:
- Versions 2.0.0 and 2.0.1 had an error in the spec file that will cause problems for Redhat and CentOS users. After doing an upgrade, the daemon will not be running, and the agent will not be installed. After upgrading to 2.0.2 or later, you must run
newrelic-installand ensure that the daemon is running. Upgrades from 2.0.2 and onwards will no longer have this bug. - On OpenSolaris, the daemon will now always be installed in
/opt/newrelic/binrather than/usr/bin, as/usris a read-only filesystem for many users. The init script will look in this new location first, and none of the other files have moved.