EF1 JMX and PMI extensions end of support
- Latest Dynatrace
- Upgrade guide
- 5-min read
- Published Aug 05, 2026
- Will deprecate
The Dynatrace Extension Framework 1.0 (EF1) JMX and PMI extensions reach their official end-of-support in July 2027 for SaaS Environments.
Use this guide to identify whether your environment is affected and whether you need to migrate these extensions to the Extension Framework 2.0 (EF2) architecture.
In 2023, Dynatrace announced that Extension 2.0 now supports JMX data sources, making migration from Extensions 1.0 possible for JMX and PMI monitoring use cases. Extension Framework 2.0 brings built-in security, configuration flexibility, versioning, packaged assets and many more features for improved user experience. This page formalizes the end-of-support deadline and gives you the steps to complete your migration.
Why upgrade?
As of July 1, 2027, all Extension Framework 1.0 JMX and PMI extensions will be out of support for SaaS Environments.
What will you do?
To keep your JMX and PMI monitoring running after July 1, 2027:
- Check if you're affected by identifying any EF1 JMX and PMI extensions that are enabled or bound to process groups in your environment.
- Migrate official extensions by replacing each EF1 extension with its EF2 equivalent, using the mapping table in this guide.
- Convert custom extensions to the EF2 format with the Convert a JMX extension procedure.
Before you begin
Identify affected extensions
-
Go to Settings Classic > Monitored technologies.
-
Check both tabs:
- On the Supported technologies tab, look for JMX monitoring in the Type column. The affected official extensions are listed in the EF1 extension column of the mapping table below.
- On the Custom extensions (deprecated) tab, look for JMX in the Extension type column.
If any JMX extensions are enabled or bound to process groups, your environment is affected.
How to upgrade
The migration path depends on whether you use official Dynatrace extensions or custom extensions.
Migrate Dynatrace supported extensions
Replace each EF1 extension with its EF2 equivalent using the table below.
- Use the table to find the EF2 replacement for your EF1 extension.
- Deploy the EF2 extension. For details, see Manage Extensions.
- Disable the EF1 extension monitoring configuration — go to Settings Classic > Monitored technologies > Supported technologies and disable JMX monitoring for the technology with Monitor the environment toggle.
| EF1 extension | EF2 replacement extension |
|---|---|
| Connection Pools: JBoss ( |
| Apache Kafka ( |
| IBM WebSphere Liberty ( |
| Connection Pools: WebSphere Liberty ( |
| Tomcat (JMX) ( |
| Connection Pools: WebLogic ( |
| WSO2 API Manager ( |
| Apache ActiveMQ Classic ( |
| Eclipse Jetty ( |
| Apache Cassandra ( |
| Hadoop ( |
| Hadoop ( |
| HornetQ ( |
| Apache Solr ( |
| Apache Spark ( |
| |
|
Convert custom extensions
-
Convert your EF1 custom extension to the EF2 format. For details, see Migrate JMX extensions.
-
Delete the old EF1 custom plugin.
- Via UI: Go to Settings Classic > Monitored technologies > Custom extensions (deprecated) and delete the plugin.
- Via API: Use the Plugins API (
DELETE /api/config/v1/plugins/{id}/binary).
Related topics
Extensions