I have received another notification email from Dynatrace involving EF1 termination in October.
The good news is that the sunset date for JMX and PMI extensions 1.0 has been extended to March 2025. The bad news is that I don’t use them, nor know anyone who does, but do have dozens of Python extensions ![]()
We also know that:
- There are several Dynatrace extensions that will not be migrated to EF2:
https://community.dynatrace.com/t5/Extensions/Which-Dynatrace-EF1-extensions-are-not-going-to-be-migrated-to/td-p/247057 - In particular, Generic DB query will not be migrated, and the suggested process is cumbersome, to say the least:
https://community.dynatrace.com/t5/Extensions/Generic-DB-Query-in-EF2-when/td-p/246987 - The Port, ping and DNS extensions are about to be replaced by a new synthetic offering that no one knows about.
- Data continuity seems to be a problem in the transition. That leads to multiple problems involving the data, alerts, and everything around it. Theses issues have not been dealt with.
- There is no plan B for those extensions that cannot be feasibly migrated by the end of October. Will maintaining ActiveGate at the mid October version work? Are there other ways to maintain functionality, even admitting that the Python support for 3.8 ends in October?
These are the notes that I recall rapidly. There are several others. How are you all dealing with this?

