`usdt`

Dust your Rust with USDT probes.

Overview

usdt exposes statically-defined DTrace probes to Rust code. Users write a provider definition, in either the D language or directly in Rust code. The probes of the provider can then be compiled into Rust code that fire the probes. These are visible via the dtrace command-line tool.

There are three mechanisms for converting the D probe definitions into Rust.

A build.rs script
A function-like procedural macro, usdt::dtrace_provider.
An attribute macro, usdt::provider.

The generated code is the same in all cases, though the third provides a bit more flexibility than the first two. See below for more details, but briefly, the third form supports probe arguments of any type that implement serde::Seralize. These different versions are shown in the crates probe-test-{build,macro,attr} respectively.

Note: This crate uses inline assembly to work its magic. As such a nightly Rust toolchain is required, and the functionality is hidden behind the "asm" feature flag. A nightly toolchain can be installed with rustup toolchain install nightly. See the notes for a discussion.

Example

The probe-test-build binary crate in this package implements a complete example, using the build-time code generation.

The starting point is a D script, called "test.d". It looks like:

provider my_provider {
	probe start_work(uint8_t);
	probe stop_work(char*, uint8_t);
};

This script defines a single provider, test, with two probes, start and stop, with a different set of arguments. (Numeric primitive types and &strs are currently supported.)

This provider definition must be converted into Rust code, which can be done in a simple build script:

use usdt::Builder;

fn main() {
	Builder::new("test.d").build().unwrap();
}

This generates a file in the directory OUT_DIR which contains the generated Rust macros that fire the probes. Unless it is changed, this file is named the same as the provider definition file, so test.rs in this case.

Using the probes in Rust code looks like the following, which is in probe-test-build/src/main.rs.

//! An example using the `usdt` crate, generating the probes via a build script.
#![feature(asm)]
#![cfg_attr(target_os = "macos", feature(asm_sym))]

use std::thread::sleep;
use std::time::Duration;

use usdt::register_probes;

// Include the Rust implementation generated by the build script.
include!(concat!(env!("OUT_DIR"), "/test.rs"));

fn main() {
    let duration = Duration::from_secs(1);
    let mut counter: u8 = 0;

    // NOTE: One _must_ call this function in order to actually register the probes with DTrace.
    // Without this, it won't be possible to list, enable, or see the probes via `dtrace(1)`.
    register_probes().unwrap();

    loop {
        // Call the "start_work" probe which accepts a u8.
        my_provider::start_work!(|| (counter));

        // Do some work.
        sleep(duration);

        // Call the "stop_work" probe, which accepts a &str and a u8.
        my_provider::stop_work!(|| ("the probe has fired", counter));

        counter = counter.wrapping_add(1);
    }
}

Note that the #![feature(asm)] attribute is required. As of Rust 1.58.0-nightly (2021-10-29), the asm_sym feature is required on macOS, so it may be placed in a call to cfg_attr, or included in any case. If you're developing a library, this is an unfortunate Rubicon -- you must choose to support compilers before that version or after, but there is no method by which compilers before and after may be supported.

One can also see that the Rust code is included directly using the include! macro. The probe definitions are converted into Rust macros, in a module named by the provider, and with macro named by the probe. In our case, the the first probe is converted into a macro my_provider::start_work!.

IMPORTANT: It's important to note that the application must call usdt::register_probes() in order to actually register the probe points with DTrace. Failing to do this will not impact the application's functionality, but it will be impossible to list, enable, or otherwise see the probes with the dtrace(1) tool without this.

We can see that this is hooked up with DTrace by running the example and listing the expected probes by name.

$ cargo +nightly run --features asm

And in another terminal, list the matching probes with:

$ sudo dtrace -l -n my_provider*:::
   ID   PROVIDER            MODULE                          FUNCTION NAME
 2865  test14314  probe-test-build _ZN16probe_test_build4main17h906db832bb52ab01E [probe_test_build::main::h906db832bb52ab01] start_work
 2866  test14314  probe-test-build _ZN16probe_test_build4main17h906db832bb52ab01E [probe_test_build::main::h906db832bb52ab01] stop_work

Probe arguments

One can see that the probe macros are called with closures, rather than with the probe arguments directly. This has two purposes.

First, it indicates that the probe arguments may not be evaluated. DTrace generates "is-enabled" probes for defined probe, which is a simple way to check if the probe has currently been enabled. The arguments are only unpacked if the probe is enabled, and so users must not rely on side-effects. The closure helps indicate this.

The second point of this is efficiency. Again, the arguments are not evaluated if the probe is not enabled. The closure is only evaluated internally after the probe is verified to be enabled, which avoid the unnecessary work of argument marshalling if the probe is disabled.

Procedural macro version

