How to enable Trace Profiling

Prerequisites

  • This feature only works on the Linux kernel 4.17 or newer.
  • We recommend that users install SkyWalking with the backend and its Java agent before enabling trace profiling for full features supported. Otherwise, only the “thread profiling” is enabled and you will see the prompt “No skywalking is installed”.

Instructions

If you have not installed the Kindling agent, please do it first before you follow the instructions. See the Installation for how to install.

After you have installed the agent successfully, the function is disabled by default, and you need to manually enable it following the instructions:

  1. Determine the IP of the host node where you want to enable the function to profile the processes.
  2. The agent on each node will start a front-end web, which listens the port 9504 by default. Visit http://{YOUR_IP}:9504 to open the page.
  3. Click “Start Trace Detection” in the upper right corner. The startup process may last for 5 to 10 seconds. After the opening is successful, the button in the upper right corner will be turned on.

Notice

After enabling this function, all Java applications on the host node will be automatically installed with a kindling-java agent. The agent is used to make SkyWalking work together with Kindling and attach the async-profiler to your applications. See more details about the kindling-java agent here .

⚠️WARNING

AsyncProfiler will Crash with two different paths . If your application has started with asyncProfiler(eg. Datadog), then DO NOT enable trace profiling.

  1. Once the function is enabled, the profile data will be saved to files. You can refresh the page to view the latest data.
  2. Click the upper filter box to filter the profile results to be viewed.

Use cases

See the use cases on Use Cases . We appreciate any new cases from you. Please feel free to open an issue if you want to contribute your cases to the community.

Edit this page on GitHub
← Architecture
Overview →