Replies: 1 comment 2 replies
-
Sampling is the base of the profiling, from call stack to the matched calls. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
environment:skywalking10.1.0、java-agent9.3.0、elasticsearch7.10.2
I have found that there is currently an issue with Trace Profiling where the APIs collected in the trace are in compliance with the configuration in the task, but not all of them have been collected. Is there a problem with Trace Profiling in this situation, or is it designed in this way.
After creating the performance analysis task, the task configuration information is as follows:
Configure Dump Period



When setting the dump period for the task configuration to 10ms, according to the documentation, APIs with a duration greater than 10ms should be able to be collected by the task. However, it was found that not all interface data in the trace was collected, with a total of 4 interfaces. After the task was completed, the API interface with a response time of 15ms did not appear in the sampling trace of the task. As shown in the following figure.
Configure Min Duration Threshold



When setting the Min Duration Threshold to 100ms. API interfaces with response times of 105ms, 106ms, etc. that meet the task configuration were not collected until API response times of 120ms or larger were detected by the task's sampling tracking.
Beta Was this translation helpful? Give feedback.
All reactions