PHP Release Notes


Restart your web server if you have recently upgraded your agent. This will fix most reporting issues and will load the agent's new features and bug fixes.

PHP agent release notes

Tuesday, June 14, 2016 - 10:55

New Features

  • Ignore Errors

    A new newrelic.error_collector.ignore_errors setting has been added. When configured, this setting can be used to prevent errors, such as E_WARNING, from being reported to New Relic. This setting does not affect errors reported via the newrelic_notice_error API.

  • Ignore Exceptions

    A new newrelic.error_collector.ignore_exceptions setting has been added. This setting accepts a comma-separated list of fully-qualified class names. When an uncaught exception occurs, the agent will not report the exception to New Relic if it is an instance of a class in this list. This setting does not affect errors reported via the newrelic_notice_error API.

Upgrade Notices

  • Guzzle support is now enabled by default. It can be disabled by setting the new newrelic.guzzle.enabled setting to false.

    The guzzle feature flag that was previously used to enable Guzzle support is now ignored.

Bug Fixes

  • The first request in each PHP process would remove any output handlers installed using the output_handler configuration setting for users of PHP 5.4 and later. This has been fixed: existing output handlers will now remain untouched.

  • Transient WordPress hooks now have the unique numbers removed from their names to avoid metric grouping issues.

  • In cases where WordPress' WP_CONTENT_DIR directory was set to a custom value, WordPress plugin metrics were not reported on PHP 5.2 to 5.4, inclusive. This affected users of the popular WP-Skeleton project. This has been fixed.

  • A regression in version 6.3 could cause Guzzle 6 users to lose support for cross application tracing and service maps, in particular when Guzzle 6 was autoloaded as a result of instantiating the only GuzzleHttp\Client object used within the lifetime of the script. This has been fixed.

Wednesday, May 18, 2016 - 10:55

New Features

  • Support for Postgres prepared statements has been added when the pg_prepare and pg_execute functions are used. The agent will now report Datastore metrics as well as capture slow queries.

Bug Fixes

  • Added a workaround for a stack corruption bug in very old versions of the Suhosin extension when used with PHP 5.3 or higher. The bug exists in Suhosin 0.9.29 and older versions only. Newer versions are not affected.

  • Automatic transaction naming could fail in certain circumstances on Laravel 4.1 or higher on PHP 5 when a before route filter was installed. This has been fixed.

  • Automatic transaction naming could fail on Laravel 5.x when a global middleware handled the request without forwarding it deeper into the application. For example, the default Authenticate middleware returns a 401 Forbidden response to unauthenticated requests, preventing proper transaction naming. This has been fixed.

  • A segfault could occur in memory constrained environments, particularly on PHP 7. This has been fixed.

Monday, May 2, 2016 - 12:00

New Features

  • We're proud to announce initial support for Alpine Linux 3.1 and newer. Currently, manual installation is required.
Tuesday, April 12, 2016 - 13:37

New Features

  • The PHP agent now has support for Doctrine 2 DQL Queries. When running a DQL query, it will appear alongside the SQL in both Slow SQLs and Transaction Traces.


  • The agent now includes attributes for HTTP response headers in web transactions:
    • response.headers.contentType
    • response.headers.contentLength

Bug Fixes

  • newrelic.transaction_events.enabled wasn't being observed. This has been fixed.

  • The PHP in SUSE and OpenSUSE Linux was incompatible with some of the agent's features, including RUM and CAT. This issue has been fixed.

Thursday, March 17, 2016 - 10:10

New Features

  • Support has been added for Magento 2.

Bug Fixes

  • Support for Laravel 5.2 has been added. Previously, Laravel 5.2 applications would fail to start with a BadMethodCallException. This was due to the agent's attempted use of a route filter for automatic transaction naming. Automatic transaction naming for Laravel 5.2 no longer relies on a route filter preventing the error. Automatic transaction naming for older versions of Laravel is unaffected.

  • Calling phpversion("newrelic") could return "unreleased" instead of the actual version number. In turn, this caused composer show --platform to report a version of 0. This has been fixed. The version number reported by phpinfo() was not affected by this bug.

  • Fixed a potential segfault when using Zend_Http_Client under PHP 5.5 or 5.6 with OPcache enabled.

Wednesday, March 9, 2016 - 10:39

Bug Fixes

  • Fixed a bug that could cause segfaults on PHP 7.0 when a __call() method was invoked and was slow enough to generate a trace node.
Monday, March 7, 2016 - 10:55

New Features

  • Support has been added for PHP 7.0.
Thursday, February 18, 2016 - 10:55

New Features

  • The agent will now gather more information about the host system, including whether the system is running on Docker or AWS. This will be used to support upcoming features.


  • We've changed the timestamp source for error events, which drive the Error Analytics page. Previously, the event's timestamp was the transaction's start time. It is now the time when the error occurred.
Tuesday, January 26, 2016 - 11:15

New Features

  • Experimental support for instrumenting Guzzle has been added.

    We are very pleased to announce that we've added experimental support for instrumenting Guzzle 3, 4, 5, and 6. Requests made using Guzzle will now show up as externals in the same way as requests made using other instrumented libraries, like curl, drupal_http_request(), and file_get_contents().

    To enable the experimental support, you will need to add a feature flag to your newrelic.ini: newrelic.feature_flag = guzzle. NOTE: We intend to enable the Guzzle support by default in a future release.

    More information can be found on our Guzzle documentation page.

Tuesday, January 19, 2016 - 10:30

New Features

  • WordPress tab in the New Relic UI

    We're pleased to announce a new UI tab just for WordPress-specific data! WordPress applications now show information about their hooks, plugins, and themes.

    For more information, see WordPress-specific functionality.