Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
How Does the .NET Profiler Communicate with the eG Agent?
The eG agent should be deployed on the same IIS web server that hosts the .NET profiler. The profiler communicates with the eG agent via that port number 14001, by default. You can change the default port by following the steps below:
Typically, once the eG agent is configured with the details of the web site to be monitored, the profiler contacts the eG agent and downloads these details from it.
Figure 1 : Communication between the .NET Profiler and the eG Agent
Then, when a transaction request for the web site comes in, the profiler injects a code in the CLR to trace the path of that request. In the process, the profiler also collects response time metrics related to that transaction. Every 10 seconds, the profiler sends these metrics to the eG agent. The eG agent stores these metrics in memory, until the next time it runs the .NET Business Transactions test. When the test is run, the agent pulls the metrics stored in memory and sends it to the eG manager.