How Does the eG Profiler for Windows Service Applications Communicate with the eG Agent?

The eG agent should be deployed on the same Windows system that hosts the .NET / .NET Core profiler for Windows service applications.

The profiler monitoring web-based Windows service applications communicates with the eG agent via port number 14004, by default. Similarly, the profiler monitoring standalone Windows service applications communicates with the eG agent via port 14005, by default.

You can change this default port , if required. To know how, follow the procedure described in the Configuring Communication Between the eG Business Transaction Profiler and the eG Agent topic .

Typically, once the profiler's listening port is configured, the profiler contacts the eG agent via that port and downloads details of URLs or .NET function calls (as the case may be) to be monitored.

Then, the profiler injects a BTM code in the application's code, whenever a transaction request is received or a method/function is called by the target application. This BTM code traces the path of that request/method (as the case may be). In the process, the profiler also collects response time metrics related to that transaction/function (as the case may be). 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 BTM test. When the test is run, the agent pulls the metrics stored in memory and sends it to the eG manager.