Supported PHP versions

The different PHP versions have support timelines defined by PHP. Please refer to Supported PHP versions at to see which versions are currently supported by PHP and when each version is planned for end of support.

  • Deprecated versions don't receive updates or security patches, so running them in production should be avoided.
  • Dynatrace is committed to supporting each PHP version for at least as long as the vendor supports it (in most cases, support extends for at least six months beyond this point).

Support matrix

PHP version Vendor released Vendor End of life Supported by Dynatrace until First supported Dynatrace OneAgent version Last supported Dynatrace OneAgent version
8.0 (Zend Engine 4.0) 2020/11/26 2023/11/26 1.207
7.4 (Zend Engine 3.4) 2019/11/28 2022/11/28 1.179
7.3 (Zend Engine 3.3) 2018/12/06 2021/12/06 1.169
7.2 (Zend Engine 3.2) 2017/11/30 2020/11/30
7.1 (Zend Engine 3.1) 2016/12/01 2019/12/01
7.0 2015/12/03 2018/12/03 2020/04/30 1.189
5.6 2014/08/28 2018/12/31 2019/11/30 1.181
5.5 2013/06/20 2016/07/21 2018/11/30 1.135
5.4 2012/03/01 2015/09/03 2018/11/30 1.135
5.3 2009/06/30 2016/07/21 2018/11/30 1.135

For details on PHP 8.0, see below.

Support for PHP 8.0

Early Adopter


  • OneAgent 1.207+
  • PHP NG monitoring must be enabled


To enable PHP 8.0 monitoring in Dynatrace

  1. In the Dynatrace menu, go to Settings > Monitoring > Monitored technologies
  2. Open PHP for editing (select the pencil icon).
  3. Turn on Enable PHP 8.0 RC monitoring on every host.

Messaging for unsupported versions

When OneAgent detects an unsupported PHP version, we exclude it from monitoring and display a warning in the process overview page:

Activation of deep monitoring was unsuccessful
  Process version is not supported

PHP Monitoring Process version not supported

We also write the message to the error logs on the host machine.

See the environments and versions that Dynatrace supports in conjunction with PHP and the PHP supported versions.

Known limitations

  • CLI monitoring is turned off by default, because, during a short-lived CLI execution, injection overhead may make up a large percentage of the whole runtime. You should refrain from using CLI monitoring when threading and forking is used for the monitored application, as these features aren't supported.
  • At this point, there is no differentiation between CGI and Fast-CGI; these are reported as a single type: CGI.