feat: USDT tracing #474
Open
feat: USDT tracing #474
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
Linux perf does not understand the probes laid down by the usdt crate. This mostly makes sense, as usdt is made by oxidecomputer folks and they mainly target illumos and linux distributions with DTrace available. My assumption is that we end up with the no-action register_probes() call and hence we get no probe information. Not sure why that is but so it is.
|
Hi @aapoalas, |
Colocation of definition and code: With the attribute macro I can define the probe where it is used, only making changes to a single file and in a single language. If I used the |
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.
USDT tracing is a way for programs to statically define "points of interest" for tracing tools like DTrace, perf, bpftrace, SystemTap, and others to hook into. I've been diving into this world lately with the intention of getting better performance feedback from Nova. I now have a working Linux-based USDT system built forked from Oxide Computer's usdt crate, and this PR is then a showcase of how that can then be utilised.
Examples
Tracing constructor calls: