Force the scripted synthetic monitor to use Internet explorer instead of Chrome

We are trying to create a new synthetic monitor using scripted browser type, we started with the login script then we have a procedure to check the reporting site where we execute a sample report and search for a text field to validate the RM site.

Problem: The sample report is executing but not generating the output in Chrome browser, due to compatibility issues or others.

We want to execute the sample report in IE where it is generating the output correctly. tried User-agent to simulate Internet Explorer but of no luck

$browser.addHeader(‘User-Agent’, ‘Mozilla/5.0 (compatible; MSIE 10.6; Windows NT 6.1; Trident/5.0; InfoPath.2; SLCC1; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 2.0.50727) 3gpp-gba UNTRUSTED/1.0’);_

Please help.

1 Like

Hi @Mbsyed

Unfortunately using $browser.addHeader(... doesn’t change the driver used for the script. It just updates the HTTP Headers when communicating with your server. At present, there is no method to run the script on a different browser. I will open a feature request for you however!

You can read more about the addHeader portion of your script at the following forum post:


How do we know what are the feature requests that are in pipeline and when they will be release

Hi @Kiran_Tanikella -

We are not able to publish our product roadmaps publicly. We do, however, try to come back to these topics when a new feature is implemented to let you know.

Thanks for your understanding.


Do we have any update on when we will be able to use synthetic monitors to test with different browsers? We would like to test as Firefox and IE.

Hi @David.Margot - Unfortunately, this is not something that’s on our roadmap right now. We’ll let you know if that changes.

Is there any plan yet to implement this functionality into New Relic to test with different browsers?

Hi, @christopher.moore: I am not aware of any plans to implement this functionality. My understanding is that Synthetics relies on the Chrome DevTools Protocol, so supporting other browsers would require a complete rewrite.

1 Like