Configuring Tests for Monitoring .NET Core Business Transactions

Once the required server is managed, you need to configure the test that will report the health of business transactions to the .NET Core web site/application hosted on that server. What test is to be configured and how to configure it will vary according to the server that is managed.

Configuring Test for Monitoring .NET Core Business Applications on Microsoft IIS

To monitor a .NET Core web site/application on a managed IIS web server, you need to configure the .NET Business Transactions test on that server. Note that this test also monitors transactions to .NET applications on IIS. The .NET Core profiler sends business transaction metrics it periodically collects to the eG agent that runs this test. To configure this test, do the following:

1. As soon as the IIS web server is managed using the eG admin interface, Figure 1 will appear displaying the details of the server that was managed.

   

   Figure 1 : The details of the IIS web server that is managed

2. Click on the icon corresponding to the IIS web server to configure tests for it. Figure 2 will then appear. From Figure 2, it is evident that the .NET Business Transactions test is fully configured by default. However, you will have to override its default configuration, so that the test can be configured with the name of the web site/application to be monitored. For that, from the CONFIGURED TESTS list of Figure 2, select the .NET Business Transactions test click the Reconfigure button to configure it.

   

   Figure 2 : Selecting the .NET Business Transactions test for configuration

3. Figure 3 will then appear.

   

   Figure 3 : Configuring the .NET Business Transactions test

4. The parameters of the .NET Business Transactions test will appear (see Figure 3). Here, make sure that you configure the WEBSITE NAME parameter with the name of the .NET Core web site/application you want to monitor. To know how to configure the other parameters of the test, refer to the .NET Business Transactions Test topic under .NET Business Transaction Monitoring. Finally, click the Update button to save the configuration.

Configuring Test for Monitoring .NET Core Business Applications on a Generic Web Server on Windows

As mentioned earlier, if you want to monitor .NET Core web sites/applications running on a web server on Windows, you need to manage that web server as a Kestrel Web Windows component in eG Enterprise. As soon as such a component is added to eG Enterprise, Figure 4 will appear.

Figure 4 : Choosing to configure tests for a managed Kestrel web server on Windows

The Kestrel Web Windows component you just added will be displayed in Figure 4. To configure business transaction monitoring for this component, do the following:

1. Click on the icon corresponding to the Kestrel Web Windows component in Figure 4 to configure tests for it. Figure 5 will then appear. From Figure 5, it is evident that the .NET Core Business Transactions test is fully configured by default. If you want to change the test configuration for any reason, then, from the CONFIGURED TESTS list of Figure 5, select the .NET Core Business Transactions test click the Reconfigure button to configure it.

   

   Figure 5 : Selecting the .NET Core Business Transactions test for configuration

2. Figure 6 will then appear.

   

   Figure 6 : Configuring the .NET Core Business Transactions test

3. The parameters of the .NET Core Business Transactions test will appear (see Figure 6). To know how to configure this test, refer to .NET Core Business Transactions Test topic. Finally, click the Update button to save the configuration.

Configuring Test for Monitoring .NET Core Business Applications on a Kestrel Web Server on Linux

If the managed Kestrel Web Linux server is a stand-alone web server or is used with a reverse proxy server such as Apache web server that is running on a different machine, then do the following:

1. Once you add the Kestrel Web Linux component to the eG Enterprise system, Figure 7 will appear displaying that component.

   

   Figure 7 : Viewing the Kestrel Web Linux component that are being managed

2. Click on the icon corresponding to the Kestrel Web Linux component in Figure 7 to configure tests for it. Figure 8 will then appear. From Figure 8, it is evident that the .NET Core Business Transactions test is fully configured by default. If you want to change the test configuration for any reason, then, from the CONFIGURED TESTS list of Figure 8, select the .NET Core Business Transactions test click the Reconfigure button to configure it.

   

   Figure 8 : Selecting the .NET Core Business Transactions test for configuration

3. Figure 9 will then appear.

   

   Figure 9 : Configuring the .NET Core Business Transactions test

4. The parameters of the .NET Core Business Transactions test will appear (see Figure 9). To know how to configure this test, refer to .NET Core Business Transactions Test topic. Finally, click the Update button to save the configuration.

If the managed Kestrel Web Linux server and its reverse proxy Apache web server are running on the same Linux machine, then, as already mentioned, it is enough if you manage the Apache web server alone. In this case, you will have to configure the .NET Core Business Transactions test to run on the Apache web server and pull metrics from the .NET Core Profiler. For this, do the following:

1. Once you add the Apache Web component to the eG Enterprise system, Figure 10 will appear displaying that component.

   

   Figure 10 : Viewing the Apache web server being managed

2. Click on the icon corresponding to the Apache web server in Figure 10 to configure tests for it. Figure 11 will then appear. From Figure 11, it is evident that the .NET Core Business Transactions test is yet to be configured. To configure this test, select the test from the UNCONFIGURED TESTS list and click the Configure button.

   

   Figure 11 : Selecting the .NET Core Business Transactions test for configuration

3. Figure 12 will then appear displaying the parameters of the test.

   

   Figure 12 : Configuring the .NET Core Business Transactions test for an Apache web server

4. Against the VIRTUAL KESTREL PORT parameter, specify the port at which the .NET Core application listens. As for the other parameters displayed in Figure 12, refer to .NET Core Business Transactions Test topic to understand their significance and how to configure them. Finally, click the Update button in Figure 12 to save the changes. Once this is done, whenever the eG agent runs this test, it will connect to the configured VIRTUAL KESTREL PORT and pull the metrics that the .NET Core Profiler sends.