PHP agent release notesRSS

Bug Fixes

• Fix an edge case segfault that could occur in situations where the daemon failed to initialize.

New Features

• Added support for the PHP Agent on Heroku

  We now support running PHP Applications on Heroku using the New Relic for Web Apps add-on.

  For more information, see PHP agent and Heroku and the Heroku Dev Center documentation.

New Features

• Added two new attributes to transaction events: errorMessage and errorType. These attributes allow for the tracking of errors within the Insights product. As a result, error messages will no longer be recorded if the agent is in high-security mode.
• Background tasks will now create Transaction events which can be tracked in the Insights product.

Bug Fixes

• Fixed request queuing metrics support The PHP Agent will now allow the leading t= prefix to be optional when parsing HTTP_X_REQUEST_START and X-Request-Start headers. Previously, the header would be treated as absent if no leading t= was included.
• Fixed presentation of the newrelic.daemon.proxy setting in phpinfo() The phpinfo() function will now display a value of no value as the default for the newrelic.daemon.proxy setting. Previously, it would incorrectly display a value of ***INVALID FORMAT***.

<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.