Skip to content

can not query any pprof with profile_id while tracing contains profile_id #1372

Answered by kolesnikovae
zhzure asked this question in Q&A
Discussion options

You must be logged in to vote

That's interesting. I'd like to learn a bit more about the deployment:

  • pyroscope server version
  • go client version

dose that means my go-agent in code and pyroscope service worked just fine if i can see profile_id in trace record?

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.

i choose a request longer than 10ms,but i still got nothing

Oh, I have to clarify that 10s of CPU time (active execution) not wall time …

Replies: 3 comments 7 replies

Comment options

You must be logged in to vote
2 replies
@zhzure
Comment options

@zhzure
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
5 replies
@zhzure
Comment options

@kolesnikovae
Comment options

@zhzure
Comment options

@zhzure
Comment options

@kolesnikovae
Comment options

Answer selected by zhzure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants