Replies: 3 comments 3 replies
-
|
The left list is trace segments, not a trace or 3 traces. |
Beta Was this translation helpful? Give feedback.
-
|
Why are there 3 segments? In a single request, I only want one segment, and the first and third segments are completely identical.
…---Original---
From: "吴晟 Wu ***@***.***>
Date: Tue, Oct 3, 2023 07:07 AM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [apache/skywalking] Why are there 3 traces in one request?(Discussion #11368)
The left list is trace segments, not a trace or 3 traces.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Trace segment is determined by the agent, how to collect spans. |
Beta Was this translation helpful? Give feedback.
-
|
Look at the content within the green box in the first image. What I'm asking is why there are 3 seg (or something else) in the left-hand list. The second one in the left-hand list is generated by @trace. You mentioned that there should be at least three services, but without @trace, there are only two. How can this be explained?
…---Original---
From: "吴晟 Wu ***@***.***>
Date: Tue, Oct 3, 2023 08:07 AM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [apache/skywalking] Why are there 3 traces in one request?(Discussion #11368)
Trace segment is determined by the agent, how to collect spans.
In your screenshot, it is clearly there are 3 services involved in a request path, so at least 3 segments from 3 services.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I don't have time to explain your details. How your codes run is your env. I gave your explanation about what trace segment is. |
Beta Was this translation helpful? Give feedback.
-
|
The second part of your question had been answered here, #11367 (comment). It means trace broken. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are there 3 traces in one request?
Why does the second trace appear separately instead of being part of the local type trace chain below it?
Beta Was this translation helpful? Give feedback.
All reactions