UEM js injected but no data
Hi all. I'm in a POC trying to configure UEM... UEM js agent is injected on page code, but no UEM data is retrieved. I tried to change dtagent and dynatraceMonitor path but any path I use I got the same... 404 page when trying to access dtagent or dynatraceMonitor.
I cannot pass UEM Health check because each time I try I get a 407 HTTP error due to I'm at customer site connedted with proxy configured.
What I'm missing? App is configured, UEM activated for this Application, js agent is injected to the page, but no data...
Using 6.2 BTW
Thanks in advanced
JM
That is really odd as you configured a URL that looks the same as the other JS files are using. I would double check if there are any other restrictions on that Web and App Server they are having. Try to get access logs of the web server as well.
Also - make sure that this IP is not load-balanced and that the actual request REALLY goes to the Web/App Server you have a dynatrace agent installed. In case the environment is load balanced you might just be unlucky and you are randomly hitting a server that doesnt have dynatrace agent injected
Andi
Hi Jose,
It's strange that no matter what you change, you keep getting 404s. It seems that the main issue you're having is that you haven't found the right URI for it yet. I would focus on being able to find the right URL for the dtagent file because that will help with the monitor as well.
In your document you have your URI as /b2b/js/b2c/comun/dtagent(...). I would try some similar URIs to other objects that are being loaded on the page, such as "/b2b/js/b2c/dtagent" "/b2b/js/b2c/comunes/dtagent". I assume you tried the default /dtagent already. You should just be able to try to look for this by trying different URIs in your browser without changing anything in Dynatrace - the file will still be there - once you find it, then you can change the configuration.
Let us know how you go.
Andrew
Hi guys, we get it. Finally apache server in front of Tomcat (where we are injecting the js agent) was blocking the signal. We had to configure 2 rules on Apache in order to force Apache to ignore /dtagent and /dynaTraceMonitor requests, and then requests are sent to Tomcat server where our java agent is working.
Best regards
JM
Thanks Andi and Andrew! Yes it is really odd...
I will continue playing with different URIs, but in fact I already tested some of them. More info just in case:
- We are injecting js agent from Java agent (in Tomcat), because webservers are Apache on Solaris x86, and we don't support such agent.
- No other "no monitored" nodes for this app. This is a PRE env where there is only 1 node receiving requests
Any advice and help will be welcome :D
BEst regards
JM
Hi Jose,
Is there anything that could block this request? Like a particular apache module or so? Maybe try to request the file directly on the tomcat server, not going through apache, to see if that works.
KR, Kristof
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
