Pre-requisites for Deploying the eG .NET Core Profiler

As already mentioned, eG .NET Core profiler is capable of monitoring transactions to .NET Core applications running on Kestrel and/or IIS web servers.

The following are the pre-requisites for performing .NET Core business transaction monitoring for Kestrel and IIS web servers:

• An eG manager 7.2 and above

• An eG agent on every Kestrel web server in the transaction path; if multiple .NET Core instances on a single server are monitored, then a single eG agent on that server would be sufficient.

• The eG .NET Core profiler is supported only in the following environments:

  • Supported Operating Systems

    • CentOS 64-bit

    • Ubuntu 64-bit

    • Microsoft Windows Server 2012

    • Microsoft Windows Server 2012 R2

    • Microsoft Windows Server 2016

    • Microsoft Windows Server 2019

    • Microsoft Windows Server 2022

    • Microsoft Windows 7, 8.1, 10

  • Supported Web Servers

    • Kestrel web server running as a stand alone server or as a service;

    • Microsoft IIS versions 7.0, 7.5, 8.0, 8.5,10

  • Supported Frameworks

    • Microsoft .NET Core versions 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0

    • Open Web Interface for .NET Core Web API

    • ASP .NET core MVC 2.0, 2.1. 2.2, 3.0,3.1, 5.0, 6.0

    • RAZOR

    • BLAZOR

  • Supported Data Storage Types and Clients

    The .NET Core profiler supports the ADO.NET data storage type and the following ADO.NET clients:

    Database Name	Client Type
    Oracle	ODP.NET and Microsoft Provider for Oracle
    MySQL	Connector/Net and ADO.NET
    Microsoft SQL Server	ADO.NET
    PostgreSQL	Object-relational database
    Sqlite	Self-contained
    EntityFramework	Code First and Database First
    Mongo	C# and .NET MongoDB Driver

  • Supported Remote Procedure Calls

    • HTTP

    • AJAX asynchronous calls and Signalr client calls are supported

  • Supported Message Queue Calls

    • RabbitMQ

    • ActiveMQ

  • Supported Windows Azure Remote Services

    • Azure Table Storage

    • Azure MySQL

    • Azure SQL

  • Managed Windows Service

    • Web API

    • WCF-based Service

  • Supported Loggers for the .NET Core BTM

    • NLog

    • Log4Net

    • Event Log

    • Serilog

• For complete visibility into the transaction path, make sure that you BTM-enable each Kestrel and/or IIS web server in the transaction path.

• To track and profile transactions to multiple web sites on an IIS web server, you need to add a separate Microsoft IIS component in eG Enterprise for each web site to be monitored.

• To track and profile transactions to multiple web sites on a Kestrel web server, you should manage each web site as a separate Kestrel Web component in eG Enterprise, with each component configured to listen on a different port;