How to configure web server agent to avoid sub-agents for each app pool
Hi,
We are using DynaTrace v5.5 and we also see the sub-agents in the Agent overview as in the post: 5.5 Web server agent on IIS 7.5
We would like to configure two agent groups for each app pool instead of dynatrace creating sub-agents for each app pool.
Here is how our Agent overview looks now.
We have one agent group 'EnvO-WSShop' , we would like to create two agent groups
1) EnvO-WSShop and 2) EnvO-WSMobile and connect each of the above sub-agents into these groups.
-Sreerag
If I am using v6.1- do I still need a seperate fixpack to resolve this issue?
From the above thread: Please upgrade also to the latest FixPack (build 5562), because we had a problem if a web site without the dtagent module is using the same application pool than an other web site with the dtagent.
My question is related to subagents not licensing.
Hi,
Starting with dT 5.5 and fix pack 5227 we only license for web servers the installed instances. As you can only install one IIS per OS you will only consume one license (even if you install two or more master agents!). See screenshot below!
Please be sure to have two separated root directories, if you want to go this approach - that means, if the default dT agent is located under:
"C:\Program Files (x86)\dynaTrace\dynaTrace 5.6.0\agent" you have to use for the second agent a directory with a different name like:
"C:\Program Files (x86)\dynaTrace\second_dynaTrace 5.6.0\agent"! Two agent directories (even with different names) in one root directory will not work:
WILL NOT WORK: "C:\Program Files (x86)\dynaTrace\dynaTrace 5.6.0\agent" and "C:\Program Files (x86)\dynaTrace\dynaTrace 5.6.0\agent2"
Before i try duplicate installation of web server agent I want to confirm if this will mean additional license or not.
-Sreerag
Yes - you will need extra Web Server Agent Licenses as every (Master) Web Server Agent requires its own license
OK, that makes sense,
A slightly different than the comment in this post Re: apply wsagent on only one website (it says for one OS only one web server agent license is used)
If you can duplicate the agent installation, then it will work!
For IIS you can not use different agent groups for different websites (and therefore also application pools). You can activate the agent (the module) only for a specific web page, but it is not possible to map web sites into different agent groups.
Please upgrade also to the latest FixPack (build 5562), because we had a problem if a web site without the dtagent module is using the same application pool than an other web site with the dtagent.
Alex
Which means we cannot get something like this?
Our current agent overview is with sub-agents under one agent group
I'm going to try the 'Multiple Web Server Agents on a Single Host' as suggested by Andi
-Sreerag
Andreas
In my case we have enabled the module on only one website but we see the subagent being loaded on other sites as well. How can we avoid it ?
Please double check if you havent configured it globally for all Web Sites in IIS. There is a global option for that.
If that doesnt solve your problem I suggest opening a support ticket. We have had a case in the past where due to a bug we loaded our module on every site. So - the question also is on which dT version you are running on?
Installation of the latest SP fixed the problem. Apparently, they have installed the GA version 
Thanks.
Aaahhh - now I understand. You want to have two different "Master Web Server Agents". For that check out the section on "multiple web server agents on a single host" on the following doc page: Web Server Agent Configuration
Yes, we do that, we enabled the module for each app pool. But how can i specify multiple agent names in the web server agent .ini file?
The agent name in .ini file is EnvO-WSShop-<server_name> but we also want to configure another web server agent called EnvO-WSMobile-<server_name> (this is for the MObile app pool)
In IIS you should be able to configure our native dynaTrace Web Server Agent Module on each Web Site which then maps to an application pool. So - instead of enabling our Module for EVERY website on IIS (I think there is a global option to do this) - you can enable this module per Web Site. That should give you what you want
