I am having difficulties recording a new script in the Dynatrace Recorder.
We are using Private Last Mile (PLM) to monitor internal intranet websites that do not require the http/https prefix - i.e. example.intranet.point (not http://example.intranet.point).
I have configured single url tests from within the portal and these are running successfully without adding the http prefix. But now I would like to record multi-step transactions and every time I enter the url within the Dynatrace Recorder, when I click run it adds the http:// prefix to the url and fails to run.
How can I prevent the Dyntrace Recorder from adding the http prefix?
Answer by Gary S. ·
Hi @Kerry C., the script is going to need some prefix there in order to make and receive the http request. It does not need to be explicitly added (you could just add dynatrace.com) but the browser will attempt http. It is not the recorder adding it in, but rather the browser and server where our navigate action will take the result from what we seen. You can change the navigate action to not include it, but the same will happen in playback that a prefix will be put back, the browser will try for http.
Just a thought, but is it possible you are running the single URL test on a PLM node, but when you playback in the recorder it is running from your local machine which can't access it, is a possibility? You could deploy the multi-step test to the PLM node and share the results?