PHP agent release notes

PHP agent v10.10.0.1

Tue, 30 May 2023 00:00:00 +0000

New Relic PHP Agent v10.10.0.1

Security

New features

ARM64 binaries are now available for PHP 8.0, 8.1, and 8.2. Please see our docs for installation instructions.

Bug Fixes

Additional handling/msg in the case of both DT and CAT being enabled #658

Important end-of-life information

Support for PHP versions 5.5 and 5.6 will end June 2023.

Support statement

Support for ZTS builds ended with release v9.19.0.309 and those binaries are no longer provided.
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages which are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.11.0.3

Tue, 13 Jun 2023 00:00:00 +0000

New Relic PHP Agent v10.11.0.3

Security

New features

Drupal 9.4 now reports hooks and modules

Bug Fixes

Important end-of-life information

Support for PHP versions 5.5 and 5.6 IS DEPRECATED. We recommend upgrading to at least PHP 7.0

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.12.0.1

Wed, 20 Sep 2023 00:00:00 +0000

New Relic PHP agent v10.12.0.1

New features

Improved Guzzle 5 and 6 detection.
Adds newrelic_set_error_group_callback API, allowing an application to register a callback function with the PHP Agent that will generate a custom error group name. Read more about this API here.
Adds newrelic_set_user_id API, allowing an application to assign a unique user ID to a transaction. Read more about this API here.
Adds a link to documentation to the install error message when installing an unsupported version of PHP.
Verified support for Guzzle 7.
Verified support for Laravel 9 and 10.

Bug fixes

Reduces the log level for a Drupal-specific message to a more appropriate value.
Fixes a bug in Infinite Tracing where distributed traces were missing a parentID attribute that caused issues displaying a distributed application in the UI.

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL in early 2024.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.13.0.2

Tue, 03 Oct 2023 00:00:00 +0000

New Relic PHP agent v10.13.0.2

New features

The PHP agent now supports APM local log decoration. See the PHP Agent Logs In Context page for more information.

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL in early 2024.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.14.0.3

Mon, 13 Nov 2023 00:00:00 +0000

New Relic PHP agent v10.14.0.3

Security

Updated the Golang version used to build the Daemon from 1.20 to 1.21.1.

New features

The PHP agent now supports APM log context attributes. See the PHP Logs In Context page for more information.
The agent now supports detecting Docker container IDs via cgroup v2.

Bug fixes

A fix was added that removes erroneous deprecation warnings which could appear using the mysqli extension with PHP 8.1 and later.
When PHP 8+ is built in debug mode, zpp/arginfo mismatches are now Fatal Errors. Fixed the mismatches that existed in the code base.
Resolved an issue impacting duplicative telemetry data.

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL in early 2024.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages. Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.15.0.4

Wed, 20 Dec 2023 00:00:00 +0000

New Relic PHP agent v10.15.0.4

New features

Adds support for PHP 8.3

Bug fixes

Removes a warning message for NULL Docker ID

Miscellaneous improvements

Several performance-related improvements

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.16.0.5

Tue, 23 Jan 2024 00:00:00 +0000

New Relic PHP agent v10.16.0.5

Security

Agent debugging log obfuscation improved for relevant agent configuration values.

New features

INI value newrelic.framework.wordpress.hooks.options that allows tailoring WordPress instrumentation. Using plugins_callbacks or threshold values offer different instrumentation levels with reduced agent’s overhead. See https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-framework-wordpress-hooks-options and https://docs.newrelic.com/docs/apm/agents/php-agent/frameworks-libraries/wordpress-specific-functionality/ for more details.

Miscellaneous improvements

Several performance-related improvements for agent when using the Wordpress framework.

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.17.0.7

Wed, 21 Feb 2024 00:00:00 +0000

New Relic PHP agent v10.17.0.7

New features

The PHP agent now sends up package detection information that can be viewed on the environment page. This feature will be enabled by default and you can find more information about this INI configuration here.

Bug fixes

Fixes a locale bug in DT W3C trace state header generation

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.18.0.8

Mon, 04 Mar 2024 00:00:00 +0000

New Relic PHP agent v10.18.0.8

New features

PHP's Just-In-Time Compilation is no longer disabled when the PHP Agent is enabled. PHP has this on-by-default starting with PHP 8.0.

Bug fixes

Fixes a bug where the agent would not properly automatically detect the Lumen framework

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.19.0.9

Mon, 18 Mar 2024 00:00:00 +0000

New Relic PHP agent v10.19.0.9

New features

Always link error traces using transaction ID

Bug fixes

Fixes a bug where the agent would not properly automatically detect the Magento 2 framework
Fixes error categorization and prioritization by adding support for E_RECOVERABLE_ERROR, E_DEPRECATED, E_USER_DEPRECATED error types. E_RECOVERABLE_ERROR, E_DEPRECATED, E_USER_DEPRECATED are no longer recorded as Error.
Fixes error recording for PHPs 8.0+: user_error_handler is honored, and the agent will not record an error if user_error_handler handled the error.

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.2.0.314

Mon, 03 Oct 2022 00:00:00 +0000

New Relic PHP Agent v10.2.0.314

New Features

newrelic-daemon: Informational messages will be logged if the number of connected applications falls below 25 or exceeds 200. #534

Bug Fixes

agent: Fixed SIGSEGV in Drupal 7 drupal_http_request instrumentation for PHP 7.4, 8.0 and 8.1. #538
agent: Fixed displaying newrelic.application_logging*.enabled value in PHP info output. #535
agent: When forwarding application logs, send the log message as a well-formed JSON string that is correctly escaped. #540
agent: Reduce the severity of a log message when an agent does not detect environmental variables. #539

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.

PHP agent v10.20.0.10

Mon, 06 May 2024 00:00:00 +0000

New Relic PHP agent v10.20.0.10

New features

Add support for Yii v2 framework
Verified support for Drupal 10 framework
Add supportability metrics for PHP packages that provide major version
Update default for newrelic.framework.wordpress.hooks.options to "plugin_callbacks"

Bug fixes

Fix error reporting for errors converted by PHP to exceptions
Improve user exception handler instrumentation for PHPs 8.0+
Fix warning from mysqli when explaining slow SQL queries
Fix json struct tag for docker id
Improve communications of PHP packages data to the backend

Security

Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 in newrelic-daemon
Bump golang.org/x/net from 0.20.0 to 0.23.0 in newrelic-daemon

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends upgrading the agent regularly and at least every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
For the latest information on supported PHP versions and platforms, consult the PHP agent compatibility and requirements page.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.21.0.11

Mon, 20 May 2024 00:00:00 +0000

New Relic PHP agent v10.21.0.11

Bug fixes

fix(agent): End guzzle's external segment for rejected request (https://github.com/newrelic/newrelic-php-agent/pull/883)

Security updates

