We are having multiple sites hosted on one server. Earlier only one site was configured under dynaTrace but now we have added two more sites under AppMon.
The dilemma is, I can see app server agent as well as primary web server agent but secondary web server agent is not visible.
Does somebody come across such an issue? Kindly help.
Solved! Go to Solution.
Hi. If you want to monitor multiple sites that are hosted by your IIS you need to make sure to enable the Dynatrace Web Server Agents Modules for every IIS Web Site. Also remember that - if you enable the Dynatrace Web Server Agent Native Module that you pick the correct bitness (32 vs 64) depending on how your AppPool is configured. This will make sure that IIS loads the correct Dynatrace Web Server Module into each hosted site.
Thanks for your input.
Any configuration step Am I missing here? Kindly suggest.
Note:- I have created two separate profiles on client for these sites.
Try the following:
If you instrument several web server instances on the same machine, the secondary Agents of the web server instances connect to the same Primary Agent service (Windows) stemming from the same directory structure and configuration in
<DT_HOME>/agent/conf/dtwsagent.ini. They share the UDP and
If your web server instances run different web sites and you want to have data for each web site in a separate System Profile:
.ini) and Agent name (and possibly a port on that the Collector listens) for each Web Server Primary Agent instance in
Read more from the following link:
Just an FYI.
-> You only need one Dynatrace Web Server Primary Agent (configured via dtwsagent.ini) that can operate on the default UDP port. That Primary Agent can handle multipile IIS Web Server Modules.
-> The only reason why you would want to have multiple Dynatrace Primary Web Server Agents is when you want to report the data for your different Web Sites into different System Profiles
-> Please ONLY load ONE version of the Agent (correct BITNESS) into the IIS WebSite. If you select both IIS might not be able to correctly launch the Web Site! Thats why it is important to first go to your AppPool settings to figure out whether the apppool runs on 32 or 64bit. You can find that information in the "Advanced Settings" on the apppool. There is a setting called "Enable 32bit apps". If that value is true it means it is a 32bit process otherwise 64bit.
Able to sort out the issue. Don't know how technically that worked but I followed below steps (suggested by support) to resolve this.
2. Resuming configuration back i.e. making APP1 module as default module