📢 Support ending for the Chrome and MS Edge browser extension by January 2024

[AgataWlodarczyk]

Dynatrace discontinues support for the Chrome and MS Edge browser extension by January 2024 as remotely hosted code will no longer be allowed for those browsers.

The SaaS vendor RUM browser extension will soon no longer be hosted in the Chrome store as remotely hosted code is being disallowed by Google. As a result, the JS Agent will no longer pass the Chrome store review process and subsequently, Dynatrace will no longer support browser extensions as of January 2024. However, Dynatrace has solutions available for customers on a case-by-case basis. 

Read more:
1. Overview
2. What it means to our customers 
3. Timeline 
4. Alternative Solutions 

- - -
1. Overview 

One of the consequences of the rollout of Manifest Version 3 for Chrome and Microsoft Edge  extensions is that remotely hosted code will no longer be allowed. An extension will only be able to execute JavaScript that is included within its own package. Because we inject the JS Agent into the customer’s page, and it’s not bundled with the browser extension, we will not pass the Chrome store review process beyond June 2023. Even if we were to bundle the JS Agent within the extension, it would most likely not be approved because we are using some functions that will not be allowed. 

- - -
2. What it means to our customers 

This means that we will have to discontinue support for the extension and the customers who use our browser extension to inject data will not be able to do so any longer.   

- - -
3. Timeline 

As of the first release of MV3 from Google in January 2023, Dynatrace can no longer update the extension. However, it will still function in the stable versions of Chrome but might be rejected in dev/beta/canary versions.   

In June 2023, the extension might also be rejected in stable Chrome versions, but the customers can disable the rejections for both of these scenarios with an Enterprise policy.  

Once v2 extensions are deleted from the Chrome store, the extension will no longer be usable even with an Enterprise policy.

- - -
4. Alternative Solutions  

Depending on the type of customer application (e.g. Salesforce, Office 365 etc.), there might be other options such as Agentless monitoring with manual injection. We are aware that this solution might not work for all customers, and we’d have to look at applications on a case-by-case basis to see if there are other alternatives. For example, for Salesforce, we also have the option of using the Salesforce Streaming API. 

[ChadTurner]

Thank you @AgataWlodarczyk for this Notice

[Fin_Ubels]

If there's one thing you can count on, it's google discontinuing something 😢

[michael_taylor]

can we put this link in the documentation as well.

[Xin_Peng]

It's a sad news as we just enabled RUM browser extension monitoring. The timeline section  motioned about Google Chrome only.  Will it apply to MS Edge as well? is Edge a better choice from now on to Jan., 2024? Will MS Edge continue to support RUM extension?

[Mike_L]

The announcement is for both Chrome and Edge.

[loutfi_samadi]

This is a big ouch, as we're left with just two options, OneAgent and Agentless 😭

[Akhil-Jayendran]

Sad news, Thank you @AgataWlodarczyk  for this Notice. We are missing one easy way of agentless injunction.

[MattSeverance]

January 2024, will it still be useable or a Hard cutoff? Completely done by Jan 2024? Is it based on a particular version? Old versions that would still have extensions - an old version might still work? Asking for one of my clients that uses SAP C4C. Thanks.

[bernhard_lackn1]

They will remove it from the store. So the extension cannot be installed any more. We do not know if the plugin will also be kicked out by certain Chrome version but we assume that this will also happen at some point.

[fstekelenburg]

This is interesting enough to know. If (and as long as) the browser, and extension, is not updated, will the extension keep functioning? This may give organisations some extra time.

[natanael_mendes]

thanks @AgataWlodarczyk for this notice

[Daniël]

As the expiration date is coming closer and closer the webextension is going to become unavailable I hope there are already some best practices or tips available which can be shared over here.
In my company we're trying to move, where possible with vendors, from the webextension to the agentless solution. For some it looks promising for some a bit challenging.

A few question I have:

- which suggestions are there for applications that can't move to an agentless solution? (eg a saas provider isn't supporting the ability to add a javascript tag)

- any suggestion to change the configuration within Dynatrace for an application from webextension type to agentless? I'm hoping to keep the existing application running (including baselines, history, configuration etc etc) and have it being modified in the backend rather then creating a new application and migrate all the settings with the consequence that baseline needs to be built again, key user actions to be defined and the history of the application remains behind in the old one. So far support is indicating that they can't change the type of application within Dynatrace.

Looking forward seeing the responses in this matter.

[bernhard_lackn1]

I'll try to answer the questions:
- Suggestions for applications that cannot use agentless: We need to look into that case by case. Sometimes applications support injecting code in other ways or provide montoring data on their own which could be used.

-  changing application from webextension to agentless: this is currently not supported but if this is really important we could look into this. Plz check with the respective product manager (Christian Gustafson)

[sivart_89]

@bernhard_lackn1 we have an application hosted by SAP which we cannot inject JS code into the HTML pages OR install the OneAgent on the application server.

Your suggest of 'We need to look into that case by case. Sometimes applications support injecting code in other ways or provide monitoring data on their own which could be used', how would we start with that?

[Malaik]

Bad news for some clients. thanks for sharing.

[AurelienGravier]

So sad, it was a great alternative for all applications without the possibility of manual injection!

Google calls the shots! 😳

[fstekelenburg]

Question: has this accouncement only be placed on the community? I can not find it in the release notes or other source.
Unfortunatly not all organisations are following the community (I know, wonder why not as well :)).
This means that it may come as of a unpleasent surprise for those who don't. 
@AgataWlodarczyk ?

[tijust1]

@AgataWlodarczyk What is the solution for Workday as this is another SaaS based application. Do we have any other alternative?

Thanks,

Tijust