Documentation
¶
Overview ¶
Tracing bootstrap — this is the ONE way a Hanzo Go daemon emits spans: one call, one service name, so the console's per-product Monitoring tab (which filters by service name) lights up for this product.
Spans travel to o11y over ZAP, luxfi/trace's native transport: a JSON SpanBatch inside a ZAP envelope, read by hanzo/o11y/pkg/zapreceiver. There is no OTLP, no protobuf and no gRPC anywhere in this path — the exporter that carried them is gone from luxfi/trace, which is why this binary's module graph no longer contains google.golang.org/grpc.
Opt-in via O11Y_ENDPOINT and non-fatal in every failure mode, so this is safe to ship before a collector is live: New() does not dial, and the batch processor exports in the background, so boot never blocks on o11y.