can not query any pprof with profile_id while tracing contains profile_id #1372
-
i can record tracing in every root span like: but i can not find anything when query with those profile_id like: i am so confused, is there anyone meet the same? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
Hello @zhzure, thank you for reaching out! There are two issues that could potentially cause the described experience:
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
That's interesting. I'd like to learn a bit more about the deployment:
Unfortunately, in the current implementation presence of
Oh, I have to clarify that 10s of CPU time (active execution) not wall time (that includes e.g. IO latencies).
According to the table, pyroscope server has received samples only for the 3rd and the 6st series within the queried time range. Also, presence of |
Beta Was this translation helpful? Give feedback.
That's interesting. I'd like to learn a bit more about the deployment:
Unfortunately, in the current implementation presence of
pyroscope.profile.id
does not mean that a profile has been captured for the span but only establishes a link between profiles and traces. We added these span attributes more for convenience reasons, so that users would be able to navigate to the Pyroscope UI by link.Oh, I have to clarify that 10s of CPU time (active execution) not wall time …