Module protocol 

Telemetry protocol types and message definitions.

Submodule split

The base module defines the main message definitions, generic over how they actually store their data. The transient and owned modules expose type aliases for the base definitions with specific data storage families. The transient data is created with references and thread-local data to avoid copying data when recording log events, this is what gets passed in to a crate::collector::Export implementor. The owned data uses heap allocation to allow passing the data around in-memory or across processes as needed.

Serialization

Both transient and owned types implement serde::Serialize, the owned types also implement serde::Deserialize; the types from both modules are compatible, so you can directly serialize a transient::LogMessage without any allocations then deserialize that as an owned::LogMessage.

Modules

base

Core protocol type definitions and storage family trait.

ownedalloc

Type aliases for owned/sendable usage (IPC, serialization).

transient

Type aliases for transient usage (with format_args! support).