Configuring the .NET Core Profiler to Communicate with the eG Agent

The profiler communicates with the eG agent via the port number 14001(IIS) or 14003 (Kestrel), by default. If you want, you can change this default port. The procedure for altering the port differs according to the web server that hosts the target application (IIS or Kestrel) and the operating on which the application runs (Windows or Linux).

For IIS

  1. Edit the eg_DotNetServer.ini file (in the <EG_AGENT_INSTALL_DIR>\agent\config directory)

  2. Configure the PORT parameter in the [EG_DOTNET_SERVER_DATA] section of the file with the new port number.

  3. Finally, save the file.

For Kestrel on Windows

  1. Edit the eg_CoreclrServer.ini file (in the <EG_AGENT_INSTALL_DIR>\agent\config directory)

  2. Configure the PORT parameter in the [EG_DOTNETCORE_SERVER_DATA] section of the file with the new port number.

  3. Finally, save the file.

For Kestrel on Linux

  1. Edit the eg_CoreclrServer.ini file (in the /opt/egurkha/agent/config directory)

  2. Configure the PORT parameter in the [EG_DOTNETCORE_SERVER_DATA] section of the file with the new port number.

  3. Finally, save the file.

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.

Then, when a transaction request for the web site comes in, the profiler injects a code in the .NET Core application code to trace the path of that request. In the process, the profiler also collects response time metrics related to that transaction. Every second, the profiler pushes these metrics to the eG agent. The eG agent stores these metrics in memory, until the next time it runs the .NET Core Business Transactions test. When the test is run, the agent pulls the metrics stored in memory and sends it to the eG manager.