EF1 Plan B support?

[AntonioSousa]

EOL of EF1 will happen in more or less 3 months.

Good planning for all transitions call for good Plan Bs. It's important that there are good & robust contingency plans if some things don't go as expected.

It would be important to be sure that Dynatrace guarantees that basic contingency plans work well.

Based on this, there are some questions that I believe should be answered:

1. In which Platform/OneAgent/ActiveGate versions will EF1 disappear?
2. Will OneAgent versions less than the version referred to in #1 still have the possibility to run EF1 extensions, after october?
3. Will ActiveGate versions less than the version referred to in #1 still have the possibility to run EF1 extensions, after october?
4. Will there be any difference in behavior regarding SaaS and Managed?
5. Will there be any server side limitation if #2 and #3 are possible?

These are those that occur to me now. Are you out there also having a plan B contingency plan?

[Mike_L]

Hi,

Adding the PM, @michal_nalezin if I missed something.

1. ActiveGate and OneAgent version 1.301 will no longer ship with Extension Framework 1.0.
2. Yes, but we strongly recommend that everyone upgrades to 1.301 once it's available as they'd otherwise be running unsupported software on their servers.
3. Same as 2.
4. There are no differences between SaaS and Managed in regards to the above.
5. For now, no. Eventually the Extension Framework 1.0 screens will be removed from our API and settings, but I don't think that there is a timeline for that yet. Michal can correct me if I am not aware of something.

[Mike_L]

Update to 5 based on a call I just attended. EF1 in the environment will also be removed in 1.301. However, it can be re-enabled per environment by our support/product management team if there is a need for the plan B.

[AntonioSousa]

@Mike_L,

What does it mean to "be removed"? Is it the UI? Or the configurations?

[Mike_L]

The UI and APIs, not the data. 

[AntonioSousa]

@Mike_L,

Seems reasonable as a point #5 Plan B for me.

[AntonioSousa]

@Mike_L,

Checked the Release Notes, and am a little worried right now:

1. Notices abound stating that EF1 will no longer be functional as the end of October:
   
2. But considering the speed at which AGs are being released, it might happen even early October:
   
3. You also state that "EF1 in the environment will also be removed in 1.301". Looking at the version evolution of the SaaS versions, this is set to happen still this month.
   

Given these worries, it seems to me important Dynatrace clarify when this will really happen. From my side, our planning has always considered the end of October as the transition period, so expecting no nasty surprises here...

[Mike_L]

It will be removed with version 1.301. The exact date when that is rolling out will be different per cluster, with SaaS being affected before Managed. For Managed it is currently set to start rolling out in the end of October. For SaaS OA/AG is scheduled to start rolling out in the beginning/mid of October. SaaS cluster 1.301 could indeed hit before the beginning of October.

If there is an escalation due to the screens being removed from the UI, please reach out to our support.

[AntonioSousa]

@Mike_L,

One more unacceptable thing considering this EF1 to EF2 transition...

Will escalate this internally.

[AntonioSousa]

@Mike_L,

Have several tenants already in 1.301, but screens still there and nothing in Release Notes. Has anything changed?

[Mike_L]

It was changed last week to only remove the ability to upload new Python EF1 extensions for now.

It is still scheduled for removal from OA/AG 1.301.

[Mike_L]

It's been decided that OA/AG 1.301 will not hit environments before the 31st of October deadline. This will give customers and partners the communicated timeline to migrate their extensions.