the calling link is discontinuous during load test #7675
-
|
When I configure agent.sample_n_per_3_secs = 1500 and receiver-trace.default.sampleRate = 100, the calling link is discontinuous during load test. Shall I restore this parameter to agent.sample_n_per_3_secs = = - 1 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
If agent.sample_n_per_3_secs = 1500 is configured, will the same request link occur when the first service is sampled and the second service is not sampled |
Beta Was this translation helpful? Give feedback.
-
|
The source codes are there, I checked, and confirmed my statements in the morning. |
Beta Was this translation helpful? Give feedback.
-
|
After reading the source code, I feel that if the sampling rate is set, the same request link will be sampled through the first service. If the second service has reached the upper limit of 1500 within 3 seconds, it will not be sampled. Then create an IgnoredTracerContext. In this way, the same request link will be missing. I want to confirm with you that my analysis is correct. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think so. If the context exists in header, force sampling would be activated. |
Beta Was this translation helpful? Give feedback.
-
|
I see. Thank you |
Beta Was this translation helpful? Give feedback.
agent.sample_n_per_3_secs = 1500doesn't affect the sampling usually, unless MQ consumer involved. Because in that case, sampling runs first than check whether there is existing tracing context. In most RPC cases, this is not an issue.