-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(profiling) add global profile context while profiler is running #12394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comments don't block here, let's go with this
trace: { | ||
data: expect.objectContaining({ | ||
['thread.id']: expect.any(String), | ||
['thread.name']: expect.any(String), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should add a test to validate the isMainThread
behaviour
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do
@JonasBa could you also add a PR description? |
Yup, will clean it up. Sorry about that |
Attach profile context to events while a profiler is active and assign thread id and name to the trace context.
This will be required by the profiling API so that we can figure out the links between spans and profiles. In the future (span streaming), tid and thread name will be assigned to each span