security(daemon): Upgrade golang to 1.22 (https://github.com/newrelic/newrelic-php-agent/pull/890)

Important end-of-life information

Support for PHP versions 7.0 and 7.1 will EOL on June 1st, 2024

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.22.0.12

Wed, 26 Jun 2024 00:00:00 +0000

New Relic PHP agent v10.22.0.12

Bug fixes

Fix MongoDB instrumentation for PHP 8.0+
Fix error where Guzzle 7+ was sending up major version for VM
Install correctly on minimalist operating systems
Fix Doctrine 2.18+ detection
Slim transaction naming updates
Fix rhel and alpine init scripts

Important end-of-life information

Support for PHP versions 7.0 and 7.1 has been EOL'd and will be removed in the next release. If you are still using these versions, please make sure to pin your agent version.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.3.0.315

Thu, 03 Nov 2022 00:00:00 +0000

New Relic PHP Agent v10.3.0.315

We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date.

Important end-of-life information

Support for 32 bit and FreeBSD binaries were deprecated with release v9.19.0.309 and are no longer shipped starting with this release.
Support for ZTS binaries was deprecated with release v9.17.0.300 and will be removed in a release in the near future.
For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it is highly recommended to disable the auto-update mechanisms for the PHP agent packages. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Alternatively, the PHP agent packages can be version pinned to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed, removing support for the required, unsupported features. This would disrupt APM data collection.
The PHP agent packages which are affected are:
- newrelic-php5
- newrelic-php5-common
- newrelic-daemon
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

New features

APM logs in context. Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about this feature see PHP: Configure logs in context, and additional configuration options are available PHP agent configuration: Config file. To learn about how to toggle log ingestion on or off by account see Disable automatic logging. #556

Bug fixes

agent: Fix to ensure datastore segments do not create children segments. #511
agent: Updates instrumentation lookups for PHP 7.4+. Using reserved field of zend_func's op_array is no longer reliable as other extensions are unreliably using this shared area which then corrupts the opcache enough that it no longer provides lookups. The new method no longer relies on the agent storing any information in the reserved array of a zend_function. Fixes: Laravel 9 PHP8.1 Not reporting errors, All transactions are "unknown" bug

PHP agent v10.4.0.316

Mon, 12 Dec 2022 00:00:00 +0000

New Relic PHP Agent v10.4.0.316

Important end-of-life information

Support for ZTS binaries was deprecated with release v9.17.0.300 and will be removed in a January 2023 release.
For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it is highly recommended to disable the auto-update mechanisms for the PHP agent packages. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Alternatively, the PHP agent packages can be version pinned to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed, removing support for the required, unsupported features. This would disrupt APM data collection.
The PHP agent packages which are affected are:
- newrelic-php5
- newrelic-php5-common
- newrelic-daemon
You should check the PHP agent compatibility and requirements page for the latest information on supported PHP versions and platforms.

New features

Code Level Metrics (CLM) has been introduced and is set to off by default.
- CLM allows you to gather more data associated with each span, including line numbers, function names, filepaths, and namespaces.
- Use this ini value to start using CLM!

Improvements

Custom Event Limit default reservoir size has been increased and is now configurable.
- The default maximum number of custom events gathered per minute has been increased from 10,000 to 30,000.
- This value can now be modified with this ini value.

PHP agent v10.6.0.318

Mon, 13 Feb 2023 00:00:00 +0000

New Relic PHP Agent v10.6.0.318

New features

Code Level Metrics (CLM) is now enabled by default.
- CLM allows you to gather more data associated with each span, including line numbers, function names, filepaths, and namespaces.
- CLM was introduced in release 10.4.0.316.
- Use this ini value to configure CLM.

Important end-of-life information

Support for PHP versions 5.5 and 5.6 will end June 2023.

Support statement

Support for 32 bit and FreeBSD ended with release v9.19.0.309 and those binaries are no longer provided.
Support for ZTS builds ended with release v9.19.0.309.
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.8.0.323

Wed, 22 Mar 2023 00:00:00 +0000

New Relic PHP Agent v10.8.0.323

New features

Added healthcheck log level for the daemon, allowing for precise monitoring of the number of connected applications.

Bug Fixes

Fixed debian package installation occasionally requiring an additional manual step #634
Fixed a warning from agent when passing null as the second parameter to curl_multi_exec #605. Special thanks to dejanceltra for finding and fixing this issue!

New Contributors

This release contains the first contribution to the New Relic PHP Agent from community member dejanceltra! Thanks!!

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.5.0.317

Wed, 18 Jan 2023 00:00:00 +0000

New Relic PHP Agent v10.5.0.317

Bug Fixes

agent: Fixed #577 - Large performance regression in 10.3.0. #588
agent: Fixed #594 - Instrumentation from opcache.preload for PHP 8.1. #595
agent: Fixed sending Supportability/Logging/Forwarding/PHP/% and Supportability/Logging/Metrics/PHP/% application logging configuration metrics. #575

Support statement

Support for 32 bit and FreeBSD ended with release v9.19.0.309 and those binaries are no longer provided.
Support for ZTS builds ended with release v9.19.0.309.
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.9.0.324

Wed, 05 Apr 2023 00:00:00 +0000

New Relic PHP Agent v10.9.0.324

Security

Updated the Golang version used to build the Daemon from 1.9 to 1.20

New features

Bug Fixes

Important end-of-life information

Support for PHP versions 5.5 and 5.6 will end June 2023.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.0.0.312

Wed, 29 Jun 2022 00:00:00 +0000

New features

The agent now incorporates updated backend communications which will pave the way to efficiently add new features.
Agent tags are now supported by the PHP agent.

Bug fixes

Infinite tracing is now disabled at startup if distributed tracing is disabled since it is required (Issue 452).
Removed a debugging statement that was no longer needed and could lead to large log file usage if verbose debugging was enabled (Issue 447).
Additional fixes to significantly reduce the number of duplicated log messages in some situations where large log consumption had been observed in the past.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document.

PHP agent v10.7.0.319

Wed, 08 Mar 2023 00:00:00 +0000

New Relic PHP Agent v10.7.0.319

Important note

If the following error occurs when installing the newrelic-php5 Debian package:

Setting up newrelic-php5 (10.7.0.319) ...
Unknown PHP version: 8.2

Please run the newrelic-install installation program which will complete the installation of the PHP agent and set up the correct symlink to the PHP extension directory.

New features

Added Support for PHP 8.2.

Important end-of-life information

Support for PHP versions 5.5 and 5.6 will end June 2023.

Support statement

Support for 32 bit and FreeBSD ended with release v9.19.0.309 and those binaries are no longer provided.
Support for ZTS builds ended with release v9.19.0.309.
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v10.1.0.313

Mon, 19 Sep 2022 00:00:00 +0000

New features

APM logs in context support for Monolog 2 and 3
- The PHP agent will now generate logging metrics for Monolog (versions 2 and 3) to allow seeing the rate of log messages by severity.
- These metrics are enabled by default and are controlled by a config file directive.
- The PHP agent can also now forward log messages from Monolog for viewing on the New Relic platform.
- Log forwarding is currently disabled by default (can be enabled by a config file directive), and will be enabled by default in a future release.
To learn more about APM logs in context, see the logs in context docs.

For more information about logs in context and the PHP agent check the PHP logs in context docs.
Enhanced redis/PhpRedis support Thank you to Michael Grunder for contributing to the PHP agent and extending the existing redis/PhpRedis support!

New contributors

As mentioned above, community member Michael Grunder made his first contribution to the New Relic PHP agent. Thanks!!!

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document.

PHP agent v11.0.0.13

Tue, 30 Jul 2024 00:00:00 +0000

New Relic PHP agent v11.0.0.13

New features

Add countDocuments mongodb instrumentation for PHP 7.x (#926)
Doctrine 3.x verified and supported.
Laravel 11 verified and supported. Note: excludes Laravel Horizon support.

Security updates

security(daemon): Upgrade golang to 1.22.5 (#940)
Instructions for configuring New Relic apt repository have been updated to no longer use deprecated apt-key utility. Please use the updated instructions

Important end-of-life information

Support for PHP versions 7.0 and 7.1 has been EOLed and is removed in this release. If you are still using these PHP versions, please make sure to pin your agent version to 10.22.0.12.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.1.0.14

Mon, 26 Aug 2024 00:00:00 +0000

New Relic PHP agent v11.1.0.14

New features

Drupal 11 verified and supported.

Bug fixes

Fixes an issue where newrelic.so was not able to resolve the strlcpy symbol on Linux using glibc version 2.39 or higher.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.10.0.24

Wed, 25 Jun 2025 00:00:00 +0000

New Relic PHP agent v11.10.0.24

New features

Security RX: Composer runtime API will be used by default to detect packages used by PHP applications #1055

Security updates

#1089 - security(daemon): upgrade golang to 1.24.4 #1090
#973 - security: rotate New Relic's public key used to verify signature of http://apt.newrelic.com/debian/ APT repository. See here for details.

Bug fixes

fix(agent): Fix undefined behavior when Composer runtime API is used #1086

Notice

Default value for `newrelic.code_level_metrics.enabled` INI changes in next release

newrelic.code_level_metrics.enabled = true

This change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected.

Support statement

The following frameworks/libraries that the PHP Agent has previously EOL'd support for will be removed in the next release:
- Guzzle 3.x
- Kohana
- Silex
- Symfony 1.x-3.x
- Zend 1.x-2.x
PHP Agent support for the following library/framework versions will end September 30, 2025:
- WordPress 5.9
- Drupal 8.x
- Laravel 6.x, 8.x
- PHPUnit 8.x
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.3.0.16

Mon, 21 Oct 2024 00:00:00 +0000

New Relic PHP agent v11.3.0.16

New Features

Memcached instance metrics with host name
Dockerized Daemon now supports arm64

Bug Fixes

Improve magic file recognition performance
Tarball installer checks for existing ini in mods-available directory
Don't skip arguments when calling mysqli::real_connect
- Huge thanks to @kovshenin for their community contribution!!

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.6.0.19

Tue, 18 Feb 2025 00:00:00 +0000

New Relic PHP agent v11.6.0.19

New features

Added support for aws-sdk-php SQS version 3 instrumentation
Added support for php-amqplib version 3.7 RabbitMQ instrumentation
Added support for Yii version 1.1 instrumentation
The agent will now generate MessageBroker metrics and attributes

Security

Daemon Golang version upgraded to 1.23.6

Bug fixes

Fixed daemon to enable go vet check on pull requests
Fixed memory leak in Laravel Queue Instrumentation
Fixed nr_header_create_distributed_trace_map memory leak

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.4.0.17

Mon, 09 Dec 2024 00:00:00 +0000

New Relic PHP agent v11.4.0.17

New feature

Added support for CakePHP framework versions 4.x and 5.x.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every three months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.5.0.18

Mon, 13 Jan 2025 00:00:00 +0000

New Relic PHP agent v11.5.0.18

New feature

Adds support for PHP 8.4

Bug Fixes

Fix Drupal error and exception handling
- This fix may conflict with the error and exception handling of the Drupal new_relic_rpm module. If you have this module installed and you aren't seeing your errors reported natively by the agent, try disabling the new_relic_rpm module. If you still experience issues after disabling this module, please reach out to New Relic Support.
Fix error where externalCallCount should be added to the transaction and not just the error event.
Address aws-sdk-php versioning change.

Security

Daemon golang.org/x/net module upgraded to v0.33.0

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every three months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.7.0.21

Wed, 19 Mar 2025 00:00:00 +0000

New Relic PHP agent v11.7.0.21

New features

feat(agent): Adds label forwarding to log events
feat(agent): Add AWS Lambda Relationship

Security

security(daemon): bump golang.org/x/net from 0.33.0 to 0.36.0

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.8.0.22

Mon, 21 Apr 2025 00:00:00 +0000

New Relic PHP agent v11.8.0.22

New features

feat(agent): Add AWS DynamoDB Instrumentation

Security

security(daemon): bump golang to 1.24.2
security(daemon): bump golang.org/x/net from 0.36.0 to 0.38.0

Notice

The default Code Level Metrics configuration will change in an upcoming release from enabled to disabled. If you do not use Code Level Metrics, you should see no impact and will not have to take any action. If you do rely on Code Level Metrics, ensure that your newrelic.ini configuration file has the newrelic.code_level_metrics.enabled INI setting uncommented and set to true. e.g: newrelic.code_level_metrics.enabled = true This change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.0.0.25

Mon, 11 Aug 2025 00:00:00 +0000

New Relic PHP agent v12.0.0.25

Bug fixes

Improve drupal hook map error logging.
Fix legacy package detection issues for Security RX.

Notice

Default value for `newrelic.code_level_metrics.enabled` INI has changed in this release

As previously communicated, the default Code Level Metrics Observability in IDE configuration will change in an this release from enabled to disabled. If you do not use Code Level Metrics, you should see no impact and will not have to take any action. If you do rely on Code Level Metrics, ensure that your newrelic.ini configuration file has the newrelic.code_level_metrics.enabled INI setting uncommented and set to true. e.g:

newrelic.code_level_metrics.enabled = true

This change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected.

Support statement

As previously communicated, the following frameworks/libraries that the PHP Agent has previously EOL'd support for will be removed in the this release:
- Guzzle 3.x
- Kohana
- Silex
- Symfony 1.x-3.x
- Zend 1.x-2.x
PHP Agent support for the following library/framework versions will end September 30, 2025:
- WordPress 5.9
- Drupal 8.x
- Laravel 6.x, 8.x
- PHPUnit 8.x
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.9.0.23

Tue, 13 May 2025 00:00:00 +0000

New Relic PHP agent v11.9.0.23

New features

feat(agent): Add auto-instrumentation of object oriented hook implementations introduced in Drupal 11.1

Other

refactor(agent): Improve performance of user functions instrumentation for PHPs 8.0+

Notice

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v11.2.0.15

Mon, 30 Sep 2024 00:00:00 +0000

New Relic PHP agent v11.2.0.15

New features

If possible, use composer runtime API to collect information about PHP packages used by the application for New Relic Vulnerability Management. This feature is controlled via the new newrelic.vulnerability_management.composer_api.enabled INI value (off by default).
Symfony 6 & 7 support verified.

Security

Daemon Golang version upgraded to 1.23.1.

Bug fixes

Fixes newrelic_notice_error() API for PHP 8+ when using the 4 parameter API variant.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.1.0.26

Tue, 09 Sep 2025 00:00:00 +0000

New Relic PHP agent v12.1.0.26

New features

Add sampling controls based on upstream w3c trace sampling decision - #1104
- See new ini values here
Add configuration option to skip instrumentation of framework exception handlers - #1113
- See new ini value here

Security

Bump golang version to 1.25.1

Bug fixes

Fix potential memleak when calling newrelic_end_transaction(true) - #1072
Don't attempt any instrumentation when not recording - #1112

Support statement

PHP Agent support for the following library/framework versions will end September 30, 2025:
- WordPress 5.9
- Drupal 8.x
- Laravel 6.x, 8.x
- PHPUnit 8.x
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.2.0.27

Wed, 19 Nov 2025 00:00:00 +0000

New Relic PHP agent v12.2.0.27

New Features

Laravel 12 verified and supported.
Laravel Horizon is now supported on Laravel 10.x+ and PHP 8.1+.

Security

#1129 - Bump golang version 1.25.3 - #1130

Bug Fixes

fix(agent): Fix Laravel queue job exception handling - #1122

Support Statement

In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided.
As previously announced, PHP Agent support for the following library/framework versions has officially ended as of September 30th, 2025:
- WordPress 5.9
- Drupal 8.x
- Laravel 6.x, 8.x
- PHPUnit (all versions)
PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026:
- For the following library & framework versions, New Relic recommends you upgrade to the latest supported version:
  - Symfony 4.x
  - Laravel 7.x, 9.x, 10.x
  - Slim 3.x
- Support for the following libraries & frameworks will be discontinued for all versions:
  - MediaWiki
  - Zend Framework
  - Lumen
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.4.0.29

Mon, 12 Jan 2026 00:00:00 +0000

New Relic PHP agent v12.4.0.29

New Features

Added PHP 8.5 support

Bug Fixes

Addressed deprecation warnings which could be seen when using Symfony 7.4 and 8.0

Support Statement

In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided.
PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026:
- For the following library & framework versions, New Relic recommends you upgrade to the latest supported version:
  - Symfony 4.x
  - Laravel 7.x, 9.x, 10.x
  - Slim 3.x
- Support for the following libraries & frameworks will be discontinued for all versions:
  - MediaWiki
  - Zend Framework
  - Lumen
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.3.0.28

Mon, 15 Dec 2025 00:00:00 +0000

New Relic PHP agent v12.3.0.28

New Features

Added aws-sdk-php Kinesis Data Streams Instrumentation

Security

Bump golang version to 1.25.5

Bug Fixes

Fixed issue where daemon did not clear package cache on restart

Support Statement

In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided.
PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026:
- For the following library & framework versions, New Relic recommends you upgrade to the latest supported version:
  - Symfony 4.x
  - Laravel 7.x, 9.x, 10.x
  - Slim 3.x
- Support for the following libraries & frameworks will be discontinued for all versions:
  - MediaWiki
  - Zend Framework
  - Lumen
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.5.0.30

Tue, 10 Feb 2026 00:00:00 +0000

New Relic PHP agent v12.5.0.30

New Features

Symfony 8 verified and supported.
#1147 - agent: update instrumentation to be compatible with MongoDB 2.x #1154, #1158

Security updates

#1160 - daemon: bump go toolchain to 1.25.7 #1163

Bug Fixes

agent: fix table naming for queries with EXTRACT function #1159
agent: fix drupal hook instrumentation #1157

Support Statement

In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided.
PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026:
- For the following library & framework versions, New Relic recommends you upgrade to the latest supported version:
  - Symfony 4.x
  - Laravel 7.x, 9.x, 10.x
  - Slim 3.x
- Support for the following libraries & frameworks will be discontinued for all versions:
  - MediaWiki
  - Zend Framework
  - Lumen
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v12.6.0.34

Tue, 31 Mar 2026 00:00:00 +0000

New Relic PHP agent v12.6.0.34

New Features

Laravel 13 verified and supported.
Instrumentation will be disabled per request when PHP Fiber usage is detected. (#1178)

Security updates

Bump go version to 1.26.1 (#1179). Addresses #1173.
Update golang grpc dependencies (#1185).

Bug Fixes

Fixed backoff tier when retrying daemon connections (#1169)
Fixed installing newrelic.ini into mods-available on Debian/Ubuntu (#1170). Addresses (https://github.com/newrelic/newrelic-php-agent/issues/1168).
Improved SQL parsing logic (#1164)

Support Statement

As previously communicated, for best practices and security, the rpm signing key has been rotated and the rpm installation page reflects the up to date changes.
PHP Agent support for the following library & framework versions will be discontinued and New Relic recommends you upgrade to the latest version supported by the vendor:
- Drupal 7 support will be discontinued in all PHP Agent Versions after September 30, 2026
- Drupal 9 support will be discontinued in all PHP Agent Versions after September 30, 2026
As previously communicated, the PHP Agent support for the following library & framework versions is discontinued in all PHP Agent releases after February 28th, 2026:
- For the following library & framework versions, New Relic recommends you upgrade to the latest version supported by the vendor:
  - Symfony 4.x
  - Laravel 7.x, 9.x, 10.x
  - Slim 3.x
- Support for the following libraries & frameworks will be discontinued for all versions:
  - MediaWiki
  - Zend Framework
  - Lumen
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.

The PHP agent packages that are affected are:

newrelic-php5
newrelic-php5-common
newrelic-daemon

PHP agent v2.0.2.65

Wed, 25 May 2011 00:00:00 +0000

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-install and 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/bin rather than /usr/bin, as /usr is 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.

PHP agent v2.0.5.98

Sat, 11 Jun 2011 00:00:00 +0000

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

PHP agent v2.0.3.89

Mon, 06 Jun 2011 00:00:00 +0000

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.

PHP agent v2.1.1.134

Wed, 13 Jul 2011 00:00:00 +0000

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/newrelic if it did not exist.
The PHP agent data reporting has been verified to be UTF-8 safe.

PHP agent v2.1.3.164

Tue, 26 Jul 2011 00:00:00 +0000

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.

PHP agent v2.2.1.181

Wed, 03 Aug 2011 00:00:00 +0000

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.

PHP agent v2.2.1.185

Sat, 06 Aug 2011 00:00:00 +0000

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

PHP agent v2.2.2.193

Tue, 16 Aug 2011 00:00:00 +0000

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)

PHP agent v2.2.3.196

Thu, 18 Aug 2011 00:00:00 +0000

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 up not detecting background jobs when run from cpanel
Corrected url path problems resulting in 500 errors for web transactions when on CakePHP

PHP agent v2.3.5.21

Thu, 22 Sep 2011 00:00:00 +0000

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:

Version number change. Starting with this release version numbers only use 2 segments, as in 2.3. The remaining bits simply reflect the build level.
Naming web transactions for several new frameworks has been added: Joomla (1.5 and 1.6), Kohana (3.1 and 3.2), Magento 1.6 and MediaWiki 1.16.
Drupal auto-RUM has been modified to inject the header earlier so that all CSS and JavaScript loading is taken into account, and it now also works when the advagg module is installed.
Drupal modules support. This needs to be enabled by setting newrelic.framework.drupal.modules=1. This will display how much time is being spent in each Drupal module, including sub-modules. When enabled this feature is accessed from the "Modules" tab of the App Server menu.
Support for MongoDB has been added.
New API call newrelic_ignore_apdex() has been added. This allows users to ignore certain time-consuming activities (such as downloading a file) from their overall apdex score.
PHP namespace separator () no longer causes a malformed JSON error when it appears in a transaction trace.
SQL parser improved to better detect table names and avoid database metric explosion on certain SQL statements.
Calls to Drupal's drupal_http_request()are now correctly identified as external service calls.
Several speed improvements to further reduce the impact when Drupal Modules support or top100 is enabled.
MacOSX agent no longer aborts when PCRE isn't loaded.
RUM scripts improved to load the footer script after the page has fully loaded so that it does not impact user-visible performance.
API functions newrelic_get_browser_timing_header() and newrelic_get_browser_timing_footer() now take an optional bool argument (that defaults to true) that indicates whether or not script start and end tags should be inserted around the returned JavaScript.
Small memory leak when adding metric names fixed.
Daemon startup scripts now correctly ignores comment lines

PHP agent v2.4.5.24

Tue, 04 Oct 2011 00:00:00 +0000

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 several coredump issues related to Drupal Modules.
Updated SQL parser to ignore C-style comments in SQL.
Added OpenSolaris x64 support.
Now possible to instrument internal PHP functions but only after consultation with technical support, as it adds additional overhead.

PHP agent v2.4.5.25

Fri, 07 Oct 2011 00:00:00 +0000

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:

Very minor change to the daemon to remove a pause on startup if the daemon happened to start within 30 seconds of the top of the minute.

PHP agent v2.5.5.29

Thu, 10 Nov 2011 00:00:00 +0000

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:

New feature: slow SQL. This is very similar to transaction traces but instead records the 10 slowest SQL statements, along with a stack trace of where the SQL was executed from in your program.
Fixed a bug in the automatic insertion of RUM headers and footers where they could sometimes be inserted multiple times (especially the footer).
The "Drupal Modules" feature can now be enabled and disabled on a per-directory basis like most other configuration settings.
A few minor bug fixes that had the potential for causing random agent crashes, although these were very infrequent.

PHP agent v2.4.5.26

Tue, 01 Nov 2011 00:00:00 +0000

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:

Very minor change to change the KB URL paths in error messages and to correct the LICENSE.txt file to include the full copyright and permissions notices for various open source components used withing the agent.

PHP agent v2.6.5.41

Tue, 13 Dec 2011 00:00:00 +0000

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:

The apt repository is now digitally signed, and in order to update the agent from this repository for Ubuntu or other Debian-like systems you will need to import the new GPG key using the following command (please note the trailing minus sign!):

wget -O - https://download.newrelic.com/NEWRELIC_APT_2DAD550E.public | sudo gpg --import --batch --no-default-keyring --keyring /usr/share/keyrings/download.newrelic.com-newrelic.gpg
A very special and big thank you to Nick Calugar of IGN Entertainment for suggesting improvements to the way in which Zend and Magento transactions are named. For these two frameworks the transaction naming is now more accurate and adds less overhead than the previous mechanism used to name transactions. This also fixed an issue where Magento transaction names sometimes had garbage characters in them or sometimes even PHP script fragments. In both cases the transaction is named 'module/controller/action' as it is for other frameworks.
Another very special thank you to Roderick Smyth of Arithon in Dublin for absolutely invaluable help during the beta testing period and for testing the OCI8 support.
Significant improvements to automatic Real User Monitoring (auto-RUM). The most important change is that auto-RUM is now implemented as an output filter so it now works for all frameworks, not just Drupal and Wordpress. It is also considerably more reliable as a result, as modules and other changes to the framework no longer impact how we insert the RUM header and footer. If you previous had to manually insert RUM headers and footers, you are strongly encouraged to re-enable auto-RUM and comment out your existing manual calls. To go with this change there is a new API call, 'newrelic_disable_autorum()' that you can call to prevent auto-RUM from running for a given transaction. For example you may want to disable auto-RUM for AJAX calls.
Regardless of how it is invoked, the RUM footer will now never be ejected if the header was not also ejected in the same transaction. This prevents JavaScript errors if the header somehow fails to get inserted.
The RUM header and footer have been very slightly modified to add a missing semicolon after the last script command. This also prevents some browsers and compliance analyzers from complaining about the JavaScript.
Support for the MemCache-like features of Redis has been added. This is by no means full support for Redis, just those portions of the Redis API that map cleanly onto the existing MemCache metrics. They will show up in the overview graphs as MemCache activity, so if you use both MemCache and Redis the data will be merged, just as the overview for different SQL databases is merged.
Considerably improved support for multi-framework sites (where more than one framework is in use for multiple parts of the same site). Instrumentation for framework-specific functions is now isolated on a per-request basis, so multiple requests handled by one PHP instance will no longer be confused by by the sudden change in framework.
The logrotate script no longer conflicts with the version installed by the New Relic Server Monitor.
Implemented a timeout for agent-to-daemon communication so that if the daemon becomes unresponsive for whatever reason, the agent will no longer hang (and thus appear to crash Apache) waiting for the daemon to recover.
Correctly ignore user notice errors in the error handler.
Added support for the deprecated but still frequently used mysql_db_query function.
Added support for the Zend framework's Zend_Http_Client::request() method to track external service calls better in Zend.
Added the ability to use the syntax newrelic.appname="%{VARIABLE}"when setting the application name. This will use the SAPI's environment variable lookup mechanism to find VARIABLE and set the application name accordingly.
The REPLACE SQL command verb will now be recognized and unique metrics generated for it rather than being lumped into "other".
A thread mutex deadlock issue on OpenSolaris has been resolved.
Support for the pure PHP MemCached client from Wikia has been added.
file_get_contents() now shows up in the external services tab if the object being retrieved is remote and uses HTTP or HTTPS.
The newrelic_notice_error() now has a third invocation form, which takes a string and an Exception object. If the string is provided it is used as the error message. If it is empty then a default string in a format similar to Exception::__toString() is automatically generated and used as the error message. The exception object provided will be used to create the stack trace for the exception so that you can see the stack trace at the time of the exception, rather than the stack trace at the time of displaying the exception.
If you enable the capturing of request parameters by setting newrelic.capture_params = true, you can now also set newrelic.ignored_params to a comma-separated list of sensitive parameters to be excluded from any data sent to New Relic.
Support for CakePHP 2.0 has been added, and the CakePHP 1.2 and 1.3 support has been overhauled a little based on feedback from the author, Mark Story. CakePHP 1.2 applications will now be considerably faster when New Relic is enabled due to the new transaction naming mechanism. It will also ensure that transactions are correctly named even if you have implemented your own custom dispatcher class.
MongoDB now correctly instruments the update command.
Added support for Oracle databases by instrumenting the two most critical calls: oci_parse() and oci_execute(). No other OCI calls are currently instrumented.
A bug that had the potential to cause a segmentation violation has been fixed.
Several performance improvements that further reduce the overhead of the agent.

PHP agent v2.6.5.44

Fri, 16 Dec 2011 00:00:00 +0000

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 is an outstanding issue with the Zend View component where it kills the output buffer that auto-RUM relies on, so for this environment you will need to disable auto-RUM by setting newrelic.browser_monitoring.auto_instrument = 0 and doing manual instrumentation for the time being.
Fixed a potential spin-loop that would cause the agent to consume 100% of the CPU if the underlying OS did not allow the daemon connection (even if the daemon was up and running).
Only apply Real User Monitoring scripts to HTML content.
Fix an issue if auto-RUM encountered content it couldn't parse, it would cause a segmentation violation and cause Apache to core-dump.

PHP agent v2.6.5.55

Mon, 09 Jan 2012 00:00:00 +0000

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 several issues that would cause Apache to core-dump. Not all users would see these faults, but a few did and those bugs have been fixed.
Removed support for the PHP-only MediaWiki memcached client that was added in 2.6.5.41, as the code that was added to support this was part of what was causing random core dumps. It will be re-added in a future release.
Use less system stack space when hooking PHP functions so that PHP code that is massively recursive runs less risk of overflowing the stack.
Corrected the way the Mac OSX client was being built so it works on OSX 10.5.
Fixed a potential buffer over-run error in the Zend and Magento framework code that would be provoked if a controller name was significantly longer than the module name.
Removed the backslash from the list of illegal characters in SQL table names as some customers actually use it.
Prevent a file descriptor leak if you do a soft restart of Apache.

PHP agent v2.6.5.57

Mon, 16 Jan 2012 00:00:00 +0000

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 an issue where using file_get_contents() could end up being mis-interpreted as an SQL node and cause a core-dump. This would only happen when Slow-SQL traces were enabled.

PHP agent v2.7.5.64

Tue, 21 Feb 2012 00:00:00 +0000

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:

Support for PHP 5.4RC8 or higher. Please note that versions prior to RC8 will not work correctly, especially not with auto-RUM. Also please heed the advice that the PHP developers themselves give about using the 5.4 release candidates: do not use it in production.
Added the frequently-requested newrelic_set_appname() API that will allow you to change the name of the application on the fly. This should be called as early as possible, and cannot be called after the RUM footer has been sent.
Fixed an occasional segmentation violation caused by the Slow SQL feature, especially when using the command line version of PHP.
Fixed an occasional segmentation violation caused by auto-RUM.
Fixed a problem where the ZTS-enabled version of the agent would cause a segmentation violation when used on the command line.
Removed the colon from the list of characters that are invalid in SQL table names, and provide a mechanism to disable table name checking completely.
Fixed a small (about 10 bytes per request) memory leak.
Fixed an issue that would sometimes cause PHP execution time to not show up in the application overview graph.
If you call the newrelic_ignore_transaction() API function, no longer produce automatic RUM headers and footers for that transaction.

PHP agent v2.7.5.69

Thu, 15 Mar 2012 00:00:00 +0000

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:

Updated to work with Apache 2.4
The auto-RUM buffer is now erasable, but doing so will obviously prevent auto-RUM from inserting the RUM header and/or footer.
Fixed a problem where WordPress blogs would result in metric explosion due to their database table naming scheme
Support transactions that last longer than 35 minutes. Long-running cron jobs will no longer report negative time.

PHP agent v2.8.5.73

Tue, 24 Apr 2012 00:00:00 +0000

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:

Considerably more detailed transaction traces, reducing to almost nil the amount of "uninstrumented time" in TT graphs.
Detailed TT's (the so-called "top100" feature) are now enabled by default.
Reduced the overhead for detailed TT's dramatically, bringing it to within 2-3% of the agent speed without them enabled.
Fixed a memory bug that was causing garbage metric names to be sent to the daemon and then on to RPM.
Fixed erroneous behavior of the "newrelic_end_of_transaction()" API call. Previously it did not correctly end the transaction.
The fix to reduce metric grouping issues with WordPress table names no longer causes the table names to produce a warning in the logfile.

PHP agent v2.9.5.78

Thu, 07 Jun 2012 00:00:00 +0000

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:

This is a very minor patch release to the 2.9 series of PHP agent. It contains only 1 small fix which only affects customers who use more than 1024 Apache worker processes:

Added missing ulimit command to daemon startup script to correctly set the maximum number of open file descriptors that the daemon can handle, in case the system default is too low.

PHP agent v2.9.5.76

Thu, 24 May 2012 00:00:00 +0000

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:

Added support as an external service for HttpRequest::Send
Added limited support for curl_multi_exec. This will now show up as an external services call but will not provide insight as to how many or which web sites were handled by the function.
CakePHP transaction naming considerably improved
The daemon and agent now support up to 2048 file descriptors (up from 1024 on Linux). This is most relevant to larger sites that have > 1024 Apache worker processes.
The daemon behaves better if the maximum number of open file descriptors is exceeded.
The Debian installer no longer changes the permissions of the log directory if the system administrator had changed them. Also, if the log directory didnt exist (first time installation) default the ownership of the directory to the Apache user and group, if Apache is installed.
SQL parser fix to avoid being confused by the words "from" or "into" appearing in table names.

PHP agent v3.1.5.120

Mon, 03 Dec 2012 00:00:00 +0000

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.

Bugfixes

This release is a bug-fix release only and adds no new features to the agent. The following bugs introduced in 3.0/3.1 have been fixed:

Fixed two segmentation violations that would occur after calling the newrelic_set_appname() API call. One had the potential to affect all users, the other was restricted to customers who used prepared SQL statements both before and after the call to newrelic_set_appname().
Fixed a problem with the Solaris init scripts which made the incorrect assumption about the process ID of init.
Fixed a small memory leak that affected CodeIgniter, CakePHP and Drupal applications.

PHP agent v3.1.5.111

Tue, 20 Nov 2012 00:00:00 +0000

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

This release of the New Relic PHP agent adds two major new features, and includes several important bug fixes and stability improvements. The new features are:

Key Transaction Support, and
Real User Monitoring improvements.

Key transactions (discussed here) allow you to mark transactions that are important to your specific business needs and can have their own Apdex settings and error metrics.

The Real User Monitoring (RUM) improvements allow you to link select transaction traces with browser traces. Other improvements include the ability for RUM to work with multiple application names, and delivery of the RUM JavaScript file will only use the https protocol if the main page was also delivered via https. The new newrelic_set_user_attributes() API call can now also be used to add additional data to browser traces. Please see this page for details.

The following smaller improvements and bug fixes have been made:

Fixed an agent segmentation fault that occurred during Slow SQL processing at the end of a transaction.
Fixed a daemon segmentation fault that occurred if the agent communication with the daemon was interrupted for any reason.
Fixed a memory leak in the agent when the maximum number of Slow SQL statements for a transaction was reached.
Fixed an error that was preventing the daemon from re-spawning a copy of itself if the worker daemon died due to a segmentation fault.
Updated the newrelic_set_appname API call to no longer send the transaction thus far to the daemon unless you give it an argument explicitly requesting this behavior. This considerably reduces the overhead of changing application names on the fly.
Updated the newrelic_end_transaction API call to allow you to decide whether or not the transaction should be sent to the daemon. It is by default.
Fixed an error in the installer script where the license key was not being inserted into the INI file correctly.
Functions with custom instrumentation (newrelic.transaction_tracer.custom) will now produce metrics that can be used in custom dashboards.
If your application produces a Content-Length header, automatic RUM ("auto-RUM") will no longer inject the RUM header and footer, which would invalidate the content length calculated by your application.
The NR_INSTALL_KEY environment variable is now correctly obeyed.
The daemon is now compiled to support showing a backtrace in the event of a segmentation violation.

PHP agent v3.1.5.136

Tue, 08 Jan 2013 00:00:00 +0000

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

Revert to using a UNIX-domain socket for agent to daemon communication. This is the same mechanism used in the 2.x and 1.x series of agents. This was done for speed purposes. The default socket path is the same as it was for the older versions of the agent: /tmp/.newrelic.sock. The newrelic.daemon.port option in the INI file and the portoption in the daemon configuration file (newrelic.cfg) can now take either a path to a UNIX-domain socket, or an integer in the range 1-65534. If you use a path, then a UNIX-doman socket will be used. If you use an integer, then a TCP socket will be used on the specified port.
Correct the "banner" displayed in the log file to show the version of the running PHP. Previously it was incorrectly showing the version that we had compiled with.
On platforms that support it, now attempt to display a stack dump in the unlikely event that the agent receives a SIGSEGV signal due to a bug. Displaying this stack is not always possible but when it works it is a big help for technical support to diagnose the exact cause of the problem. This feature existed in the 2.x series of agent but was not working correctly in the 3.x series until now.
Fixed a problem where a communications failure between the agent and daemon when sending a transaction trace would result in a core dump (rare).
Fixed a problem with Memcache metrics using the wrong metric name.
Fixed a coredump that would occur when sending SQL tracers that were both un-obfuscated and contained lots of UNICODE characters (very rare).
If a SIGSEGV signal is ever received make sure the daemon exits completely so that it can be respawned. Under certain conditions it could become "stuck" which would slow down the agent and stop all data from being sent to New Relic.

PHP agent v3.1.5.141

Fri, 25 Jan 2013 00:00:00 +0000

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.

Bugfixes

Correctly destroy a thread mutex that was sometimes not being destroyed.
Correctly obey newrelic.capture_params INI setting in regards to URL get parameters.

PHP agent v3.1.5.137

Wed, 16 Jan 2013 00:00:00 +0000

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.

Bugfixes

Fixed an issue where massive log files were created if the agent received a SIGSEGV.
Fixed an issue that occasionally caused SIGSEGV's when using RUM2.

PHP agent v3.2.5.143

Tue, 12 Feb 2013 00:00:00 +0000

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

Show full URL of external calls in transaction trace nodes. Username, password, and query parameters are stripped from the URL.
Fixed a bug causing time spent in background CLI tasks to be included in main overview graph.
Fixed a bug causing incorrect custom tracer metrics in the event of out of order clock times.
Look for and respond to 'X-NewRelic-ID' header in all incoming http requests. This change helps improve the correlation of performance between services in a service-oriented architecture for a forthcoming feature. In the meantime, if you wish to disable the header, set 'newrelic.cross_process.enabled=0' in your .ini file.

PHP agent v3.3.5.154

Thu, 11 Apr 2013 00:00:00 +0000

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

Increase visibility into errors by adding error type (eg E_WARNING) to captured errors.
Refactor changes to local daemon to increase simplicity and stability.
Prevent duplicate log file descriptors on Apache restart.

PHP agent v3.2.5.147

Wed, 27 Feb 2013 00:00:00 +0000

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

Prevent potential memory leak by daemon when connecting applications.
Ensure that the agent will not block when attempting to connect to the daemon.
Fix potential locking bug during daemon's application harvest cycle.

PHP agent v3.3.5.160

Tue, 23 Apr 2013 00:00:00 +0000

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 bug that was causing the daemon to spin and consume 100% of a CPU
Removed the 45 application limit

PHP agent v3.3.5.161

Thu, 25 Apr 2013 00:00:00 +0000

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

The previous fix for the daemon spin was incomplete. This release correctly fixes the problem we identified.

PHP agent v3.4.5.167

Wed, 01 May 2013 00:00:00 +0000

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

The agent can now write an audit log that shows an unencrypted stream of all information sent to New Relic’s servers. The audit log can potentially use up a lot of disk space, so it’s best to use this on an as-needed basis.
In addition to wall-clock time, CPU time (a.k.a. “burn”) is included at the top of transaction traces in the New Relic user interface.
SSL connections to New Relic collectors are now kept alive for the entire application data harvest, rather than re-negotiated for each application during the harvest.
The agent will attempt to auto-detect client SSL certificates on FreeBSD.
This agent release also includes various bug fixes, including ones concerning obfuscated SQL processing and cross-application data leakage.

PHP agent v3.5.5.170

Wed, 15 May 2013 00:00:00 +0000

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

Drupal module instrumentation has been enhanced.
The agent can now instrument Drupal hooks and view execution.
The agent now reports the 50 most frequently called functions and the 50 slowest functions for individual requests. This data is now used on the Transaction Trace Summary tab allowing a more accurate and complete display of slowest components.
Auto-detection of local SSL certificates has been improved.
Various stability and performance enhancements.

PHP agent v3.5.5.172

Wed, 22 May 2013 00:00:00 +0000

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

Patch release to fix an occasional segmentation fault when using Drupal.

PHP agent v3.6.5.178

Mon, 03 Jun 2013 00:00:00 +0000

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

Data uploads to the New Relic collectors now default to SSL. SSL can be disabled through the configuration file.
The agent now carries its own SSL certificate bundle, improving portability across platforms.
Queuing time display has been corrected for certain dispatcher configurations.
Various stability and performance enhancements.

PHP agent v3.7.5.7

Tue, 11 Jun 2013 00:00:00 +0000

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

Magento transaction naming has been refined
MySQL errors will now be recorded properly under PHP 5.1
Request queue timing can be specified with X-Request-Start as well as HTTP_X_REQUEST_START
Other small bugfixes

PHP agent v3.8.5.11

Thu, 29 Aug 2013 00:00:00 +0000

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

Preliminary support for Cross Application Tracing has been added. The following external calls are supported.
- curl_exec()
- file_get_contents()
- httprequest::send()
Communication between the agent and the daemon process has been improved, fixing a rare issue that could affect data quality.
Fixes a rare issue where too many daemon processes could be launched.
Various bug fixes and stability improvements.

PHP agent v4.0.5.18

Mon, 30 Sep 2013 00:00:00 +0000

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

Support for histograms and percentiles
PHP 5.5 support added
PHP 5.1 deprecated
Various bug fixes and stability improvements.

PHP agent v3.9.5.13

Thu, 12 Sep 2013 00:00:00 +0000

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

Support for two additional external calls has been added to cross application tracing.

Zend_Http_Client::request()
drupal_http_request()

PHP agent v4.10.0.60

Mon, 30 Jun 2014 00:00:00 +0000

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

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.

PHP agent v4.11.0

Thu, 31 Jul 2014 00:00:00 +0000

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.

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.

PHP agent v4.10.1.62

Tue, 01 Jul 2014 00:00:00 +0000

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

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.

PHP agent v4.11.1

Mon, 25 Aug 2014 00:00:00 +0000

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

PHP agent v4.12.0

Thu, 28 Aug 2014 00:00:00 +0000

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.

New Features [#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 [#bugs]

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

PHP agent v4.13.0

Wed, 10 Sep 2014 00:00:00 +0000

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.

New Features [#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.

PHP agent v4.14.0

Wed, 24 Sep 2014 00:00:00 +0000

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.

New Features

Support for agent-side configuration of application labels using the newrelic.labels INI setting has been added. New Relic enables you to label and organize your apps so they "roll up" into an unlimited number of meaningful categories. You can also easily sort, filter, and page through all the applications on your account's Applications list. See the New Relic APM documentation and the PHP agent (newrelic.ini) settings documentation for more details.

Bug Fixes

Fixed issue that could prevent capturing database table name for prepared statements on PHP 5.6.

PHP agent v4.13.1

Thu, 11 Sep 2014 00:00:00 +0000

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.

Bug Fixes

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

PHP agent v4.15.0.74

Tue, 28 Oct 2014 00:00:00 +0000

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.

New Features

The daemon now uses openssl 1.0.1j, rather than 1.0.1h.
Support for generating explain plans for SELECT queries issued using the PDO MySQL driver has been added.

When the newrelic.transaction_tracer.explain_enabled setting is enabled and a SELECT query is issued through a PDO connection to MySQL that takes longer than newrelic.transaction_tracer.explain_threshold, an explain plan will be generated and will appear within the query analysis section of the slow SQL trace.

Bug Fixes

Fix an issue that could cause some background task metrics to be attributed to web transactions and some web transaction metrics to be attributed to background tasks. This could affect Drupal customers whose applications use drupal_cron_run.
This release changes the handling of HTTP Referer headers to always strip query parameters before reporting to New Relic. Previously, any query parameters present in a Referer header would be reported to New Relic by the PHP agent.
Fix an issue where urls using the file: protocol scheme with curl_exec() would cause the agent to record external metrics. This has been corrected and the agent will no longer treat file urls as external services.

PHP agent v4.17.0.83

Fri, 02 Jan 2015 00:00:00 +0000

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.

Bug Fixes

Fix a memory leak affecting newrelic_add_custom_parameter API function.

PHP agent v4.1.5.24

Mon, 28 Oct 2013 00:00:00 +0000

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

Transaction traces containing many consecutive calls to curl_multi_exec will now show the cumulative time as a single node. Previously the transaction trace would show one node for each call.
We fixed segmentation faults when restarting Apache on Darwin and FreeBSD.
We corrected an issue in the newest Debian-based Linux distributions that prevented the newrelic.ini file from being installed properly.
A warning message is put in the agent log when newrelic_name_transaction() fails.

PHP agent v4.17.0.79

Fri, 19 Dec 2014 00:00:00 +0000

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.

Bug Fixes

The agent now uses the route pattern as the transaction name for unnamed, closure-based routes under Laravel. For example, the following route will now be named hello/{name} instead of GET/index.php.

Route::get('hello/{name}', function($name) { return "Hello ${name}!"; });

Previously the agent could fail to detect the Laravel framework when artisan optimize was used. This has been fixed.
When the agent cannot determine a transaction name for the Laravel framework, the name "unknown" will be used instead of "laravel-routing-error". The latter implied the cause of the failure may have originated within Laravel itself rather than solely within the agent's instrumentation.

PHP agent v4.18.0.89

Tue, 17 Feb 2015 00:00:00 +0000

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.

New Features

Support for synthetic monitoring.

The PHP agent now gives you additional information for requests from synthetic monitors when the newrelic.synthetics.enabled setting is enabled. The agent records more transaction traces and events for synthetic-originated requests to give you a clearer look into how your application is performing around the world.

For more details, see https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/getting-s...
Add a new newrelic_record_custom_event API function.

This API function allows you to add custom events to New Relic's Insights product. For more information, please see: https://docs.newrelic.com/docs/insights/new-relic-insights/adding-queryi...
The daemon now uses openssl 1.0.1k, rather than 1.0.1j.

Bug Fixes

The agent properly recognizes prepared statements constructed with mysqli_stmt::__construct().
The newrelic-install script has been fixed to once again work for users with custom extension_dir settings.

Notes

The ability to set the appname to a string like: %{FOO} and have FOO expand into the environment variable was removed.

PHP agent v4.19.0.90

Wed, 04 Mar 2015 00:00:00 +0000

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.

New Features

Unified view for SQL database and NoSQL data stores
The agent will now provide a breakdown of SQL operations according to the database product being used. This is in addition to the existing breakdown of SQL statements and operations. For NoSQL data stores, the agent will now provide a similar breakdown of the operations performed.
Memcached and Redis time reported separately
Previously, the agent grouped Memcached and Redis operations into a single Memcached category. This is no longer the case. Time spent performing Memcached or Redis operations are separate.

Bug Fixes

Laravel transaction naming improvements
Prior to this version, Laravel applications that had replaced the default router service could find that, in some circumstances, their transactions would be named as "unknown" rather than being correctly named from the route. This has been improved: replacement router services will now get appropriate transaction naming provided that they either implement filtering or ensure that the same events are fired as the default Laravel router.

PHP agent v4.20.0.92

Wed, 01 Apr 2015 00:00:00 +0000

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.

Release Unavailable

Due to a bug in this release related to the new explain plan support for MySQLi, we have decided to remove it from our download servers. Instead, we recommend installing version 4.20.1, which includes a fix for this bug.

New Features

Support for Laravel 5.0.

We are pleased to announce support for the latest Laravel release: Laravel 5. Sites and applications using Laravel 5.0 are now automatically detected and named in the same way as Laravel 4 applications.
Support for explain plans with MySQLi.

The existing support for generating explain plans for slow SELECT queries with the PDO MySQL driver has been extended to MySQLi. Explain plans are controlled by the newrelic.transaction_tracer.explain_enabled and newrelic.transaction_tracer.explain_threshold settings. These plans can be seen in the query analysis section of the slow SQL trace page in APM.

Explain plans will be generated for queries issued through mysqli_query, mysqli_real_query, and mysqli_stmt_execute, as well as their OO equivalents mysqli::query, mysqli::real_query, and mysqli_stmt::execute.

Please note that the mysqli_multi_query API is not currently supported, and that explain plans are not generated for multiple (semicolon separated) queries.
Added Memcache connection monitoring.

The connect and pconnect functions (and their OO counterparts) of the Memcache extension are now instrumented, and will generate metrics. As a result, if there is a problem with calling those functions, it will now be visible within New Relic.

Bug Fixes

Laravel 4 App::after() filters are no longer overridden.

In certain circumstances, the improved Laravel transaction naming code in version 4.19 of the PHP agent could result in filters registered using Laravel 4's App::after() method no longer being executed. This has been fixed.

Upgrade Notices

The daemon now uses openssl 1.0.1m, rather than 1.0.1l.
The daemon now uses curl 7.41.0 rather than 7.40.0.

PHP agent v4.20.1.93

Thu, 02 Apr 2015 00:00:00 +0000

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.

Bug Fixes

MySQLi segfaults fixed.

Version 4.20.0 could cause the PHP agent to segfault when certain types of parameters were bound to mysqli_stmt objects. This has been fixed.

PHP agent v4.20.2.95

Mon, 13 Apr 2015 00:00:00 +0000

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.

Bug Fixes

Support for mixed Laravel 4 and 5 environments has been improved.

Web servers serving both Laravel 4 and Laravel 5 applications from the same process pool could see autoloader errors in the Laravel 4 applications after the first load of a Laravel 5 page. This has been fixed, and mixed environments should now work as expected.
Laravel detection has been improved.

Starting with Laravel 5.0.15, applications with an optimized classloader use a new location for the optimized "compiled.php" file. Previously, the agent would fail to detect Laravel in this circumstance. The agent now looks in this new location as well as the old location for Laravel auto-detection.

PHP agent v4.22.0.99

Wed, 03 Jun 2015 00:00:00 +0000

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.

New Features

Support for the Predis library

The PHP agent now supports the Predis library. Users of this library will see new metrics in the Database tab, nodes in transaction traces, and breakdown metrics on individual transaction pages. Pipelining multiple commands will result in those commands being grouped and treated as a single command metric named pipeline.

Note that our Predis support does not include instrumentation for commands wrapped in MULTI and EXEC via the Predis client's transaction method. We also do not instrument the executeRaw or monitor methods of Predis, nor its PubSub functionality.

Increased specificity of PECL Redis metrics

Metrics made for the PECL Redis extension will now more closely match the name of the function called. For example, the redis::setex method will now create a metric with the text setex, rather than simply set.

Named Laravel Artisan commands

Background transactions that are Laravel Artisan commands are now named. Instead of being named unknown, Laravel Artisan commands will now be named based on the command. For instance, the command ./artisan cache:clear will result in a background transaction named Artisan/cache:clear.

UTC offsets in agent logfiles

The log file format has been extended to include the UTC offset of the local time zone. This makes it easier to match log entries to time windows in the New Relic UI.

PHP agent v4.23.0.102

Wed, 08 Jul 2015 00:00:00 +0000

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.

New Features

Exceptions that are uncaught and handled only by a last resort exception handler installed via set_exception_handler() will now generate errors that can be viewed in the APM UI. Previously they would not be sent to New Relic at all.

As a result of this, some customers will see more errors in the APM UI than they had previously seen.

Bug Fixes

In certain circumstances, such as an exception being thrown during database connection, errors generated by uncaught exceptions could result in the stack trace shown in APM including function argument values, which could potentially expose database passwords and other sensitive information. This problem has been fixed.

We now catch these formerly-uncaught exceptions and thus have control over how the stack trace is built, ensuring that function argument values will no longer show up in those stack traces.

PHP agent v4.21.0.97

Thu, 30 Apr 2015 00:00:00 +0000

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.

New Features

Zend Framework 2 transaction naming support

Support has been added for naming transactions automatically based on ZF2 route names. Transaction naming will work with routes set in module.config.php, or anything else using the setMatchedRouteName method of Zend\Mvc\Router\RouteMatch (or the same methods of the corresponding HTTP and Console routers).

For example:

'router' => array( 'routes' => array( 'route1' => array( ... ) 'route' => '/foo[/:bar][/:baz]', 'constraints' => array( ... ), 'defaults' => array( ... 'route2' => array( ... )

Anything the router matches to route1 will be named route1 regardless of URL, parameters or controller. 404 errors and similar will be named "unknown".

Silex transaction naming support

Support has been added for naming transactions automatically based on Silex controller names. If a route name has been set using the Controller::bind() method, then that will be used, otherwise the default controller name generated by Silex will be used instead.

For example:

// This will be named with the autogenerated "GET_hello_name". $app->get('/hello/{name}', function ($ name) { ... });

// This will be named "hello", as bound. $app->get('/hello/{name}', function ($ name) { ... })->bind('hello');

Automatic transaction naming will work on all Silex 1.x versions provided the default kernel service has not been replaced with an object of a type other than Symfony\Component\HttpKernel\HttpKernel. If the kernel service has been replaced with something else, you will need to continue to use the newrelic_name_transaction function to name your transactions.

End of Life Notices

memcacheDuration attributes have been removed.

A bug in version 4.19 of the PHP agent removed support for memcacheDuration attributes in Transaction events. We have decided not to restore this functionality, as these durations are now accounted for in databaseDuration attribute values.

Bug Fixes

databaseDuration attributes have been restored.

A bug in versions 4.19 and 4.20 of the PHP agent resulted in databaseDuration attributes no longer being attached to Transaction events. These have been restored, with one change: they now also include time spent in Memcached operations, as these are now unified with other datastores in New Relic APM.
Fix application name rollup ordering issue.

When using application rollup names, the agent had the restriction that any name could only appear as the first rollup name once, which prevented the simultaneous connection of a;b and a;c. This restriction has been removed.

PHP agent v4.23.1.107

Fri, 10 Jul 2015 00:00:00 +0000

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.

Bug Fixes

Under certain circumstances, version 4.23.0 of the PHP agent could crash when newrelic_set_appname() or newrelic_end_transaction() were called and a custom exception handler had been installed via set_exception_handler(). This has been fixed.
Under certain circumstances, Drupal applications that rely on the newrelic_set_appname() API function to start transactions would not see the Drupal tab in the New Relic UI. This has been fixed.

PHP agent v4.23.3.111

Mon, 20 Jul 2015 00:00:00 +0000

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.

Bug Fixes

This release fixes a rare bug where applications that had the ionCube loader enabled and called set_exception_handler() repeatedly could crash.

New Features

Exceptions that are ignored by Laravel 5's default exception handler will also now be ignored by the PHP agent's error reporting feature. This can be controlled by adding or removing entries in the dontReport property of Laravel's default exception handler, as described in the Laravel documentation.

PHP agent v4.2.5.26

Wed, 13 Nov 2013 00:00:00 +0000

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've added support for Symfony 2. Symfony 2 controller names will now show up in the web transactions view. This is an intermediate step leading up towards future Drupal 8 support.
We have improved Zend Framework 1 transaction naming in order to reduce instances of metric grouping issues.
We have tidied up our code for handling slow SQL statements.

PHP agent v4.23.4.113

Fri, 24 Jul 2015 00:00:00 +0000

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.

Bug Fixes

A memory leak that could occur when a large number of PDO or mysqli statements were prepared and executed has been fixed.

PHP agent v4.2.5.27

Wed, 20 Nov 2013 00:00:00 +0000

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

Fix a segfault that could occur when the daemon was unable to bind to its listening socket during startup. The watcher process would then attempt to spawn a new daemon process leading to another segfault creating a loop. This loop would then cause the daemon log file to grow indefinitely. All customers are encouraged to upgrade.

PHP agent v4.3.5.33

Wed, 11 Dec 2013 00:00:00 +0000

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

This release of the PHP agent automatically marks Drupal cron requests as background tasks, improves the categorization of PHP errors within the New Relic UI, and fixes several bugs. Additionally, the internals of the agent have been significantly refactored to improve the stability and performance of the agent.

New Features

Treat Drupal cron requests as background tasks

Drupal cron requests (identified by calls to drupal_cron_run()) will now be counted as background tasks (not web transactions) regardless of how they are started. Previously, it was necessary to use the newrelic_background_job() API to explicitly mark Drupal cron requests as background tasks.
Use the exception class as the category for errors

Errors created using the newrelic_notice_error() API function with an exception will be grouped according to the exception's class. Previously, all errors were grouped under 'NoticedError'.

See https://docs.newrelic.com/docs/php/the-php-api#api-notice-error
Limit the maximum number of nested PHP function calls

The agent will now limit the maximum number of nested function calls within PHP applications. This is to provide protection against stack overflows due to infinite recursion. Previously, this would result in a segmentation fault. The agent will now log an error and terminate the process by raising a fatal PHP error. By default, this limit is set to a very high value of 500. Exceeding this limit should be extremely rare.
Improve the stability and performance of the agent

The internals of the agent and its background daemon process have been significantly refactored to improve interprocess communication, stability and performance. The maximum number of connections to the background daemon process has been doubled to 4096.

Bug Fixes

Fix for installing on Ubuntu 13.10 when using PHP-FPM

Previously the installer would fail to install a newrelic.ini file in the configuration directory for PHP-FPM (/etc/php5/fpm/conf.d), if one was present. This has been fixed, and the installer will correctly install a newrelic.ini for CLI, DSO and FPM configuration directories.
Fix for drupal_http_request() always returning NULL under PHP 5.5

Version 3.9.5.13 added support for external calls made using drupal_http_request(). Due to the way the agent instruments this function under PHP 5.5, this function would always return NULL instead of the correct return value. This has been fixed.
Fix for real user monitoring when a Content-Length response header is present.

When automatic real user monitoring is enabled, the agent will only perform JavaScript injection into HTML pages when a Content-Length header is not already present in the response. In some cases, this check was not working correctly leading to the value in the Content-Length header not matching the actual number of bytes sent to the client.
Fixed a segmentation fault when Zend Thread Safety is enabled.

Attempts to use the agent under Apache using a threaded MPM (e.g. worker or event) and mod_php would result in segmentation faults. This has been fixed, but New Relic does not recommend using the agent in these circumstances.
Fixed high CPU usage under heavy load

Under very high loads with thousands of PHP processes, the background daemon process could consume 100% CPU when the per-process file descriptor limit was exceeded. This has been fixed. The agent will now throttle the number of new connections accepted when per-process file descriptor limit is reached. A message is also printed to the log file.

PHP agent v4.5.5.38

Thu, 13 Feb 2014 00:00:00 +0000

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

PHP agent v4.6.5.40

Thu, 27 Feb 2014 00:00:00 +0000

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

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.

PHP agent v4.4.5.35

Wed, 08 Jan 2014 00:00:00 +0000

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

This release of the New Relic PHP Agent improves real user monitoring and adds support for custom parameters in transaction analytics events. These changes were made to create a solid foundation for future enhancements. Additionally, an emphasis was placed on reducing the download size of the agent. As a result, the download size has been reduced by 75%.

New Features

Improve Real User Monitoring

The PHP agent's code for both automatic and manual injection of Real User Monitoring scripts has been improved. No application changes are required, but the new injection logic is simpler, faster, more robust, and paves the way for future improvements to Real User Monitoring.
Attach custom parameters to analytics events

Custom parameters given to the agent through the API functions newrelic_add_custom_parameter and newrelic_set_user_attributes can now be automatically attached to transaction and page view analytics events. By default custom parameters will be attached to traces, errors, and transaction analytics events. Optionally, custom parameters can also be included in the JavaScript injected for Real User Monitoring. This allows custom parameters to be attached to page view analytics events.

The behavior of custom parameters can be controlled through the following configuration settings, which are shown with their default values.

newrelic.transaction_tracer.capture_attributes = true newrelic.error_collector.capture_attributes = true newrelic.analytics_events.capture_attributes = true newrelic.browser_monitoring.capture_attributes = false

PHP agent v4.7.5.43

Tue, 01 Apr 2014 00:00:00 +0000

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

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

PHP agent v4.8.0.47

Thu, 24 Apr 2014 00:00:00 +0000

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

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.

PHP agent v5.0.0.115

Mon, 26 Oct 2015 00:00:00 +0000

New Features

Users can now delete applications from the UI after 20 minutes of inactivity. Previously, this required a restart of the New Relic PHP daemon.

Upgrade Notices

We rearchitected the daemon to enable future improvements.
Daemon log levels are now simpler. While verbose and verbosedebug will still work, debug now gives you all the debugging information. Agent log levels remain unchanged.

End of Life Notices

For the few customers who start the daemon manually, the newly renamed command-line flags can be found with the -h or --help flags. The following old flags will be removed in a future release:
- [-p pidfile]
- [-d level]
- [-c config]
- [-l logfile]
- [-P port]
- [-s]
- [-n]
- [-b SSL-certificate-bundle]
- [-S SSL-certificate-path]
- [-H host]
- [-x proxy]
- [-a auditlog]

PHP agent v5.1.0.129

Mon, 09 Nov 2015 00:00:00 +0000

New Features

To easily distinguish dynamically assigned hosts, users can now assign a display name to a host with the setting newrelic.process_host.display_name.
The New Relic PHP Agent now supports the latest Production Release of 64-bit FreeBSD, which is currently at 10.2-RELEASE.

Upgrade Notices

Transactions run under PHP's CLI Web server will now report as Web transactions instead of background transactions. If you want the agent to continue reporting them as background transactions, use the newrelic_background_job() API function to mark the transaction as a background job.

Notes

The agent now collects the following information in web transactions (not yet shown in the New Relic UI): Accept, Host, Content-Length, and Content-Type HTTP request headers, and HTTP request method.

PHP agent v4.9.0.54

Tue, 20 May 2014 00:00:00 +0000

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

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.

PHP agent v5.1.1.130

Tue, 17 Nov 2015 00:00:00 +0000

New Features

With this release, the agent reports TransactionError events. These new events power the beta feature Advanced Analytics for APM Errors (apply here to participate). The error events are also available through New Relic Insights.

PHP agent v5.2.0.141

Tue, 15 Dec 2015 00:00:00 +0000

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.

PHP agent v5.3.0.148

Tue, 19 Jan 2016 00:00:00 +0000

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.

PHP agent v5.4.0.150

Tue, 26 Jan 2016 00:00:00 +0000

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.

PHP agent v6.0.0.155

Mon, 07 Mar 2016 00:00:00 +0000

New Features

Support has been added for PHP 7.0.

PHP agent v5.5.0.154

Thu, 18 Feb 2016 00:00:00 +0000

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.

PHP agent v6.0.1.156

Wed, 09 Mar 2016 00:00:00 +0000

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.

PHP agent v 6.1.0.157

Thu, 17 Mar 2016 00:00:00 +0000

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.

PHP agent v6.2.1.0

Mon, 02 May 2016 00:00:00 +0000

New Features

We're proud to announce initial support for Alpine Linux 3.1 and newer. Currently, manual installation is required.

PHP agent v6.2.0.158

Tue, 12 Apr 2016 00:00:00 +0000

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.

PHP agent v6.3.0.161

Wed, 18 May 2016 00:00:00 +0000

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.

PHP agent v6.4.0.163

Tue, 14 Jun 2016 00:00:00 +0000

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.

PHP agent v6.5.0.166

Thu, 28 Jul 2016 00:00:00 +0000

New Features

Support has been added for Zend Framework 3.

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.

PHP agent v6.6.0.169

Tue, 23 Aug 2016 00:00:00 +0000

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.

PHP agent v6.6.1.172

Thu, 25 Aug 2016 00:00:00 +0000

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.

PHP agent v6.7.0.174

Wed, 21 Sep 2016 00:00:00 +0000

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

To avoid potential deadlocks, MySQL SELECT queries that use the FOR UPDATE or LOCK IN SHARE MODE suffixes will no longer generate explain plans.

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.

PHP agent v6.8.0.177

Wed, 09 Nov 2016 00:00:00 +0000

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.

PHP agent v7.0.0.186

Tue, 21 Feb 2017 00:00:00 +0000

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.

PHP agent v6.9.0.182

Thu, 19 Jan 2017 00:00:00 +0000

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.

PHP agent v7.2.0.191

Wed, 19 Apr 2017 00:00:00 +0000

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.

PHP agent v7.1.0.187

Thu, 23 Mar 2017 00:00:00 +0000

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.

PHP agent v7.3.0.193

Mon, 26 Jun 2017 00:00:00 +0000

Upgrade Notices

Laravel Queue instrumentation has been updated to better interoperate with other New Relic APM features. It is possible that messages sent from PHP installs running version 7.3 (or later) of the PHP agent may not be correctly linked to the message queue worker transaction if the worker is running with version 7.2 or earlier of the PHP agent.

If you use the Laravel Queue instrumentation, we recommend ensuring that all agents used to produce and consume messages are upgraded to version 7.3 simultaneously to avoid unexpected service map issues.

Bug Fixes

Compatibility with extensions that install opcode handlers on PHP 7 has been improved, most notably with uopz. While we still do not recommend using other extensions that hook deeply into PHP (such as uopz, runkit, or xdebug) with the New Relic PHP agent, this change should result in improved functionality.
A potential segfault when using Predis in a session handler invoked at request shutdown has been fixed.
External requests issued using Guzzle 6 are now properly instrumented when the GuzzleHttp\Client class has been extended.

PHP agent v7.3.1.197

Tue, 27 Jun 2017 00:00:00 +0000

Bug Fixes

Users of Guzzle 4 or 5 may have seen crashes in version 7.3.0 of the PHP agent due to a bug in the agent's request shutdown instrumentation for that library. This has been fixed.

PHP agent v7.4.0.198

Wed, 05 Jul 2017 00:00:00 +0000

Bug Fixes

On the first request served by a PHP process, a Drupal 6 or 7 hook that was invoked with module_invoke() before it had been invoked by module_invoke_all() could have its module name reported as an empty string. This has been fixed.
On PHP 7.0 and 7.1, a Drupal 6 or 7 hook invoked via module_invoke_all() could report the module name as an empty string in some situations. This has been fixed.

PHP agent v7.5.0.199

Tue, 29 Aug 2017 00:00:00 +0000

New Features

A new API function for timing datastore functions that the PHP agent doesn't natively instrument has been added: newrelic_record_datastore_segment(). Documentation and usage examples can be found on the New Relic Documentation site.
The agent now collects additional metadata when running within AWS, GCP, Azure, and PCF. This information is used to provide an enhanced experience when the agent is deployed on those platforms.

Bug Fixes

On Laravel 5.4, previous versions of the PHP agent named transactions handled by routes without explicit names based on the request method and front controller name, instead of using the route URI as with other versions of Laravel. This has been fixed, and automatic transaction names are once again consistent across all Laravel versions.
When generating explain plans for queries issued with MySQLi, the PHP agent could bind parameters from the wrong query if the PHP object ID had been reused internally. This has been fixed.

PHP agent v7.6.0.201

Tue, 10 Oct 2017 00:00:00 +0000

New Features

Internal functions can now be instrumented by enabling the newrelic.transaction_tracer.internal_functions_enabled configuration setting. When enabled, internal functions will appear in transaction traces like PHP functions.

Note that enabling this option may result in transactions being slower, especially when collecting many traces from PHP 5.x. Enabling this option is only recommended when specifically debugging performance issues where an internal function is suspected to be slow.

Bug Fixes

In some cases, Magento 2's UI Component JSON data sources return with an (incorrect) Content-Type of text/html. This resulted in auto instrumentation insertions into JSON data that contained a <head> string. We now identify these specific JSON data sources and ensure the auto instrumentation is not inserted into this JSON data.
On PHP 7, using file_get_contents() to get a HTTP URL in a function which also read from $http_response_header resulted in the external call not being linked correctly in the APM UI: the external call would appear in transaction traces without a link to the receiving application. This has been fixed.
Using curl_setopt_array() to set options on a cURL handle could result in cross application tracing failing. This has been fixed.
When generating explain plans for queries issued with MySQLi, the PHP agent could bind parameters from the wrong query if the PHP object ID had been reused internally. This has been fixed.
Due to a change in Laravel 5.5's router API, the PHP agent would crash when automatically naming a Laravel transaction. This has been fixed.
On PHP 7, when naming transactions for the Laravel 5 framework, well-formed transaction names were being replaced by the too-generic $METHOD/index.php. This has been fixed.
Invoking newrelic_record_datastore_segment() before the PHP agent had connected to New Relic would result in the query callback silently failing to execute. This has been fixed; the callback will always be invoked provided parameters of the correct type are given to the function, otherwise an E_WARNING will be generated.

PHP agent v8.0.0.204

Mon, 12 Mar 2018 00:00:00 +0000

Upgrade Notices

The newrelic.daemon.ssl ini setting has been removed to increase security. Transport Layer Security (TLS) will now always be used in communication with the New Relic collector.
Laravel Queue support has now been enabled for all users. If newrelic.feature_flag=laravel_queue is set, it will now be ignored.

Bug Fixes

On FreeBSD and Solaris, when newrelic.daemon.port is configured to use TCP to connect the agent to the daemon, the agent would have difficulty receiving application configuration data from the daemon due to the default timeout of 100 milliseconds matching the delay enforced by the FreeBSD kernel as part of its implementation of Nagle's algorithm. The PHP agent will now set the TCP_NODELAY flag when connecting to the daemon via TCP, which increases the reliability of the agent:daemon connection.

PHP agent v7.7.0.203

Wed, 10 Jan 2018 00:00:00 +0000

New Features

Support for PHP 7.2 has been added.

Bug Fixes

Datastore metrics would not be generated for Predis users who stopped and started the transaction after instantiating a Predis\Client object. This included users using the newrelic_set_appname() API. This has been fixed.

PHP agent v8.1.0.209

Mon, 30 Apr 2018 00:00:00 +0000

Upgrade Notices

The PHP Agent API call newrelic_set_appname has been updated with security improvements in anticipation of future releases.

PHP agent v8.2.0.221

Wed, 05 Sep 2018 00:00:00 +0000

Bug Fixes

Fixed an entire category of bugs where a Drupal hook whose hook name matched its module name resulted in the generation of empty metric names.

Operating Systems Support

This release of the PHP Agent removes support for the Solaris operating system. For Solaris support, please install agent version 8.1 or prior.

PHP agent v8.3.0.226

Mon, 15 Oct 2018 00:00:00 +0000

Bug Fixes

In rare cases, during a reset of the apache web server, the agent and mod_php would hang with 100% CPU utilization. This has been fixed.

PHP agent v8.4.0.231

Wed, 05 Dec 2018 00:00:00 +0000

New Features

Support for Distributed tracing

Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before.

Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.

To enable distributed tracing, two parameters should be changed in the newrelic.ini file:
```
newrelic.distributed_tracing_enabled = true
```
and
```
newrelic.transaction_tracer.threshold = 0
```
Read more about about distributed tracing in the PHP Agent.

Bug Fixes

A bug in the PHP agent resulted in databaseCallCount attributes no longer being attached to Transaction events. The 8.4 release restores these attributes.
Predis 2 cluster connections could not be instrumented due to internal changes in Predis. The 8.4 release fixes this.

PHP agent v8.5.0.235

Wed, 19 Dec 2018 00:00:00 +0000

New Features

Added support for PHP 7.3.
Keeping up with the latest and greatest from the PHP Core team, the New Relic PHP Agent now supports PHP 7.3.
Distributed Tracing Improvements!
The PHP Agent's Distributed Tracing support (introduced in version 8.4 of the PHP Agent) now includes the `http.method` attributes for External spans.
Up to date PHPUnit support.
The PHP Agent now supports automatic creation of custom events for PHPUnit 6, PHPUnit 7, and PHPUnit 8.

PHP agent v8.6.0.238

Thu, 14 Mar 2019 00:00:00 +0000

New Features

Support Laravel's handling of CORS HTTP OPTIONS.
Requests for Laravel's built-in automatic handling of CORS HTTP OPTIONS requests will now be given the transaction name _CORS_OPTIONS.

Bug Fixes

A potential segfault when using PHP 7.3, opcache and multiple PHP workers has been fixed.
Uncaught exceptions within a job being executed by a Laravel Queue worker are now reported correctly.
Invoking function_exists() on a function disabled with the disable_functions configuration directive will now correctly return false.

PHP agent v8.7.0.242

Thu, 14 Mar 2019 00:00:00 +0000

Bug Fixes

Transaction globals are now cleanly separated from request globals. This fixes crashes related to the initialization of multiple transactions during one request (mostly triggered by newrelic_set_appname()).

PHP agent v9.0.2.242

Thu, 08 Aug 2019 00:00:00 +0000

New features in 9.0

Detailed transaction traces now available when distributed tracing is enabled.

This release includes a refactor of segment storage to allow the agent to sort and apply different prioritization of segments that are used for transaction traces instead of distributed tracing. The PHP agent 8.4 release included limited support for distributed tracing, which resulted in the loss of detailed transaction traces for individual PHP services when distributed tracing was enabled.

The refactor in this new release allows the agent to send up the segments (spans) you want to view for a distributed trace that includes PHP services. It also separately provides as much segment detail as possible when exploring transaction traces for an individual PHP service.

Notes:

The instructions to enable distributed tracing have not changed with this release.
The behavior of newrelic.transaction_tracer.detail has changed when distributed tracing is on. In the 8.4 - 8.7 PHP agent releases, newrelic.transaction_tracer.detail was disabled when distributed tracing was enabled. That is no longer the case. For more information, see the documentation for configuring trace level detail when using distributed tracing.
To enable the improved support for distributed tracing, the PHP agent's memory allocation strategy has changed in 9.0. The PHP agent will more aggressively allocate memory when a transaction starts, and the system allocator may choose not to release that memory back to the operating system immediately, depending on the configuration of the operating system kernel and C library. As a result, the memory usage of the PHP processes may now be higher than it was with previous versions of the PHP agent.

Upgrade notices for 9.0

With these distributed tracing enhancements, please check threshold values.

In the 8.4 - 8.7 PHP agent releases, we recommended that customers set newrelic.transaction_tracer.threshold = 0 so that the agent would report complete distributed traces even when a lightweight PHP service was part of the trace. This is no longer necessary.
When upgrading to the 9.0 release, we recommend that you review your newrelic.transaction_tracer.threshold settings, and return this value to its default or some higher value that is sensible for the application.

The daemon will now issue a warning if it cannot find a root certificate bundle on startup.

The daemon includes its own certificates and will still operate, but a future version of the PHP agent will remove the built-in certificates. At that point the PHP agent will not be able to communicate with New Relic's servers.
Recommendation: Ensure a root certificate bundle is installed on your host or in your container before using the PHP agent. This is generally available on most Linux distributions as a ca-certificates package. On FreeBSD, a bundle is available via the security/ca_root_nss package in ports.

The daemon may no longer be invoked with the --tls flag.

As of PHP agent version 8.0.0 the newrelic.daemon.ssl ini setting had been removed to increase security, but you could still invoke the daemon from the command line with --tls true. Command-line invocations of the daemon with the --tls flag will cause the invocation to fail.
As with all PHP agent versions since 8.0.0, TLS is always used for communication with New Relic servers.

Bug fixes

A potential segfault when using drupal_http_request under PHP 7.3 has been fixed.
In some cases, starting a new transaction during a request (via newrelic_start_transaction or newrelic_set_appname) could result in an incomplete state of framework and user function instrumentation.
When obfuscating SQL, comments are stripped without any loss of the SQL itself.
Predis 0.8 commands that used the synchronous executeCommand() code path (for example, HSET) on a clustered connection did not generate metrics. This has been fixed.

Known issues and workarounds

Potential memory exhaustion for long running transactions

PHP agent 9.x uses more memory than previous versions, as it is less aggressive about freeing the memory used to track function calls and segments during transactions: in the normal case, memory is only freed at the end of each transaction.

This tends to manifest mainly for users with long running transactions, such as background jobs to process message queues, transform or report on data, or send e-mails.

We apologize for the inconvenience this issue has caused, and are actively working to fix it. In the short term, we have four potential workarounds to mitigate this issue.

Workarounds:

1. Start/stop transactions manually. If the affected transaction is one that performs a series of repetitive processes, such as a message queue consumer, you can manually instrument each iteration as a separate transaction. This provides you more fine-grained data on how the process is operating. By doing this, the memory used will be freed after each transaction. To implement this, you would ignore the initial automatic transaction with newrelic_end_transaction(true), then use newrelic_start_transaction()and newrelic_end_transaction() to instrument each transaction in turn.
2. Reduce transaction trace detail. If you will need PHP 7.4 immediately, or any of the functionality added in the PHP agent 9.x releases, and can get by with traces only including information on datastore and external calls, then you can reduce the level of detail the PHP agent captures by changing this configuration setting: newrelic.transaction_tracer.detail = 0. With this setting, traces will no longer contain PHP function calls. NOTE: Transactions that make hundreds of thousands of datastore or external calls may still be affected by memory issues.
3. Downgrade to PHP agent 8.7. If you don’t intend to use PHP 7.4 immediately, this is likely the simplest and fastest solution. To downgrade, you can either install from the tarballs at https://download.newrelic.com/php_agent/archive/8.7.0.242/, or downgrade to version 8.7.0.242 in your package manager and pin that version. Note that if distributed tracing is enabled on PHP agent 8.7, transaction tracer detail is automatically reduced (as per the next option).
4. Cap the # of function segments that are created (stay on PHP agent 9.x). This is similar to the “reduce transaction trace detail” option, but also allows for a limited number of PHP function calls to be traced, at the cost of an increase in memory usage commensurate with the number of functions that are captured. (As a rough rule of thumb, each segment requires about 320-400 bytes of the heap.) To capture the first 5,000 function calls, you would add this configuration setting: newrelic.transaction_tracer.max_segments = 5000. With this setting, any PHP functions after the number of function calls that are configured will be ignored. NOTE: Transactions that make hundreds of thousands of datastore or external calls may still be affected by memory issues.

**NOTE: A more detailed explanation of these options can be found in our Explorer’s Hub post.

PHP agent v9.0.2.245

Mon, 19 Aug 2019 00:00:00 +0000

Notes

A bug that could result in segfaults when transactions were restarted (either directly through newrelic_start_transaction() or indirectly through newrelic_set_appname()) was fixed.

This also affected customers using Laravel Queue instrumentation, as this uses transaction restarts internally.
PHPUnit may not have been detected on case sensitive filesystems on 9.0.0. This has been fixed.
A bug that could result in segfaults for CodeIgniter applications on PHP 7 when call_user_func_array() inlining failed was fixed.

Known issues and workarounds

Potential memory exhaustion for long running transactions. See description under Known issues and workarounds in the PHP 9.0.0.242 release notes.

PHP agent v9.10.0.262

Wed, 29 Apr 2020 00:00:00 +0000

Bug Fixes

In some rare cases where requests to cloud provider metadata endpoints are blocked via certain methods, the PHP Daemon logged panics from the underlying Go HTTP library. This scenario is now accounted for and handled gracefully.

Upgrade notices

On Linux systems, the default value for newrelic.daemon.address changed from /tmp/.newrelic.sock to @newrelic. This means that by default on Linux, agent and daemon communicate via abstract sockets instead of socket files.
The PHP Agent installer for Ubuntu/Debian systems now requires Python 3. Debian based distributions with Python 2 are no longer supported.

End of life notices

The distributing tracing API functions newrelic_create_distributed_trace_payload() newrelic_accept_distributed_trace_payload(), and newrelic_accept_distributed_trace_payload_httpsafe() used to manually instrument applications have been deprecated, and will be removed in a future release.

Instead, use the API functions compatible with W3C Trace Context support, added in agent version 9.8: newrelic_insert_distributed_trace_headers(), and newrelic_accept_distributed_trace_headers()

PHP agent v9.10.1.263

Tue, 05 May 2020 00:00:00 +0000

Bug Fixes

In some cases, instrumenting Laravel queue applications while having distributed tracing turned on could potentially lead to a segfault. This has been fixed.

PHP agent v9.1.0.246

Wed, 04 Sep 2019 00:00:00 +0000

New Features in 9.1

Symfony 4 support added.

Web transactions that use the Symfony 4 framework will now be automatically named based on the route or controller name.

Addition of the ability to migrate to Configurable Security Policies (CSP) on a per agent basis for accounts already using High-security mode (HSM).

When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured.

Upgrade notices

Requests handled by PHP-FPM that result in a 404 error because the script does not exist, or a 403 error because PHP-FPM does not have permission to access the script, will now result in a transaction called 404 or 403, respectively, rather than being named after the request URI. This change was made to prevent metric grouping issues, particularly when sites are being probed by potential attackers.

If you wish to capture the actual request URI for analysis, it can be attached to the transaction event under the request.uri attribute using the following configuration setting: newrelic.transaction_events.attributes.include=request.uri

Bug fixes

In version 9.0, Guzzle and Predis execution time could be double counted on application overview and transaction charts in APM, as time could be attributed to both PHP execution and the external or datastore time, respectively. This has been fixed, and charts should now revert back to their previous behavior.
Restarting a transaction from within a Drupal or WordPress hook could result in a segfault. This has been fixed.

Known issues and workarounds

Potential memory exhaustion for long running transactions. See description under Known issues and workarounds in the PHP 9.0.0.242 release notes.

PHP agent v9.11.0.267

Tue, 16 Jun 2020 00:00:00 +0000

New Features

Added support for New Relic Infinite Tracing. Note: the PHP agent does not yet support attributes on spans. This will be available in the next minor release.
Added the following Infinite Tracing configuration options:
Support for auto-instrumenting Symfony 5 applications has been added.
Support for auto-instrumenting Drupal 9 applications has been added.

Bug Fixes

In some cases the newrelic-daemon got caught in an infinite loop on startup when the socket it tried to connect to was already acquired by another process. This behavior has been accounted for and fixed.

PHP agent v9.12.0.268

Tue, 21 Jul 2020 00:00:00 +0000

New Features

With the addition of attributes on spans, the PHP agent now fully supports Infinite Tracing on New Relic Edge.

Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. You configure your agent to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network.

Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative.
Added support for attributes on spans. All custom attributes and some agent attributes previously applied as “Transaction events” are now also applied to the currently executing span, subject to the new span configuration settings.
- Added the transaction.name to spans.
- Added http.statusCode to external spans, representing the status code on an http response.
- Added error attributes to each span that exits with an error or exception. error.class and error.message are now included on the span in which an error or exception was noticed, and, in the case of unhandled exceptions, on any ancestor spans that also exit with an error. Also, the public API method newrelic_notice_error now attaches these error attributes to the currently executing span, while still creating a Transaction Error event.
  
  Spans with error details are now highlighted red in the distributed tracing UI, and error details will expose the associated error.class and error.message. It is also now possible to see when an exception leaves the boundary of the span, and if it is caught in an ancestor span without reaching the entry span. NOTE: This “bubbling up” of exceptions will impact the error count when compared to prior behavior for the same trace. It is possible now to have a trace that has span errors without showing an error on the root span or entry spans.
- Added a new API method newrelic_add_custom_span_parameter that allows adding custom attributes to spans. This is independent of the transaction; using this new API to add custom attributes to spans does not add them to transactions. If the maximum number of custom attributes is reached, span-level custom attributes take precedence over transaction-level custom attributes.
- Added the following span event attributes configuration to enable attribute filtering for spans:
  Note: Security recommendation—Review your Transaction attributes configuration. Any attribute include or exclude settings specific to Transaction events, should be applied to your Span attributes configuration or your global attributes configuration.

Bug Fixes

In cases where the agent is configured to connect to the hostname of a daemon that exists in a separate container/host, after successfully connecting, the agent would not attempt to resolve the IP address again. This was seen when the daemon container/host goes down and then comes up again with a new IP address. Now, the agent will wait 45 seconds since either the last known good connection or the last IP address resolution and will attempt to resolve an IP address again.

PHP agent v9.13.0.270

Mon, 17 Aug 2020 00:00:00 +0000

New Features

Support has been added for Slim Framework 4.x.
Support has been added for Laravel 7.x.

Bug Fixes

Users of newrelic_record_datastore_segment may have experienced situations where the total transaction time was higher than the response time. This was fixed and users will see behavior consistent with automatically created datastore segments.
Previously, WordPress plugins referred to by their path names were not accounted for in caching. This behavior has been fixed, and users to which this applies to should see improvements in overhead.

PHP agent v9.14.0.290

Thu, 29 Oct 2020 00:00:00 +0000

New Features

The PHP agent is now open source!

The agent source code is available and open to contributions. You can now report issues and make feature requests for the agent directly on GitHub. See our README for more information.

Bug Fixes

Under some circumstances, the agent reported a total time higher than the response time when using Zend_Http_Client. This has been fixed.
The agent leaked a small amount of memory for each fulfilled Guzzle promise. This has been fixed.
Calls to newrelic_insert_distributed_trace_headers could cause crashes on PHP 7.0, 7.1, and 7.2. This has been fixed.
In rare cases, using Guzzle with WordPress and PHP 7.4 caused crashes. This has been fixed.

PHP agent v9.15.0.293

Mon, 07 Dec 2020 00:00:00 +0000

End of Life Notices

Support for PHP 5.3 and PHP 5.4 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 - 7.3 or higher as of the date of this release. If you would like to continue running the New Relic PHP agent with PHP 5.3 and 5.4, we recommend using version 9.15 of the agent for maximum compatibility. However please note that we can only offer limited support in this case.
This release marks the last officially supported New Relic PHP Agent for CentOS 5.
MacOS builds of the New Relic PHP Agent will no longer be provided, and we will no longer ensure compatibility on MacOS platforms.
For more information about these EOL notices, see our Explorers Hub post.

New features

Support has been added for Laminas 3.x.
Support has been added for Laravel Lumen 6.x, 7.x, and 8.x
Experimental support has been added for excluding subpaths from Wordpress instrumentation. This lowers the overall Wordpress instrumentation overhead since it reduces the number of files being instrumented, but at the cost of losing visibility into the code in the excluded subpaths. This can be enabled using the ini file setting newrelic.framework.wordpress.hooks_skip_filename.

Bug fixes

Corrected string representation of arginfo parameter names. Thank you @TysonAndre for this contribution.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.4.0.

PHP agent v9.17.0.300

Wed, 21 Apr 2021 00:00:00 +0000

End of life notices

This will be the last release in which ZTS builds are supported. In the future, ZTS builds may not be provided, and support may be completely pulled from the codebase.
New Relic no longer supports PHP 5.3 or PHP 5.4. New Relic highly encourages upgrading to a supported version of PHP. If you would like to continue running the New Relic PHP agent with PHP 5.3 or 5.4, we recommend using version 9.16 of the agent. However, please note that we can only offer limited support in this case.
Ubuntu LTS versions earlier than 14.04, Ubuntu non-LTS versions earlier than 19.04, and Debian versions earlier than 7 "wheezy" are no longer supported.
The following frameworks or framework versions are no longer supported and may be removed from future agent builds:
- Cake PHP 1.x
- Joomla 1.5, 1.6, and 2.x
- Kohana
- Silex 1.x and 2.x
- Symfony 1.x and 2.x

New features

The agent now supports 64-bit PHP 8.0! Compatibility note: When PHP 8.0 detects the New Relic agent, it disables JIT.
mysqli_commit is now instrumented.

Bug fixes

Fixed a memory leak that occurred when short lived segments throw exceptions.
Fixed a build up of duplicate distributed tracing headers that sometimes occurred when using file_get_contents.
Fixed an issue where Laravel Lumen transactions were not being properly named.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0.

PHP agent v9.16.0.295

Mon, 25 Jan 2021 00:00:00 +0000

Bug fixes

The Drupal instrumentation now guards against rare conditions that led to PHP processes exiting with an allocation error. Additionally, the allocation routines now log stack traces when they fail.
When initially building the agent, a parallel build is no longer required to avoid an error about a missing header file (v1.pb-c.h).
SOAP transactions when using Magento 2.3.2+ are now properly named instead of being attributed to Magento's internal SOAP interceptor. Thanks @steven-hoffman-jomashop for the issue report and fix suggestion!

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.5.0.

PHP agent v9.17.1.301

Wed, 28 Apr 2021 00:00:00 +0000

New Relic PHP Agent v9.17.1

Bug Fixes

Fixed instances where the agent's mysqli_commit instrumentation returned a NULL instead of a boolean.
Fixed an issue where parameters were not passed by reference in the agent's pdo instrumentation. This caused a warning in PHP 8.
Fixed instances where an Unknown PHP version: 8.0 error was occurring when installing on Debian and Ubuntu systems.

Support Statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0.

PHP agent v9.19.0.309

Wed, 02 Mar 2022 00:00:00 +0000

New Relic PHP Agent v9.19.0

New Features

Added support for 64-bit PHP 8.1! (#177). Compatibility note: Support for PHP 8.1 does not include Fibers.

Bug Fixes

Fixed Symfony 5 auto detect (#113, #256). Thank you @piotrantosik for your contribution!
Fixed URL of New Relic for PHP docs website used in error messages (#334)
Fixed URL of New Relic of PHP docs website in README (#254). Thank you @revilon1991 for your contribution!

End of Life Notices

32-bit support for PHP versions 5.5, 5.6, 7.0, 7.1, 7.2, 7.3, 7.4 is deprecated and will be removed by June 2022.
Support for FreeBSD operating system is deprecated and will be removed by June 2022.
This will be the last release in which ZTS builds are supported. In the future, ZTS builds may not be provided and support may be completely pulled from the codebase.

Support Statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0.

PHP agent v9.18.1.303

Mon, 23 Aug 2021 00:00:00 +0000

New Relic PHP agent v9.18.1

New features

Added a Docker development environment. It's now possible for contributors to both develop and test (unit tests and integration tests) without setting up a specific environment on their own system. Please see our documentation for more information.
Route caching in Laravel 7.x is now supported!. Transaction naming now works with routes cached via php artisan route:cache. @stockalexander, thanks for your contribution!
Redis::mget and Redis::mset functions are now supported. @b-viguier, thanks for your contribution!

Bug fixes

Fixed instances where a memory leak was occurring with our curl multi instrumentation.
Fixed an issue where a supportability metric used to track an edge case was causing a segfault.
Fixed an issue where PHP versions with an unknown API version were incorrectly handled during Debian package install.
Fixed instances where parent.transportDuration values are 0 for transactions between two PHP applications instrumented through distributed tracing. @b-viguier, thanks for your contribution!
Fixed an issue where the newrelic.ini configuration file was incorrectly installed. @b-viguier, thanks for your contribution!

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0.

PHP agent v9.20.0.310

Mon, 14 Mar 2022 00:00:00 +0000

New Relic PHP agent v9.20.0

New features

AWS instance metadata service (IMDS) feature now allows AWS IMDSv2 by @robertprast.

New Contributors

@robertprast made their first contribution. Thanks!!

End of Life Notices

Support for the Centos 6 / RHEL6 operating systems are deprecated and will be removed by June 2022.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document.

PHP agent v9.2.0.247

Mon, 07 Oct 2019 00:00:00 +0000

New features in 9.2

More flexibility for container deployments

The PHP daemon and agent no longer have to reside on the same host and can now communicate over a IPv4 or IPv6 TCP socket. This can be configured via the newrelic.daemon.address setting in the agent and the --address command line option for the daemon.
When terminating the New Relic PHP daemon via the SIGTERM signal (and/or the SIGINT signal if started with the -f, --foreground flag), the daemon will now send all buffered data to New Relic prior to exiting.
The PHP daemon has introduced a new configuration --watchdog-foreground. This keeps the daemon watchdog process in the foreground, whereas the --foreground configuration keeps the daemon worker process in the foreground. The new configuration makes it possible to use the daemon in a blocking way, without losing the additional stability provided by the watchdog process.

Upgrade notices

The PHP agent has introduced a new configuration newrelic.daemon.address which serves as an alias to newrelic.daemon.port. You may use either to specify the location of the New Relic PHP daemon. If both values are set, newrelic.daemon.address takes precedence.

Similarly, the PHP daemon has introduced a new configuration --address which serves as an alias to --port. Customers may use either to specify the location of the New Relic PHP daemon. If both values are set, --address takes precedence.
When starting the daemon as an external process, the daemon will now wait for up to three seconds for the listening port to be ready to receive connections before forking into the background. This usually occurs in (much) less than a second, and most users with this configuration will notice no difference in practice.

The time that the daemon will wait can be controlled by setting the --wait-for-port setting with a duration. This duration may be 0 to prevent any blocking. If the option is omitted, the default value is 3s.

Note that this is not the default configuration shipped with the PHP agent, and generally is only used in conjunction with the PHP agent configured with newrelic.daemon.dont_launch set to 3.

Daemons started in foreground mode (with the --foreground flag) are unaffected, and will behave as before.

Bug fixes

When duplicating database connections to generate explain plans, the agent will no longer make those connections persistent, even if the original connection was persistent.
The daemon now synchronously handles critical code paths related to harvesting and merging transaction data. This prevents crashes caused by race conditions.
Previously, the PHP agent was silently ignoring the setting newrelic.daemon.port if the value was outside of the range 1 - 65535. In this case, it used the default value of /tmp/.newrelic.sock. The PHP agent no longer silently ignores these port values; it now logs these errors in php_agent.log.

Known issues and workarounds

Potential memory exhaustion for long running transactions. See description under Known issues and workarounds in the PHP 9.0.0.242 release notes.

PHP agent v9.21.0.311

Tue, 26 Apr 2022 00:00:00 +0000

New Relic PHP agent v9.21.0

New features

Distributed Tracing is now turned on by default.
Distributed Tracing span reservoir size now has a default of 2000 (up from 1000) and a maximum of 10000.
Cross Application Tracing is deprecated.

Bug fixes

Fixed an install script bug where it detects Alpine Linux as Debian when phpize dependencies are installed.
Improved stability of using Laravel framework when using opcache with PHP 8.1.

Support statement

New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document.

PHP agent v9.3.0.248

Mon, 11 Nov 2019 00:00:00 +0000

Known issues and workarounds

Potential memory exhaustion for long running transactions

See description and recommendations under Known issues and workarounds in the PHP 9.0.0.242 release notes.

New features in 9.3

Trace and entity metadata API calls

A new API function newrelic_is_sampled() has been added. This call returns true if the current transaction is part of a sampled distributed trace.
A new API function for obtaining linking metadata been added. newrelic_get_linking_metadata(). This call returns an opaque map of key/value pairs that can be used to correlate this application to other data in the New Relic backend.
A new API function newrelic_get_trace_metadata() has been added. This call returns a collection of metadata used to identify a trace: trace.id, which provides the currently executing trace's identifier; and span.id, which provides the span identifier associated with the currently executing span.

Configurable connection timeout

The PHP agent has introduced a new configuration newrelic.daemon.app_connect_timeout. Customers may use this to specify a timeout for the agent to wait for a daemon connection.

With this timeout set, the agent will not immediately drop a transaction when the daemon hasn't connected to the backend yet, but rather grant the daemon time to establish the connection.

It is recommended to only set this timeout when instrumenting long-lived background tasks, as in case of connection problems the agent will block for the given timeout at every transaction start.

PHP agent v9.4.0.249

Thu, 05 Dec 2019 00:00:00 +0000

Known issues and workarounds

Potential memory exhaustion for long running transactions

See description and recommendations under Known issues and workarounds in the PHP 9.0.0.242 release notes.

New features in 9.4

Added support for PHP 7.4

The PHP agent can detect libraries and frameworks that were preloaded via the opcache.preload setting.
- You can disable this feature by using the following configuration setting: newrelic.preload_framework_library_detection = false.

Request URI attribute is now captured

We now capture the request.uri attribute. The request URI appears in transaction queries in New Relic Insights.
- You can disable this attribute by using the following configuration setting: newrelic.attributes.exclude = "request.uri".

Upgrade Notices

For cross agent conformance, the agent attributes request.headers.User-Agent and httpResponseCode are renamed to request.headers.userAgent and response.statusCode. The value response.StatusCode is changed to an integer.
- Attributes are reported with both the new and the legacy attribute names.
- Support for legacy attribute names will be removed in future agent versions.

Bug Fixes

Since 9.0, transaction traces and span events were not created when newrelic_end_transaction was called inside a PHP function. newrelic_end_transaction now creates transaction traces and span events in any case. It reports all traces and span events for segments that weren't ended at the time of its invocation as unknown.
Since 9.0, Predis calls weren't instrumented when the Predis client was loaded from a path ending in Predis/Client.php. This has been fixed.
For inbound distributed tracing payloads with invalid or missing values for pr (priority) and/or sa (sampled) the agent used to assign a default priority of -1 and/or a default sampled value of false to the transaction.
- This has been fixed, the agent now keeps initial priority and sampled values if the respective values in the inbound distributed tracing payload are missing or invalid.
The daemon used to erroneously send SIGUSR1 signals to its parent process group in case one of the flags --foreground or --watchdog-foreground was given. This has been fixed.

PHP agent v9.4.1.250

Wed, 11 Dec 2019 00:00:00 +0000

Bug fixes

A potential segfault when using PHP 7.4 in connection with framework instrumentation has been fixed.

Known issues and workarounds

Potential memory exhaustion for long running transactions

See description and recommendations under Known issues and workarounds in the PHP 9.0.0.242 release notes.

PHP agent v9.5.0.252

Mon, 06 Jan 2020 00:00:00 +0000

New Features

Support for Real Time Streaming
- Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation.
- Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute.
Laravel 6 is now fully supported by the PHP agent.

Known issues and workarounds

Potential memory exhaustion for long running transactions

See description and recommendations under Known issues and workarounds in the PHP 9.0.0.242 release notes.

PHP agent v9.6.0.255

Thu, 16 Jan 2020 00:00:00 +0000

New Features

Enhanced visibility into curl_multi_exec calls

Previously, curl_multi_exec requests appeared as one segment with one total time. Now, we expose the individual segments of a curl_multi_exec request that include individual times and host details. This provides greater visibility as to which URLs are being called and improved ability to troubleshoot slow curl calls.

Configurable daemon start timeout

The PHP Agent has introduced a new configuration newrelic.daemon.start_timeout. Customers may use this to specify a timeout for the agent to wait for the daemon after a daemon was launched by the agent.

With this timeout set, the agent will not immediately drop a transaction when the launched daemon hasn't acquired a socket yet, but rather grants the daemon time to do so.

It is recommended to only set this timeout when instrumenting long-lived background tasks, as in case of daemon start problems the agent will block for the given timeout at every transaction start.

Upgrade Notice

For cross agent conformance, the agent attribute httpResponseCode has been renamed to http.statusCode. In PHP agent release 9.4, we erroneously introduced httpResponseCode as the replacement for response.statusCode.

The new http.statusCode agent attribute name will align with other agents and enables standardized alerts and INSIGHTS queries based on a common attribute name.

Attributes are reported with both the new http.statusCode name and the
legacy httpResponseCode and response.statusCode attribute names.

Support for legacy attribute names will be removed in future agent versions.

Known issues and workarounds

Potential memory exhaustion for long running transactions

See description and recommendations under Known issues and workarounds in the PHP 9.0.0.242 release notes.

PHP agent v9.7.0.258

Tue, 11 Feb 2020 00:00:00 +0000

New Features

Avoid potential memory exhaustion for long running transactions

The configuration settings newrelic.transaction_tracer.max_segments_cli and newrelic.transaction_tracer.max_segments_web were added. These settings can be used to limit the number of segments the PHP agent records during a CLI transaction and a web transaction respectively.

newrelic.transaction_tracer.max_segments_cli defaults to 100000 and thus avoids potential memory exhaustion for long running CLI transactions.

newrelic.transaction_tracer.max_segments_web defaults to 0, meaning that the PHP Agent shall capture all segments during a web transaction.

For more information, see the documentation about the PHP agent configuration.

Performance improvements

The PHP agent now creates segments in a more efficient way, which results in improved performance.

Bug fixes

The Debian init script now uses pidof instead of ps. This solves issues related to starting the daemon with systemctl on Debian. Previously, the daemon would start and immediately stop.

PHP agent v9.9.0.260

Wed, 01 Apr 2020 00:00:00 +0000

Bug fixes

Under some circumstances, Drupal 8 transactions were named after generic controllers. These names were not useful for troubleshooting.

Drupal 8 transaction naming is now improved and hooks into Symfony routing to resolve the main controller associated with a route.

PHP agent v9.8.0.259

Wed, 25 Mar 2020 00:00:00 +0000

New Features

Support for W3C Trace Context, with easy upgrade from New Relic trace context

Distributed Tracing now supports W3C Trace Context headers for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format.
When distributed tracing is enabled, there are two new API function calls available that now support W3C tracestate and traceparent distributed tracing headers in addition to the New Relic distributed tracing header information:
- newrelic_insert_distributed_trace_headers() is used to add distributed tracing headers
- newrelic_accept_distributed_trace_headers() is used to accept distributed tracing headers
When distributed tracing is enabled, you can use the new configuration setting newrelic.distributed_tracing_exclude_newrelic_header to exclude the New Relic distributing tracing header and only rely on W3C Trace Context headers.

Bug fixes

Fixed a case where the memory usage of the PHP agent increases when newrelic.transaction_tracer.max_segments_cli limit is reached.
In rare cases, optimized segment data structures could cause crashes for long-running transactions that hit the segment limit set via newrelic.transaction_tracer.max_segments_cli or newrelic.transaction_tracer.max_segments_web. This has been fixed.

Known Issues and Workarounds

If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream PHP New Relic agents to this agent release.

PHP agent v3.0.5.95

Tue, 23 Oct 2012 00:00:00 +0000

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

This release marks the start of a brand new series of PHP agent releases. This represents many months of performance tuning, stability improvements and additional new features. All existing users are highly encouraged to upgrade to the latest agent. There are many changes in this version, the most interesting of which are listed below. All users who are upgrading from a previous release are encouraged to read the upgrade notes document to fully understand some of the impacts of upgrading.

Highlights of this release include:

Drastic memory usage reduction. The agent overhead is down from approximately 35% to just 4%.
Significantly less stack space used (down from 40K per PHP function call to just 84 bytes). This affects users with deeply recursive functions.
License keys are now set in the INI file and not the daemon configuration file, and they are settable on a per-directory or per-virtual host basis. This very frequently requested feature will allow multi-tenant sites to use different keys for each tenant.
The New Relic daemon can now be started automatically by the agent. For upgrade customers it will still be started the way it always was with the init scripts, but you can now change that by configuring the daemon in your INI file. Please see this page on daemon startup modes for details.
Several bugs related to auto-RUM (Real User Monitoring) have been fixed, including a fix for non-standard HTML (where the head element is at the end of the document).
The agent startup "banner" now contains much more useful information that can be included in the initial dialog with support, and will short-circuit the typical "what OS and PHP version are you using exactly?" preamble to getting a ticket resolved.
The agent and daemon no longer use a UNIX-domain socket for their communications. Now a standard TCP socket (port 33142 by default) is used, which makes deploying in a chroot environment a lot easier.
The RPM and Debian packages have been split into three separate packages: the agent, the daemon and common scripts between the two. This was primarily done so that the agent was in its own package, and on 64-bit systems the agent package now only contains the 64-bit agent. This means that 64-bit users do not have to install the entire 32-bit runtime just to install the PHP agent. The 32-bit agent can always be installed alongside the 64-bit one.
The phpinfo() output has been changed to more clearly distinguish between global and per-directory settings. It now also correctly displays the per-directory value if the script was invoked from within a directory that changed default values.
The newrelic.transaction_tracer.top100 setting has been renamed to newrelic.transaction_tracer.detail.
You can now arbitrarily begin and end transactions (for example, at the beginning and end of each job queue unit of work). This is done using the new newrelic_end_transaction and newrelic_start_transaction API calls.
The daemon has been considerably simplified and uses fewer locks, thus reducing the potential for entering a "spin" state.
Many other improvements to speed and stability.

PHP agent v9.6.1.256

Wed, 22 Jan 2020 00:00:00 +0000

Bug Fixes

In 9.6.0, custom outbound headers added to curl requests could be silently removed if both newrelic.cross_application_tracer.enabled and newrelic.distributed_tracing_enabled are disabled. This has been fixed.