feat(instrumentation,telemetry): Incorporate thread pool telemetry #419
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rabbitstack
force-pushed
the
threadpool-provider
branch
from
87ffd74 to
f4b357c
Compare
The thread pool telemetry is captured from the dedicated thread pool provider. Presently, we collect three different event types including the call stacks. More specifically, SubmitThreadpoolWork, SubmitThreadpoolCallback, and SetThreadpoolTimer events. Additionally, the callback addresses are symbolized to derive to function name, and when the callback is the ZwContinue or RtlCaputreContext function call, we also try to decode the CONTEXT structure and symbolize the instruction pointer address.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this PR / why it is needed?
The thread pool telemetry is captured from the dedicated thread pool provider. Presently, we collect three different event types including the call stacks.
More specifically,
SubmitThreadpoolWork,SubmitThreadpoolCallback, andSetThreadpoolTimerevents.Additionally, the callback addresses are symbolized to derive to function name, and when the callback is the
ZwContinueorRtlCaptureContextfunction call, we also try to decode the CONTEXT structure and symbolize the instruction pointer address.What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area instrumentation
/area telemetry
Special notes for the reviewer
Does this PR introduce a user-facing change?
Yes, the new section in the docs should be prepared to describe thread pool events.