Trying to debug an issue with the proxy device and we are trying to get the header information sent by the request. Any thoughts on if there is a debug option that will spit out the header info to a log file and the log file location what will help debug synthetic browser based transaction test
Solved! Go to Solution.
is this an internal or external synthetic? Assuming that it is an internal synthetic, you could always review the logs on the activegate performing this synthetic. If this is external, id open a support ticket for further assistance with this.
Hi @Moses C.
the first question is .. what is the error?
In my understand you set up the activegate. So i think:
Before Proxy I suggest checking installation. This was my case.
all chromium packages are installed as expected? maybe you miss a library because not available in the repository or the version is not the requested one.
It's a dedicated Activegate? (suggested)
So I suggest you start a clean installation and look to the screen and log for error. After the proxy, it's base on your environment
Speaking about Proxy all depends on your proxy security policy.
If it's in Linux Activegate, you could get it out from Chromium.
In my case, I also have private locations and I have resorted to capturing traffic through tcpdump. Nowadays, almost all traffic is encrypted, but if not, that is probably your easiest solution...
You can do a lot with Chromium. There are several options, take a look at https://www.chromium.org/developers/how-tos/debugging-on-windows It's better to do it in Linux than Windows, because in ActiveGate/linux you have to install/update Chromium by yourself.
But the usual logs will not get you the header information. Your best option will probably be to wrap the invocation around the option --log-net-log, but beware it can grow very, very fast. Other options are available here:
I have done this a lot in other circumstances, but not with Activegate. I would consult with your Dynatrace contact first, though.
You can also click the reward link 😉
my organization is switching to Zscaler - so there is no more proxy. There seems to be a call to google and google api right when the browser is launched for synthetic browser transaction. I am trying to find what are the headers for the call. Or better yet is there a way to turn off that call.