Expand description
Per-query tracing instrumentation shared by all drivers.
Every driver emits one event per physical database operation through
QueryLog, so all backends produce the same shape: target
toasty::query at DEBUG (escalated to WARN past the configured
slow-statement threshold), with the statement text or operation name,
elapsed time, row count, and outcome. Field names follow the
OpenTelemetry database semantic conventions (the two-segment forms —
db.system, db.statement — since tracing macros reject field names
with more than two dot-separated segments).
Structs§
- Query
Log - Measures one in-flight database operation and emits the
toasty::queryevent when finished. - Query
LogConfig - Configuration for the per-query
toasty::querytracing event.
Constants§
- TARGET
- The tracing target of the per-query event, shared by all drivers.