parser failed on evidently report html with embedded drift charts error

TL;DR

Parse the report data, not the rendered page: Evidently HTML reports embed charts as scripts and data blobs, so extract the embedded JSON metrics from the report, or regenerate the metrics from the Evidently workspace instead of scraping the HTML structure. The HTML report is a rendering for humans. Its chart payloads are embedded in script blocks whose shape changes between versions, which is why structure-based parsing keeps breaking.

parser failed on evidently report html with embedded drift charts error

Use this when

• The check or run fails with this symptom: a parser fails on an Evidently report HTML file with embedded drift charts.
• You are working on an agent workflow that extracts metrics from generated Evidently HTML reports and the failure repeats on the same data or configuration.
• You need the failing rows, rule, or stage isolated before changing thresholds or code.

Not for this skill when

• A report saved as JSON by Evidently, which should be parsed directly and needs no HTML handling at all.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Open the failing report and locate where the metrics live: rendered tables or an embedded data payload. Verify: the payload location in this report version is identified
2. Extract the embedded payload and parse it as JSON. Verify: metric names and values are readable
3. Map the needed metrics, such as drift scores per column, from the payload. Verify: the extracted values match the visible report
4. Where possible, switch the pipeline to save the Evidently report as JSON alongside the HTML. Verify: future parses read the JSON directly
5. Record the Evidently version the extractor targets. Verify: a version change triggers an extractor review

Variant phrasings

parser failed evidently report html drift charts

The shorter phrasing focused on the named failure.

evidently html report embedded charts parse error

The symptom phrasing a searcher tries next.

extract metrics evidently html report fix

The variant naming the failing stage or tool directly.

Compatibility: Evidently 0.4 and later HTML and JSON report outputs

Why it happens

Evidently renders charts by embedding a data payload and plotting it in the browser. Parsers written against the page structure or against one version payload layout fail when charts, ordering, or the payload format change, even though the underlying metrics are unchanged.

Edge cases / pitfalls

• Do not screenshot or OCR the charts as a fallback for numbers that exist in the payload; the payload is exact and the chart is not.
• Embedded payloads can be large; stream or select the needed sections instead of loading the whole report into an agent context.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstWZ6lyFGNieIclCmnydMxg