Looking for a temporary 3rd party browser recorder to validate synthetic checks. (1502 html elements not found)

[runatyr]

Good morning Dynatracers... I hope all is well for you. 😎

So we have enabled a new basic synthetic check that reached our main website, logs in, and then logs out.

What I am seeing ... over the last 2 days is on "average" an 8-10% failure rate .

We see from 4 different locations in Azure and AWS the same failure of

1502...element can not be found. The image from the synthetic check.. shows just a blank page where the page is redirecting. (I'll include) When I ruin this in playback .. I do not encounter this (so far....)

All of that said, I will likely need to provide similar results from a second/temporary 3rd party tool.

If anyone knows of a temporary browser recorder that would behave similar to a Dynatrace synthetic check

that would be a perfect way to validate the findings.

Is there an easier way to validate outside of a browser recorder? I am not a developer.. so my programming skills are limited.

Ideally, I'd like to run it from a cloud presence but I can resort to an on prem desktop if need be.

(The screen shot we receive when failing.)

[HannahM]

Before checking using another tool, I would try changing the wait to something else, as it looks like the page hasn't waited for long enough. If there's another event after it, I would try 'wait for next event', otherwise, you could wait for a specific element to appear or try waiting for a specific amount of time. You can find the list of wait options here

[Kor03]

Is the auth some kind of third party SSO (Azure/Okta/etc)? If so, that's going to be an issue with any synthetic/headless browser tool. When an authenticated user performs the recording from their browser or tries the playback from the Synthetic app, the auth works differently and does not redirect to the auth provider the same way. On a fresh headless browser for an unauthenticated machine, it will try to redirect you to your auth provider which messes up the synthetic flow of what was recorded. The only "workaround" we've found is to internally file an infosec variance and allow the auth clients created for Synthetic use to bypass SSO altogether (we have other controls in place for security concerns).

I've never done it, but its supposed to be possible to use a Windows ActiveGate that is joined to your domain and has an active user account to pull this off. Could be worth a shot? https://community.dynatrace.com/t5/Synthetic-Monitoring/Testing-SSO-with-Synthetic-Monitoring/td-p/1...