The procedural macro version of this crate can be seen in the probe-test-macro example, which is nearly identical to the above example. However, there is no build.rs script, so in place of the include! macro, one finds the procedural macro:

dtrace_provider!("test.d");

This macro generates the same macros as seen above, but does at the time the source itself is compiled. This may be easier for some use cases, as there is no build script. However, procedural macros have downsides. It can be difficult to understand their internals, especially when things fail. Additionally, the macro is run on every compile, even if the provider definition is unchanged. This may be negligible for small provider definitions, but users may see a noticeable increase in compile times when many probes are defined.

Serializable types

As described above, the three forms of defining a provider a nearly equivalent. The only distinction is in the support of types implementing serde::Serialize. This uses DTrace's JSON functionality -- Any serializable type is serialized to JSON with serde_json::to_string(), and the string may be unpacked and inspected in DTrace scripts with the json function. For example, imagine we have the type:

#[derive(serde::Serialize)]
pub struct Arg {
    val: u8,
    data: Vec<String>,
}

and a probe definition:

#[usdt::provider]
mod my_provider {
    use crate::Arg;
    fn my_probe(_: &Arg) {}
}

Values of type Arg may be used in the generated probe macros. In a DTrace script, one can look at the data in the argument like:

dtrace -n 'my_probe* { printf("%s", json(copyinstr(arg0), "ok.val")); }' # prints `Arg::val`.

The json function also supports nested objects and array indexing, so one could also do:

dtrace -n 'my_probe* { printf("%s", json(copyinstr(arg0), "ok.data[0]")); }' # prints `Arg::data[0]`.

See the probe-test-attr example for more details and usage.

Serialization is fallible

Note that in the above examples, the first key of the JSON blob being accessed is "ok". This is because the serde_json::to_string function is fallible, returning a Result. This is mapped into JSON in a natural way:

Ok(_) => {"ok": _}
Err(_) => {"err": _}

In the error case, the Error returned is formatted using its Display implementation. This isn't an academic concern. It's quite easy to build types that successfully compile, and yet fail to serialize at runtime, even with types that #[derive(Serialize)]. See this issue for details.

A note about registration

Note that the usdt::register_probes() function is called at the top of main in the above example. This method is required to actually register the probes with the DTrace kernel module. This presents a quandary for library developers who wish to instrument their code, as consumers of their library may forget to (or choose not to) call this function. There are potential workarounds to this problem (init-sections, other magic), but each comes with significant tradeoffs. As such the current recommendation is:

Library developers are encouraged to re-export the usdt::register_probes (or a function calling it), and document to their users that this function should be called to guarantee that probes are registered.

Notes

The usdt crate requires a nightly toolchain, as it relies on the currently-unstable inline asm feature. However, the crate contains an empty, no-op implementation, which generates all the same probe macros, but with empty bodies. This may be selected by passing the --no-default-features flag when building the crate, or by using default-features = false in the [dependencies] table of one's Cargo.toml.

Library developers may use usdt as an optional dependency, gated by a feature, for example named usdt-probes or similar. This feature would imply the usdt/asm feature, but the usdt crate could be used with the no-op implementation by default. For example, your Cargo.toml might contain

[dependencies]
usdt = { version = "*", optional = true, default-features = false }

# ... later

[features]
usdt-probes = ["usdt/asm"]

This allows users to opt into probes if they're willing to accept a nightly toolchain.

The Rust `asm` feature

Recall from the example that the usdt crate relies on inline asm, which is not yet a stable Rust feature. This means that the code calling the generated probe macros must be in a module where the asm! macro can be used, i.e., where the feature(asm) configuration directive is applicable.

Toolchain versions and the `asm_sym` feature

In addition, the asm feature was recently broken out into several more fine-grained features. Though it's great that inline assembly is being stabilized, a downside of this that an additional feature flag is required on macOS platforms, asm_sym. This can be included just on that platform, e.g., with #![cfg_attr(target_os = "macos", feature(asm_sym))], or unconditionally on all platforms.

The addition of this new feature presents an unfortunate problem. It is no longer possible to compile the usdt crate (or any crate defining probes) with a toolchain from before that feature was added and after its addition. In the former case, we'd get errors about an unknown feature should we include the asm_sym feature, and we'd get errors about functionality behind a feature gate from later compilers should we omit the feature.

usdt-impl 0.3.1

`usdt`

Overview

Example

Probe arguments

Procedural macro version

Serializable types

Serialization is fallible

A note about registration

Notes

The Rust `asm` feature

Toolchain versions and the `asm_sym` feature

References

usdt-impl 0.3.1

usdt

Overview

Example

Probe arguments

Procedural macro version

Serializable types

Serialization is fallible

A note about registration

Notes

The Rust asm feature

Toolchain versions and the asm_sym feature

References

`usdt`

The Rust `asm` feature

Toolchain versions and the `asm_sym` feature