Dave Grochowski e94b9aeda0 feat(tracing): add datastore tracing plumbing (#2760) ...

Configure a dedicated datastore tracing target on the OTLP layer while
preserving explicit logging filters and avoiding span overhead when OTLP
is disabled.

This is in preparation for adding trace spans for datastores used in
Buzz

## Update — 2026-07-27

- Export HTTP requests as `INFO` server spans under `buzz_relay`,
preserving request parentage for datastore spans.
- Configure OTEL span filtering independently with `BUZZ_OTEL_FILTER`,
so `RUST_LOG` changes cannot break trace topology.
- Verify exported HTTP and datastore spans share a trace ID and have the
expected parent/child relationship.

Co-authored-by: Amp <amp@ampcode.com>

2026-07-27 23:32:42 -04:00

..

examples

mesh: upgrade runtime, enforce membership, add shared compute provider (#1656)

2026-07-15 10:10:29 -04:00

src

feat(tracing): add datastore tracing plumbing (#2760)

2026-07-27 23:32:42 -04:00

Cargo.toml

feat(tracing): add datastore tracing plumbing (#2760)

2026-07-27 23:32:42 -04:00

CHANGELOG.md

chore(release): release Buzz Relay version 0.2.0 (#1728)

2026-07-10 16:43:23 -04:00