Guides

Start with local OpenTelemetry, investigate bounded evidence, then add an authored browser check when a concrete flow needs direct verification.

01Using the monitoring CLIStart the collector, query services, traces, and logs, and run audits.→02Configuring the collectorMonitor host, port, database path, and retention via flags, env vars, or config files.→03Collect your first tracePoint an existing OpenTelemetry exporter at the local collector and query it.→

Active verification guides

• Observe, investigate, verify explains where passive telemetry stops and active flow evidence starts.
• Run browser checks with the CLI covers the supported runner.
• CI integration records repeatable flow evidence and optional control-plane runs.
• Production-target browser checks defines the identity, side-effect, cleanup, and artifact safeguards required in production.
• Browser Harness documents the lower-level controlled browser boundary used by the runner.