Skip to main content

Troubleshooting

Why Can't Stack Trace Information Be Collected?​

Currently, in slow trace details or error details, it is not possible to view the stack trace information corresponding to .NET Core code methods. The root cause is that collecting StackTrace on the .NET Core 3.0 platform has poor performance. According to estimates, each StackTrace execution can cause millisecond-level CPU usage.

Technically, we can collect stack traces, but due to performance issues, enabling this feature would severely impact user application performance. Therefore, we have not enabled stack trace collection for now.

To resolve this issue, we need to wait for the .NET Core team to develop a more efficient StackTrace method.

Viewing Logs​

If the Agent is not working properly or there is no data, you can usually get more information from the logs to locate the problem.

  • On Windows, log files are in the "log" folder under the Agent installation path. The default path is usually "C:\Program Files (x86)\Networkbench.COM\NetCore Profiler".

  • On Linux, the log file path depends on installation permissions.

    • Root installation: The path is "/var/log/tingyun/".
    • Non-root installation: The path is "/<installation_path>/log/" specified by the user.

Normally, there should not be keywords like Error or Critical in the logs.

By default, the log level is Info and audit mode is off, so the amount of information is relatively small.

You can increase the log level to debug and enable audit mode to output more log information for troubleshooting.

Troubleshooting Installation Issues​

Please confirm that the following files exist in the installation directory.

Windows​

  • tingyun_profiler.dll
  • TingYun.dll
  • TingYun.ini
  • TingYun.json

Linux​

  • tingyun_profiler.so
  • TingYun.dll
  • TingYun.ini
  • TingYun.json

Installation Successful but No Data​

  1. After the initial installation, it may take some time to see data, usually 5 minutes or longer. Please wait a while.
  2. Some users may have browser cache issues. Even if there is data, you may not see it without a forced refresh. Please try clearing the cache, forcing a refresh, or using a different browser.
  3. After the Agent is installed, monitoring must be enabled, otherwise the Agent will not take effect.
  4. Please confirm whether the license key is correct.
  5. Please confirm whether there are user requests to the web server. The Agent's data is based on HTTP requests. If there are no requests, there will be no performance data. If there are no user requests, please use a browser to access the application and check the report again after 5 minutes.