oma-observability

1# Observability Agent - Intent-based Router
2 
3## Scheduling
4 
5### Goal
6Route, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics.
7 
8### Intent signature
9- User asks for observability, telemetry, OTel, metrics, logs, traces, profiles, SLOs, RUM, APM, incident forensics, trace propagation, transport tuning, or observability-as-code.
10- User needs vendor/category routing or observability architecture instead of a single vendor's already-covered setup.
11 
12### When to use
13- Setting up an observability pipeline (OTel SDK + Collector + vendor backend)
14- Designing traceability across service and domain boundaries (W3C propagators, baggage, multi-tenant, multi-cloud)
15- Tuning transport layer (UDP/MTU, OTLP gRPC vs HTTP, Collector DaemonSet vs sidecar topology)
16- Running incident forensics (6-dimension localization: code / service / layer / host / region / infra)
17- Selecting a vendor category (OSS full-stack vs commercial SaaS vs high-cardinality specialist vs profiling specialist)
18- Implementing observability-as-code (Grafana Jsonnet dashboards, PrometheusRule CRD, OpenSLO YAML, SLO burn-rate alerts)
19- Meta-observability (pipeline self-health, clock skew detection, cardinality guardrails, retention matrix)
20- Covering the MELT+P signal set: metrics, logs, traces, profiles (OTEP 0239), cost (OpenCost), audit (SOC2/ISO), privacy (GDPR/PIPA)
21…