5.5 Web server agent on IIS 7.5
I've just upgraded to dynaTrace 5.5 (5.5.0.5227) on Windows 2008 R2 (IIS 7.5). I added the web server agent as detailed in the documentation to one of my applications (there are a few on the IIS server). However, in my "Agents Overview" dashlet, I am seeing every application pool listed. Further, the Javascript agent is not being injected.
When I run the health check, the error that gets reported under Injection Check is "UEM is deactivated on connected agent. There might be some connection issues between dt server and the connected agent". However, looking at the logs I see that does connect and can access the Shared Memory
The documentation looks almost identical for 5.5 as it did for 4.2 for the web server agent, but I'm wondering if I need to do something different to:
A) Only have the web server agent be injected into one application (I wonder if I am using multiple licenses here)
B) Get the Javascript agent injected.
Hi. Have you started your "dynaTrace Web Server Agent" Windows Service? Web Server Agents injected into IIS will communicate with the local Web Server Agent Service that will run on the same machine. This is the service that is actually THE "MASTER" AGENT that you will see in your Agent Overview Dashlet. When adding a new Tier to your System Profile you will get detailed instructions on how to modify the dtwsagent.ini file and then launch the web server agent service.
I think this is the missing step in your scenario
The service was running and was reporting properly to the server, but I uninstalled and re-installed the agents on the web-server anyway. It looks like the initial install did not register the module within IIS. I now am getting the Javascript injected down to the client.
However, I still see multiple sub-agents listed under the master agent. This is my configuration:
Server
-->Sites
------>Default Web Site
----------->web
"Default Web Site" has it's own application pool, let's call it "DefaultAppPool". Then the application "web" has it's own application pool, let's call that "WebPool". Even though I only have the module configured at the "web" level (not at server or default web site level), I still get sub-agents for "DefaultAppPool" along with "WebPool".
Am I using 2 WebServer agent licenses in this scenario (or do you only count master agents)?
Is the dynaTrace DLL getting loaded by the "DefaultAppPool" and called in the request process (even though it should not be doing any work)?
I had the same issue a while ago, since you have 5.5.0.5227 you should only be consuming one license.
I think you get subagents for all App Pools because the dynaTrace Module is also enabled on the "Sites" level. I didn´t investigate much further since this only consumes one license so I didn´t mind having the DefaultWebSite showing up on my Agents Overview.
Thanks David. What about the dynaTrace dll? Does it still get called in the IIS request process? I don't want to introduce overhead in my other application pools that I'm not monitoring.
I am also interested to know the answer- will the dynatrace dll be loaded for all the sites underneath the default site? In my case, the site I want to monitor is configured under the default site- so I don't have any option other then adding the ISAPI filter module (IIS 6) at the default site level.
Jigar
The DLL will be loaded for all sites where it is configured to be loaded. I dont have IIS6 available in the moment. But - if you load it for the Default Site the default behavior is to load it under all sub sites as well. I am not sure if there is an option in IIS6 to exclude certain modules from being loaded on sub sites. In IIS 7.x that is possible.
Thanks Andi. I just looked at the IIS Manager again and I could not find a way to exclude module at the subsite level in IIS 6. If anyone knows how do it for IIS 6- please let me know.
Jigar
