FAQ

Updated at:

This topic describes common issues with Continuous Profiling.

No data on the Continuous Profiling page

  • This issue occurs if you have not enabled the CPU or memory profiling features for any application in the selected region.

    Go to the Continuous Profiling Settings section on the Application Settings > Custom Settings page. Enable the main switch and configure Real-time Effective IP or Real-time Effective CIDR Block. After you save the settings, wait one to two minutes, then check for the data again.

    As needed, enable the CPU Hotspots, Memory Hotspots, or Code Hotspots sub-switches. Confirm the sampling parameters and click Save.

  • The application instance's IP address is outside the effective CIDR block.

Changes in data and storage costs

Your data volume may change for the following reasons:

  • It adds new capabilities, such as multi-instance aggregate queries, thread-level analysis, and intelligent flame graph interpretation powered by Copilot.

  • The storage architecture has changed. To let you reuse your profiling data, it is now stored in Log Service (SLS) under your account instead of the built-in OSS. The data is stored in an SLS Project named proj-xtrace-<encode>-<region-id> and an SLS Logstore named logstore-profiling. This migration can change the total amount of stored data.

The .no_Java_frame item in flame graphs

This typically occurs when you use an Alpine base image. To reduce its size, the Alpine base image removes JDK debug symbols. As a result, the method stack for C++ threads within the JDK cannot resolve function names, and they appear as .no_Java_frame. These method stacks usually contain details for non-Java threads, such as the VM Thread or a JIT compiler thread. If .no_Java_frame represents a small portion of the profile, you can safely ignore it and focus on analyzing other Java method stacks. However, if .no_Java_frame accounts for a large portion, either install debug symbols for the JDK in your base image or use a non-Alpine base image. Note that some JDK versions do not have corresponding debug symbol packages, which may prevent the installation from succeeding.

The other item in flame graphs

Seeing an other item in a flame graph is normal. The Continuous Profiling feature simplifies the flame graph by consolidating nodes. The feature groups less significant nodes into the other item. This process does not affect overall troubleshooting.

Data query time range

Continuous Profiling data is retained for 7 days.