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.

2017, April 19 - 10:00

Upgrade Notices

  • Users of the newrelic-php5 Debian package with PHP 5.2: due to discontinued support of PHP 5.2, upgrading to version 7.x of the PHP agent may result in your applications no longer reporting to New Relic. We advise that you upgrade to a supported version of PHP.

    If upgrading PHP is not possible, you can use apt-get and dpkg to install version 6.9 of the PHP agent and then hold that installed version by running these commands as root:

    apt-get update
    apt-get upgrade newrelic-php5-common=6.9.0.182 newrelic-daemon=6.9.0.182 newrelic-php5=6.9.0.182
    echo 'newrelic-php5-common hold' | dpkg --set-selections

Bug Fixes

  • Automatic transaction naming has been fixed for Symfony 1 users who replaced the controller class via factories.yml with one that did not call sfFrontWebController::dispatch() or sfController::forward().

  • Datastore metrics could not be generated for Predis 0.7 and 0.8 in version 7.1 of the PHP agent. This has been fixed.

  • The agent would not report Zend_Http_Client external calls when the Zend Framework was used directly as a library or indirectly by a framework like Symfony or Magento. This has been fixed.

2017, March 23 - 10:35

New Features

  • Added support for the MongoDB library

    The PHP agent now supports the MongoDB userland library, which is the recommended interface to the mongodb extension. Users of this library will see new metrics in the Databases tab, nodes in transaction traces, and breakdown metrics on individual transaction pages.

  • Database instance information available for Redis, Predis, and MongoDB

    Queries and commands issued using the PECL Redis extension, the Predis library, and the MongoDB library now capture instance information. Transaction traces now include the name of the host (including the port or socket) and database that the query was run against.

    Collection of host information can be disabled by setting newrelic.datastore_tracer.instance_reporting.enabled = false in the newrelic.ini. Similarly, the database name can be omitted with newrelic.datastore_tracer.database_name_reporting.enabled = false.

Upgrade Notices

  • Commands in Predis pipelines are now reported individually, rather than being rolled into a single pipeline query.

Bug Fixes

  • When using PHP 7.0 or 7.1, calling curl_setopt() with the CURLOPT_HTTPHEADER option and an array with elements that have been accessed by reference (for example, with foreach ($array as $k => &$v)) would result in the headers used by New Relic to track external calls overwriting other custom headers. This has been fixed.
2017, February 21 - 09:35

New Relic PHP Agent Release Notes

End of Life Notices

  • The New Relic PHP agent no longer supports PHP 5.2. New Relic highly encourages upgrading to a supported version of PHP - 5.6 or higher. If you would like to continue running the New Relic PHP agent with PHP 5.2, we recommend using version 6.9 of the agent, however please note that we can only offer limited support in this case.

New Features

  • Automatic transaction naming for Magento 2 has been improved. Previously, only requests that were handled by Magento's normal routing were automatically named, which resulted in request types that utilized Magento's interceptor/plugin functionality being named as unknown. This primarily affected users of the REST or SOAP web services.

    REST and SOAP requests will now be named in the Webapi/Rest and Webapi/Soap namespaces, respectively, and will be named according to the service class and method that handle the request.

    Third party modules that add an interceptor on Magento\Framework\App\FrontControllerInterface to override the dispatch() method will result in transaction names that are based on the interceptor class name. New Relic recommends using the newrelic_name_transaction() API function from within the module to name the transaction if you require more precision.

2017, January 19 - 11:15

End of Life Notices

  • Support for PHP 5.2 in the New Relic PHP agent is deprecated and will be removed in a future version. New Relic highly encourages upgrading to a supported version of PHP - 5.6 or higher. If you would like to continue running the New Relic PHP agent with PHP 5.2, we recommend using version 6.9 of the agent, however please note that we can only offer limited support in this case.

New Features

  • Instance information for the pgsql and PDO pgsql extensions is now captured. Slow database queries and transaction traces now include the name of the host (including the port or socket) and database that the query was run against.

    Collection of host information can be disabled by setting newrelic.datastore_tracer.instance_reporting.enabled = false in the newrelic.ini. Similarly, the database name can be omitted with newrelic.datastore_tracer.database_name_reporting.enabled = false.

2016, November 9 - 11:15

End of Life Notices

  • Support for PHP 5.2 in the New Relic PHP agent is deprecated and will be removed in a future version. New Relic highly encourages upgrading to a supported version of PHP - 5.6 or higher. If you would like to continue running the New Relic PHP agent with PHP 5.2, we recommend using version 6.8 of the agent, however please note that we can only offer limited support in this case.

