PHP agent release notesRSS

<div id="watermark">End of Life</div>

<div class="callout-important">
<p>The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see <a href="/docs/agents/manage-apm-agents/installation/update-new-relic-agent">Update the agent</a>. For more information, see <a href="/docs/agents/manage-apm-agents/maintenance/new-relic-agent-plugin-end-life-policy">End-of-life policy</a>.</p>
</div>

Bug Fixes

• Fix to prevent proxy credentials transmission

  This update prevents proxy credentials set in the agent config file from being transmitted to New Relic.

New Features

• Our long-awaited support for Joomla 2.x and 3.x have been added. The PHP agent now instruments and names Joomla transactions without the need for additional plugins.

Bug Fixes

• Prevent injection of page load timing JavaScript when the Content-Type is first set to text/html then changed to something else, such as application/json.
• Fix Zend Framework transaction naming when exit() is called during request processing. Previously, it was possible to exit before the agent set the transaction name. This caused the transaction to be reported as index.php, an issue that most commonly occurs with the Redirect action helper. The agent now correctly names these transactions.
• Fix segfault triggered by JSON encoding when strings to be encoded are marked as UTF-8, yet contain invalid UTF-8 byte sequences.

Notes

Bug Fixes

• Fixed an issue whereby Debian and Ubuntu users running the daemon via the init script may have been unable to start the daemon after upgrading to 4.10.0. This has been fixed by reverting back to the init script used in 4.9.0 and earlier versions.

Notes

End of Life Notices

• The MacOSX/Darwin agent and daemon are now compiled only for Mac OS X 10.6 or higher.

New Features

• Changed the daemon to use openssl 1.0.1h, rather than 1.0.1g.
• Logging to stdout and stderr is now supported when running the daemon in the foreground.
• Created new installer for Ubuntu/Debian systems. If the application name is not present, the installation process will ask for one. Also, Debian/Ubuntu users do not have to run the newrelic-install script.

Upgrade Notices

• The agent now supports PHP 5.6beta4.

Bug Fixes

• Zend externals could be double counted when the cURL adapter was used. In previous versions of the agent, using Zend_Http_Client::setAdapter() with an instance of Zend_Http_Client_Adapter_Curl caused the agent to double count the external call. This has been fixed.
• Prevent real user monitoring javascript injection when a Content-Type header has not been set and the default mimetype is not text/html.

Notes

New Features

• Added new local setting to enable high-security mode. newrelic.high_security = false

  This setting is false by default. When set to true, this setting has the following effects:

  • Data will not be sent to New Relic unless the newrelic-daemon is using SSL.
  • Raw SQL strings will never be gathered, regardless of the value of newrelic.transaction_tracer.record_sql.
  • Request parameters will never be captured, regardless of the value of newrelic.capture_params.
  • The following API functions will have no effect, and will return false: newrelic_add_custom_parameter newrelic_set_user_attributes

  If you change this setting, you must also change the RPM UI security setting. If the two settings do not match, then no data will be collected.

• Introduce new attribute configuration scheme.

  All parameters captured by the agent and created by the newrelic_add_custom_parameter API call are now considered attributes and have a new set of INI configuration options. As a result, the newrelic.capture_params and newrelic.ignored_params configuration options have been deprecated. The newrelic.ignored_params comparison will now be case-sensitive.

  For full information, please see the documentation.

Bug Fixes

• The Laravel 4.0 framework is now supported in a manner analogous to the existing support for Laravel 4.1. (The portion of the routing code that is instrument changed the function names and arguments slightly going from Laravel 4.0 to Laravel 4.1.)
• Fix potential metric grouping issue with Kohana transaction naming. Previously, the agent would treat the first two segments of the request URI as the controller and action when no route was found. Now the agent will use 'unknown' as the transaction name when no route is found. This is consistent with the behavior for other frameworks.

Notes

New Features

• Upgraded to cURL version 7.35 from 7.30.
• Upgraded to OpenSSL 1.0.1g from 1.0.1e.

Bug Fixes

• Fixed an issue that would cause New Relic cross application tracing headers to accumulate during multiple curl_exec() calls.

• Fixed an issue with the installer when the path includes spaces. When newrelic-install.sh was run from a path that included spaces, such as /tmp/new relic/newrelic-php5-4.6.5.40-linux, the installation would fail. This has been corrected.

