Expand description
The Venator “engine” provides the functionality that powers the Venator app. It is able to store, index, and query the spans, events, and related entities. Do note that this crate does not have support for listening for events and spans.
Although the Venator application and tracing library are considered stable, this crate isn’t. It is still built and somewhat documented so that someone could use it on its own.
Modules§
- engine
- The actual engine that handles inserts and queries.
- filter
- Types and functions for handling filters.
- storage
- Traits and implementations for storing data in the engine.
Structs§
- Ancestor
- Attribute
- Composed
Event - Composed
Span - Create
Span Event - Dataset
Stats - Delete
Filter - Delete
Metrics - Engine
Status - Event
- Level
Convert Error - NewClose
Span Event - NewCreate
Span Event - NewEnter
Span Event - NewEvent
- NewFollows
Span Event - NewResource
- NewSpan
Event - NewUpdate
Span Event - Resource
- Span
- Span
Event - Update
Span Event
Enums§
- Attribute
Source - Full
Span Id - Level
- NewSpan
Event Kind - Source
Kind - Span
Event Kind - Subscription
Response - Trace
Root - Value
- Value
Operator
Type Aliases§
- Event
Key - This is the internal type used to identify events. The value is the unique timestamp from when the event was created.
- Instance
Id - This is the external type used to identity a tracing instance. This is generated client-side and should be random to make it unique.
- Resource
Key - This is the internal type used to identify resources. The value is the unique timestamp from when the resource was created.
- Span
Event Key - This is the internal type used to identify span eventss. The value is the semi-unique timestamp from when the span event was created. “Semi-unique” because the “create” event shares a timestamp with the span it creates.
- SpanId
- This is the external type used to identity a span. This is generated client- side and is either unique within that instance (for tracing data) or unique within that trace (for opentelemetry data).
- SpanKey
- This is the internal type used to identify spans. The value is the unique timestamp from when the span was created.
- Subscription
Id - Timestamp
- TraceId