New Features

  • Support for PHP 7.1 has been added.

  • The elapsed time after which an application will be considered inactive can now be configured using the newrelic.daemon.app_timeout setting. This setting is useful when the only transactions being executed are very infrequent, such background processing using a cron job. Previously, an application was considering inactive after ten minutes with no transactions.

  • Instance information for the mysql, mysqli, and PDO mysql extensions is now captured. Slow database queries and transaction traces now include the name of the host (including the port or socket) and database that the query was run against.

    Collection of host information can be disabled by setting newrelic.datastore_tracer.instance_reporting.enabled = false in the newrelic.ini. Similarly, the database name can be omitted with newrelic.datastore_tracer.database_name_reporting.enabled = false.

Bug Fixes

  • Automatic transaction naming for MediaWiki versions 1.18 and later was broken in version 6.3 of the New Relic PHP agent. This has been fixed.
2016, September 21 - 11:00

New Features

  • PHPUnit test events

    Support has been added for the popular unit test library PHPUnit (versions 3.7 to 5.5, inclusive). When enabled, the agent reports test results as custom Insights events. Test suite summary data are sent as TestSuite events, while individual test cases are sent as Test events.

    You can enable this feature in your newrelic.ini file with newrelic.phpunit_events.enabled = true. Depending on your events retention policy, enabling this setting may impact your New Relic billing statement.

    Read more about this feature on our documentation site.

  • Support has been added for Slim Framework 2.x and 3.x.

Upgrade Notices

Bug Fixes

  • Automatic page load timing instrumentation was broken on PHP 5.4-7.0 in certain edge cases: most notably, when the <head> element was not in the first 40kB of the page content, or when the </body> element was not in the last few kilobytes of content. This has been fixed.

  • Prevent real user monitoring JavaScript injection when the Content-Type is first set to text/html then subsequently changed to something else (for example, application/json). This was a regression introduced in version 6.2.

2016, August 25 - 16:00

Bug Fixes

  • When using version 6.6.0 of the PHP agent, instantiating a PDO object with options set could result in PHP crashing at the end of handling a request. This has been fixed.
2016, August 23 - 11:20

New Features

  • Support has been added for Laravel 5.3.

  • Experimental Laravel Queue support.

    Experimental support for the Laravel Queue component has been added. This supports all versions of Laravel from 4.0 to 5.3, inclusive.

    Whether run via artisan queue:listen or artisan queue:work, queue workers will now generate a separate background transaction for each job that is processed. These transactions will be named with the class name of the job, or IlluminateQueueClosure if a closure was queued.

    Additionally, a transaction that queues one or more jobs will be linked to the background transaction(s) that processed those jobs on the transaction map in the New Relic UI.

    To enable this support, you will need to set the laravel_queue feature flag in newrelic.ini. For most users, this will simply involve adding this line:

    newrelic.feature_flag=laravel_queue

    As this is presently an experimental feature, we would welcome feedback — both positive and negative — on whether this feature helps users using the Laravel Queue component better visualise the structure and performance of their applications.

    If all goes well, it is anticipated that Laravel Queue support will be enabled by default in a future version of the agent.

Upgrade Notices

  • Symfony 1 transactions that generate 404 errors due to no routes being matched will now be named based on the module and action that are actually used, rather than the module and action inferred from the request URL. In most cases, this will result in the transaction name being based on the error_404_module and error_404_action Symfony settings.

    Note that, as a result of this change, if the configured 404 action calls sfAction::forward() to forward to another action, the transaction name will be based on the final action. All other uses of sfAction::forward() are unaffected.

