For AI agents: the complete documentation index is available at https://mfdoctor.kevinbeier.com/llms.txt, the full documentation bundle is available at https://mfdoctor.kevinbeier.com/llms-full.txt, and this page is available as Markdown at https://mfdoctor.kevinbeier.com/observability-runtime.md.
MFDoctor
  • English
  • 2.0.0

      • Observability latest.json → mfdoctor runtime

      Module Federation Observability writes runtime reports such as .mf/observability/latest.json. MFDoctor consumes that file through the offline CLI — not by injecting a doctor agent into the browser.

      Observability Plugin  →  .mf/observability/latest.json  →  mfdoctor runtime

      Example

      After Observability has written a report (Node/SSR fileOutput, browser export, collector, or onReport handoff), correlate it with local MFDoctor project facts:

      mfdoctor check --format json
mfdoctor runtime ./.mf/observability/latest.json ".mf/doctor/**/project.json"

      Minimal form when project facts already live under .mf/doctor/**/project.json:

      mfdoctor runtime ./.mf/observability/latest.json

      Or set runtimeTrace in mfdoctor.config and omit the path on the command line. Supported report formats are terminal, JSON, and SARIF only — there is no HTML report or --ui dashboard.

      Expected inputs

      InputRole
      .mf/observability/latest.json (or another Observability export path)Runtime report from the official Observability Plugin
      .mf/doctor/**/project.json (default glob)Build/check project facts from MFDoctor

      mfdoctor runtime accepts:

      • one Observability report object;
      • an array of reports;
      • a {"report": ...} or {"reports": [...]} envelope.

      Current upstream Observability 2.5.3 reports and the legacy MFDoctor v1 shape are supported. Partial reports import as partial evidence; missing fields never count as a pass. Unknown future shapes and Observability build reports (.mf/observability/build-report.json / build-info.json) are rejected — those are build telemetry, not runtime traces.

      Prefer latest.json for the latest complete runtime report. Use events.jsonl only when you need event ordering or multiple traces; it is not the default mfdoctor runtime input.

      Not an in-browser agent

      Analysis stays post-build / CLI:

      • Do not inject MFDoctor into the page or client bundle.
      • Do not look for an HTML doctor UI or --ui flag.
      • MFDoctor never fetches URLs found in a report, never opens a browser, and never executes report contents.
      • An in-browser MFDoctor runtime agent is not planned (#33).

      For live loading failures, use the official Observability Plugin (or its export/collector path), then run mfdoctor runtime on the saved JSON.

      Optional CI step

      In CI, after a job that produces both Observability output and MFDoctor project.json files:

      mfdoctor runtime ./.mf/observability/latest.json ".mf/doctor/**/project.json" --format terminal,json

      Exit codes match the rest of the CLI: 0 pass, 1 policy fail, 2 analysis incomplete. Invalid or missing opt-in traces do not break ordinary mfdoctor check; they simply omit runtime correlation.