• Fixed an issue where not all Drupal 8 hooks were instrumented.

  While most Drupal 8 hooks are executed via ModuleHandlerInterface::invoke() and ModuleHandlerInterface::invokeAll(), a handful such as page_build are executed via variable functions by Drupal 8 as they require their arguments to be passed by reference. These hooks are now instrumented correctly.

Notes

New Features

• Support for custom SSL trust stores

  It is now possible to configure the agent to use a custom SSL trust store to authenticate New Relic's servers. In most cases this should not be necessary. The agent ships with the necessary certificates and will use them unless configured not to do so. Caution should be used with these settings. If the trust store does not contain the necessary certificates, the agent will be unable to report data to New Relic. See the documentation for more details.

Bug Fixes

• drupal_http_request responses that redirect are no longer double counted

  External metrics created when drupal_http_request received a HTTP response that was a redirect, such as a 302 Found response, would have their execution time counted and call count incremented twice. The double counting has been removed, and the entire external time will be counted including any redirects.

• Fixed potential OpenSUSE 11.4 segmentation fault during Apache graceful restart

Notes

End of Life Notices

• This release no longer supports BSD (either 32-bit or 64-bit) or the 32-bit variant of Mac OS X.

New Features

• Add Laravel 4.0 support

  Laravel version 4.0 or greater is now supported natively. The naming scheme that we use follows the scheme developed by Patrick Leckey at Intouch Insight, and we are very grateful for his assistance.

  If you are already using the LaravelNewrelicServiceProvider from https://packagist.org/packages/intouch/laravel-newrelic then we recommend removing that from the list of service providers, and relying on our native support instead.

  However, if you are using the custom naming mechanism with 'name_provider' from the intouch/laravel-newrelic package, then those transaction names will take precedence over our automatically generated transaction names. If you do use 'name_provider', please write us and let us know what your namer does so we might extend our built in capabilities.

Bug Fixes

• Improved real user monitoring Javascript insertion.

  The real user monitoring Javascript loader will now be injected after any meta charset tag, ensuring that the meta charset tag is close to the beginning of the page.

  The real user monitoring Javascript footer will no longer be inserted into HTML comments or nested HTML iframes.

• Properly observe newrelic.ignored_params when capturing the request's URL.

  If newrelic.capture_params is true then the agent will capture the values within the $_REQUEST parameter and the full raw URL of the request. The contents of newrelic.ignored_params are used to selectively ignore values from $_REQUEST. The presence of newrelic.ignored_params will now also prevent the capturing of query parameters in the request URL.

• Fix transaction naming when newrelic.webtransaction.name.functions is present.

  When newrelic.webtransaction.name.functions had a non-empty value, the URL was being used as the default web transaction name instead of the PHP filename.

• Print backtrace to log file in the event of a segmentation fault.

  This functionality has been missing since release 4.4.

Notes

We're happy to announce the availability of version 4.5.5.38 of the New Relic PHP Agent, featuring Drupal 8 instrumentation. More details below.

End of Life Notices

• This release no longer supports any backdoor exceptions to run threaded Apache MPM. PHP itself is unstable in this environment.
• This is the last release of the PHP agent for BSD (either 32-bit or 64-bit.)
• This is the last release for the 32-bit variants of Mac OSX. 64-bit Mac OSX will still be supported.
• This release no longer ships with any backdoor support for PHP 5.1.

New Features

• Experimental Drupal 8 support

  Drupal 8 is now supported by the PHP agent's framework detection code. This support should be considered "experimental" given the pre-release nature of Drupal 8. Drupal 8 applications will have their transactions named correctly, and will also generate the same module, hook and view metrics as Drupal 6 and 7 applications. This support can be forced by setting the newrelic.framework configuration setting to drupal8 if auto-detection fails.

Upgrade Notices

• All customers running on old x86 hardware that does not support the SSE3 instruction set (such as early releases of the AMD Opteron) should upgrade to this release as soon as possible. Prior to this release, the daemon inadvertently contained SSE3 instructions which would cause an illegal instruction on such hardware. The only way the SSE3 instructions were executed was when we changed the choice and priority of SSL cipher algorithms at our data center, and we would like to change those priorities by the end of 2Q2014.

Bug Fixes

• Fixed a bug with file_get_contents instrumentation.

  Fixed a bug which would cause the default context to be ignored by file_get_contents when a context parameter was not provided. This issue was causing customer API calls to fail in certain situations. The previous remedy was to disable cross-application tracing to work around the issue. This is now fixed.