#user-events #trace-points #trace-logging #logging #trace #scripting-language #eventheader

no-std eventheader_dynamic

Rust API for runtime-specified eventheader-encoded Linux Tracepoints via user_events

9 releases

0.4.0 Apr 12, 2024
0.3.5 Feb 27, 2024
0.3.4 Nov 27, 2023
0.3.3 Aug 23, 2023
0.1.0 May 9, 2023

#412 in Profiling

Download history 21/week @ 2024-07-22 86/week @ 2024-07-29 43/week @ 2024-08-26 3/week @ 2024-09-02 116/week @ 2024-09-09 20/week @ 2024-09-16 34/week @ 2024-09-23 94/week @ 2024-09-30 1/week @ 2024-10-07 32/week @ 2024-10-14 19/week @ 2024-10-21 13/week @ 2024-10-28 13/week @ 2024-11-04

77 downloads per month
Used in 2 crates

MIT license

200KB
2K SLoC

EventHeader for Rust

Crates.io Documentation MIT licensed Build Status maintenance status

The eventheader_dynamic crate provides a flexible way to log EventHeader-encoded Tracepoints via the Linux user_events system. The events can be generated and collected on Linux 6.4 or later (requires the user_events kernel feature to be enabled, the tracefs or debugfs filesystem to be mounted, and appropriate permissions configured for the /sys/kernel/.../tracing/user_events_data file).

This "dynamic" implementation is more flexible than the implementation in the eventheader crate. For example, it supports runtime-defined schema and can easily log arrays of strings. However, it is harder to use, it has higher runtime costs, and it depends on the alloc crate. This dynamic implementation is intended for use only when the set of events cannot be determined at compile-time. For example, eventheader_dynamic might be used to implement a middle-layer library providing tracing support to a scripting language like JavaScript or Python. In other cases, use the eventheader crate instead of this crate.

Dependencies