# Mosaic Observability Architecture

Mosaic receives OTLP-compatible telemetry, classifies events by operational value, and routes them across Datadog, OpenObserve, and Cloudflare R2.

## Routing contract

- WARN, ERROR, and CRITICAL stay Datadog-visible by default for monitors, Watchdog-style workflows, saved views, dashboards, and incident response.
- INFO and DEBUG are context-first signals. They are written to OpenObserve and R2 unless incident state, customer impact, or trace context promotes them.
- Raw payloads are retained in R2 for replay and vendor rehydration.
- Correlation keys are preserved across destinations: trace_id, span_id, service.name, customer.name, tenant.id, transaction_id, and deployment.environment.

## Failure behavior

Mosaic fails open to Datadog. If the orchestration path is unavailable, all severities should continue to reach Datadog before optimization resumes.