If Mosaic is unavailable, telemetry still reaches Datadog.
Mosaic OS module
Self-driving orchestration for observability
Mosaic keeps SRE workflows intact while dynamically deciding what stays hot in Datadog, what fans out to OpenObserve, and what lands in R2 for replay.
WARN, ERROR, and CRITICAL remain monitor-safe.
Lower urgency context goes to OpenObserve and R2.
How it works
1. ReceiveOTLP-compatible logs, metrics, and traces.
2. ClassifySeverity, customer impact, service, trace, and incident state.
3. ProtectKeep monitors, dashboards, saved views, and trace pivots usable.
4. RouteDatadog hot path, OpenObserve context, R2 replay archive.
5. AdaptIncident expansion and fail-open controls happen automatically.
Customer-first guardrails
Optimization never outranks the SRE workflow.
- Monitor-safe hot severities stay Datadog-visible.
- Correlation keys survive across every plane.
- Incident mode expands the Datadog hot path automatically.
- Raw telemetry remains replayable from R2.
- Agents can inspect policy before changing routing.
Agent-readable surface
Humans can read it. Agents can build with it.
Use /llms.txt, /openapi.json, and /api/observability/manifest to understand capabilities and generate a connector bundle.
Connector generator
Generate a starter tool for Datadog, OpenObserve, and R2.
This public page uses placeholders for secrets. It does not store credentials.
Generate a bundle to preview .env, compose, policy, MCP, and agent instructions.