Bug Fixes

  • Previously, calling PDO::query with more than one argument resulted in the query being counted under the 'other' category on the Datastores page in the New Relic UI. This has been fixed. The agent will now correctly categorize the query as 'select', 'insert', 'update', or 'delete'.

  • Previously, calling PDO::query with more than one argument resulted in the agent reporting "(unknown sql)" if the query was slow. (i.e., it exceeded the threshold given by the newrelic.transaction_tracer.explain_threshold setting.) This has been fixed.

  • Previously, calling SQLite3::querySingle with two arguments resulted in the query being counted under the 'other' category on the Datastores page in the New Relic UI. This has been fixed. The agent will now correctly categorize the query as 'select', 'insert', 'update', or 'delete'.

  • Previously, calling SQLite3::querySingle with two arguments resulted in the agent reporting "(unknown sql)" if the query was slow. (i.e. It exceeded the threshold given by the newrelic.transaction_tracer.explain_threshold setting.) This has been fixed.

  • Transient Magento 2 tables now have the unique numbers removed from their names to avoid metric grouping issues.

  • Pressflow 6 applications were incorrectly detected as Drupal 7 applications. This could cause POST requests made using drupal_http_request to be converted into GET requests. This has been fixed.

  • Explain plan generation is now always performed on a separate database connection. This has been changed to avoid issues when using MySQL's SELECT FOUND_ROWS() feature.

  • Previously, instrumenting method calls that resolved to __call() or __callStatic() calls could result in crashes on PHP 7. This primarily manifested in crashes for users of certain WordPress plugins (for example, wp-external-links) that registered hooks or actions that used magic methods. This has been fixed.

2016, July 28 - 12:00

New Features

Bug Fixes

  • The behavior of the installer when attempting to detect PHP installations has been tightened up. Previously, a directory structure such as /usr/local/php/php/* would be detected as an installation of PHP in /usr/local/php, as the nested php directory would be wrongly assumed to be a PHP CLI binary. The installer now checks if the nested php (or php-config) is a directory, and ignores the path if so.

    Although this is likely to improve the installer in multiple environments, most noticeably, this fix removes erroneous messages about there being multiple PHP installations when installing the PHP agent within the Docker Hub's official PHP images.

  • Spurious messages like ALERT: oops, unknown child could appear in the PHP FPM log when a New Relic daemon process was started. This has been fixed.

2016, June 14 - 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.

2016, May 18 - 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.

2016, May 2 - 12:00

New Features

  • We're proud to announce initial support for Alpine Linux 3.1 and newer. Currently, manual installation is required.
2016, April 12 - 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.

Notes

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

2016, March 17 - 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.

2016, March 9 - 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.
2016, March 7 - 10:55

New Features

  • Support has been added for PHP 7.0.
2016, February 18 - 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.

Notes

  • 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.
2016, January 26 - 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.

2016, January 19 - 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.

2015, December 15 - 13:30

New Features

  • On Linux, abstract sockets are now supported for agent to daemon communication. An abstract socket can be created by prefixing the value of the port setting in your newrelic.ini file (e.g. newrelic.daemon.port = "@newrelic-daemon") or newrelic.cfg file (e.g. port = "@newrelic-daemon").

  • The daemon can now be passed a --define <setting>=<value> flag that allows setting arbitrary parameters from your newrelic.cfg file. These parameters will take precedence over settings from that file.

  • Drupal 8 requests that are successful full page cache hits for anonymous users (handled by Drupal\page_cache\StackMiddleware\PageCache) are now given the name WebTransaction/Action/page_cache.

  • Support for automatically naming transactions has been added for Symfony 2.8 and 3.0.

  • Support for automatically naming transactions has been added for MediaWiki 1.18.0 and newer.

Upgrade Notices

  • It is now possible to disable reporting of errors for exceptions that are handled by an exception handler installed with set_exception_handler() by enabling the newrelic.error_collector.ignore_user_exception_handler setting.

  • Calls to newrelic_notice_error with improper parameters will no longer record an error with the message "?". Instead, no error will be recorded. newrelic_notice_error will now return true if an error is saved, null if the arguments are invalid, and false otherwise. If newrelic_notice_error is called with two parameters and the second parameter is not a valid exception, no error will be recorded: The first parameter is now entirely unused.

Bug Fixes

  • On Redhat Enterprise Linux 7 and related systems such as CentOS and Fedora, the systemctl start|stop newrelic-daemon commands were not working due to a bug in the newrelic-daemon init script when executed by systemd. This has been fixed.

  • On some Linux systems, an SELinux policy could prevent the newrelic-daemon from determining the correct hostname. Affected systems were unable to report data because a valid hostname is required by New Relic. This has been fixed. This issue could also prevent the newrelic-daemon from determining the correct hostname when running in a chrooted environment, or any environment in which access to the /proc filesystem is limited.

  • Detection of Zend Framework 2.5 and later was unreliable when the framework was installed via Composer. This has been fixed.

  • Detection of Laravel 5.1 and later was unreliable when artisan optimize was used. This has been fixed.

  • The agent now sends the attribute request.headers.contentLength as an integer rather than a string.

Pages