Quick installation and troubleshooting

Windows

Check service status

Check that the WhaTap.NET service is properly registered and in Running status.

Run the services.msc command as administrator, or double-click the Services icon in the Control Panel to open the Services manager.

The WhaTap .NET service transmits collected monitoring data to the WhaTap server. Check agent-related logs at C:\Program Files\WhaTap .NET\logs and C:\ProgramData\WhaTap\dotnet\logs.

If problems occur after installing the .NET agent, check the following items and resolve the issue. If the problem is not resolved, contact support@whatap.io. You can also get additional support through the chat window that appears when you click the button in the upper right of the service screen.

Note

Agent log file location

The agent log files may be required when inquiring via email or chat.

• C:\Program Files\WhaTap .NET\logs

• C:\ProgramData\WhaTap (If this path does not exist, ignore it.)

When all data is not collected

If data is not collected on all widgets, check the following:

• Verify that the project access key and collection server information are correctly entered in the whatap.conf file for agent configuration.

• Check the firewall settings on the server. Port 6600 must be open for outbound connections.

When hitmap data is not collected

If hitmap information is not collected properly, check the supported environment for the user's application. For the supported environment for .NET application monitoring, refer to this document.

Even if the server's .NET version meets the supported environment, if the application version is not .NET Framework 4.5 or later, data collection for monitoring may not work properly.

When support cannot be determined or the application may be supported

Send the target application's web.config file to support@whatap.io to inquire. If possible, it is recommended to also provide the project file (.csproj).

Check system environment variables

1. Run the sysdm.cpl command to open the System Properties window.

2. Click Advanced > Environment Variables to check that the system environment variables are properly registered.

   

3. System environment variables are automatically registered when installing the agent. Check that the following are registered.

   • WHATAP_APP_TYPE = 7

     Fixed value for the type of agent communicating with the WhaTap server.

   • WHATAP_DOTNET_HOME = C:\Program Files\WhaTap .NET

     Home path of the WhaTap program.

   • WHATAP_DOTNET_TRACE = 1

     Activates the monitoring data collection function.

Check GAC

When installing the agent, DLL files are automatically registered in the GAC. Check the registered files at the C:\Windows\Microsoft.NET\assembly\GAC_MSIL path.

📄 Sigil

📄 Microsoft.Diagnostics.NETCore.Client

📄 Microsoft.Diagnostics.Runtime

📄 System.Diagnostics.DiagnosticSource

📄 System.Memory

📄 Whatap.Startup

📄 Whatap.Loader

📄 Whatap.Tracer

Note

Manual GAC deletion

Even after uninstalling the agent, data registered in the GAC is not automatically removed. If necessary, manually delete them from the C:\Windows\Microsoft.NET\assembly\GAC_MSIL path.

Linux

Check environment variables

Five environment variables are set through the install.sh installation.

• WHATAP_DOTNET_HOME = "/usr/whatap/agent/dotnet"
• CORECLR_ENABLE_PROFILING = "1"
• CORECLR_PROFILER = "{21CAE18A-4E44-4578-83FD-0576AAA47E68}"
• CORECLR_PROFILER_PATH = "/usr/whatap/agent/dotnet/Whatap.ClrProfiler.so"
• DOTNET_STARTUP_HOOKS = "/usr/whatap/agent/dotnet/Whatap.Startup.dll"

Check installed files

After installation, files are created at the /usr/whatap/agent/dotnet path.

📄 Whatap.ClrProfiler.so	Native CLR profiler
📄 whatap_dotnet	GO module daemon executable
📄 Whatap.Tracer.dll	.NET tracer
📄 Whatap.Loader.dll	.NET loader
📄 Whatap.Startup.dll	.NET Startup Hook
📄 whatap.conf	Agent configuration file
📄 whatap.env	Environment variable file for systemd
📄 VERSION	File indicating the agent version
🗂️ logs/	Agent log directory