.NET

Features

Germain monitors Uptime, Performance and Usage of .Net Application.

Requirements

Compatibility Matrix

The following table shows the versions of Windows and .NET supported by the Germain Profiler:

Configuring a .NET CLR Monitor in Germain

Deploy a new .NET CLR Monitor via the Germain ‘.NET CLR (C#, etc) Agent’ Wizard:

Germain Workspace > Left Menu > Wizards > .Net

• Go to 'Wizards' then find the '.NET CLR (C#, etc) Agent' Wizard

• Click ‘Add'

• Fill in the Monitors details then click ‘Next’

• You can download the agent here or go to our Wiki.

• Click ‘Finish’ to continue.

• There is a link to the related dashboard.

• Click Close to exit the Wizard, or Click ‘Add Another’ to repeat the Wizard.

Configure Profiler Files on Hosts

Single Host Installation

This method describes the manual installation method of the profiler files for a single host.

1) Deploy the installer to the target machine and execute the installer

2) Click ‘Next’

3) Enter the path for installation. Choose if it is for everyone, or just the current user. Click ‘Next’

4) Click ‘Close’

Bulk Host Installation via Active Directory

This method is for administrators who need to deploy the profiler to a large number of systems.

Creating a GPO to Assign a software to be installed:

For bulk installations across your enterprise you will create a GPO in your Active Directory. In this GPO you will need to Assign the Package to the group of Users or Computers you wish for the profiler files to be installed on. Please see the Microsoft documentation linked and review the section “Assign a package“ for details: https://docs.microsoft.com/en-us/troubleshoot/windows-server/group-policy/use-group-policy-to-install-software#assign-a-package

How to: Alter the Installer to change Default Install Path:

When installing in bulk, you may need to change the default install path of the Profiler Files. The instruction below will explain what you need to do to make this change to the installer.

You will need to get the Microsoft tool Orca.exe to modify the installer: https://docs.microsoft.com/en-us/windows/win32/msi/orca-exe

To get ORCA:

you will need to use the “Windows SDK” installer.

• Get the “Windows SDK” installer

  • Search for 'Windows SDK' and get it from the Microsoft site

• Run the “Windows SDK” installer and choose to download “MSI Tools“

  • Please note where you chose to download the files to

• Go to the directory you downloaded the file to and run the ‘Orca-x86_en-us.msi’ installer

• Once installed, you can open ORCA by right clicking on the Germain .NET Profiler .msi file and choose “Edit with Orca”

• Go to the Property table and add the property “TARGETDIR” with your choice of directory for the value.

• Use “Save As…” to create your new installer file with your non-default install directory.

Configure Profiling for .NET Applications

Profiling a .NET application

How To: Attach Profiler to Running .NET Application

Starting with .NET4, it is possible to dynamically attach the profiler to a running CLR. To do so, run the following command with specific process ID: 

How To: Launch .Net Application with Profiler Attached

The profiler console can be used to list all currently running .NET CLRs. Please note, that the 32 and 64 bit versions of the console will only show .NET CLRs of the corresponding architecture (i.e., 64 bit console will only show 64 bit CLRs).

 For each CLR, the console will display the process ID, CLR version, and application path. For a list of .NET runtime versions, see https://msdn.microsoft.com/en-us/library/w4atty68(v=vs.110).aspx#version.

To start profiling a new .NET executable, run the following command: 

Profiling to a ASP.NET Application

The following instructions are specific to monitoring Internet Information Services (IIS), but should be applicable to monitoring other Windows services as well.

1. Create new environment variables to enable profiling: 
   

   

2. Create an environment variable for the profiler class ID ({D768E37F-294B-43D3-9178-250C40F6F8C1}): 
   

   

3. Create registry key to specify the executable to monitor under HKEY_LOCAL_MACHINE\SOFTWARE\Germain Software\Germain Profiler 
   

   

4. Restart the server to apply the environment variables. The profiler will automatically attach the next time the IIS service is started.