heady-observability-mesh

Unify OpenTelemetry distributed tracing, Sentry, and LLM tracing by propagating a single correlation_id across Cloudflare edge, Cloud Run, and Neon, linking per-stage spans with LLM cost analytics and classified errors.

Correlation context propagation works by passing a single correlation_id from the edge through Cloud Run, Neon, Upstash, and LLM providers, ensuring end-to-end trace continuity across multi-provider pipelines.

Yes, you can track per-LLM-call cost analytics by wrapping LLM interactions with Langfuse tracing, providing token accounting and provider-cost aggregation alongside OpenTelemetry per-stage spans.

The observability mesh supports alerting by calculating phi-weighted coherence scores across latency, errors, and cost, triggering threshold-based alerts for operational visibility.

Available endpoints for operational visibility include /health for readiness checks, /trace/llm for LLM traces, /coherence for scoring, and /cost for provider-cost aggregation.

Classify Sentry errors automatically by applying CSL-based error tagging with Sacred Geometry context, enabling proactive alerting and structured error tracking across distributed traces.