nemo-relay-plugin-observability

# Configure Observability Plugins Start with one exporter managed by the built-in Observability plugin. This is the default for reusable process configuration and the best first plugin for most users because it makes Relay's captured activity visible. Choose one proof output before layering additional telemetry destinations. Use manual subscriber or exporter APIs only when a test, script, or application needs direct control over registration names, collection windows, or flush timing. Both paths consume the same canonical event stream. ## Select The Relay Version Determine whether the application uses NeMo Relay 0.6 or 0.7 before proposing configuration or binding APIs. Prefer the installed package version, lockfile, or manifest. Ask the user when the version cannot be established; do not mix the two surfaces in one example. - **0.6** uses observability configuration version 2. OpenTelemetry and OpenInference are separate exporters with `OpenTelemetryConfig` / `OpenTelemetrySubscriber` and `OpenInferenceConfig` / `OpenInferenceSubscriber`. - **0.7** uses observability configuration version 3. One typed OpenTelemetry exporter provides `full`, `gen_ai`, and `openinference` projections. ## Choose The Output Select the output that best matches the user's immediate inspection target: - **Console or custom event handling** Use a manual subscriber for short-lived in-process inspection. - **Raw canonical lifecycle events** Use ATOF JSONL; read `references/atof.md`...