Cameron CordesandClaude Opus 5.5 3b3e6bdb39 feat(otel): export logs through the tracing pipeline, correlated with traces (#147) ...

Logs were a separate pipeline: env_logger in debug (never exported) and
opentelemetry-appender-log in release (exported without trace context,
so SigNoz could not link logs to traces).

- tracing-subscriber `tracing-log` feature: try_init installs LogTracer,
  so log:: records become tracing events: one console format, and
  RUST_LOG per-module directives still apply to them.
- opentelemetry-appender-tracing exports events as OTel log records when
  OTLP_OTLS_ENDPOINT is set (any build), stamped with the enclosing
  span's trace_id/span_id. A per-layer filter drops the exporter's own
  crates.
- The OTel span layer keeps only WARN/ERROR events as span events; the
  info/debug copies duplicated the correlated logs.
- Remove env_logger init in the server, init_logs, and the unused
  opentelemetry-appender-log / opentelemetry-stdout deps.
- tests/otel_log_correlation.rs pins correlation (native + bridged),
  the span-event filter, and per-module filtering of bridged records.
- Constitution 1.2.0 (Principle V logging rule), CLAUDE.md, README,
  .env.example.

Closes #147

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-29 22:56:10 -04:00

..

otel_background.rs

Tracing: root spans for background jobs, retire raw OTel spans (#142)

2026-09-29 17:02:40 -04:00

otel_db_spans.rs

Tracing: root spans for background jobs, retire raw OTel spans (#142)

2026-09-29 17:02:40 -04:00

otel_llm_spans.rs

Tracing: LLM clients + streaming spans on tracing, drop cx threading (#140)

2026-09-29 17:02:40 -04:00

otel_log_correlation.rs

feat(otel): export logs through the tracing pipeline, correlated with traces (#147)

2026-09-29 22:56:10 -04:00

otel_propagation.rs

Tracing: cargo fmt tests/otel_propagation.rs (#143)

2026-09-29 17:04:08 -04:00

otel_traceparent.rs

Tracing: DAO layer + handler spans on tracing, drop all Context params (#141)

2026-09-29 17:02:40 -04:00