The measured gap: the scan found 599 pages, 244 image assets, 59 HTML tables and 450 table rows. The published chart screenshots use Grafana-style grids and a green/yellow/blue palette, while the site’s brand primary is purple (#621773).
This gallery is the buildable chart set: benchmark tables plus the clearest published monitoring figures. Covers, diagrams, logos and UI screenshots are catalogued in scan/inventory.csv but are not counted as charts.
Benchmarking Kubernetes log collectors — max throughput
bar · site-table● max throughput
exact · visualized from a published HTML table · Exact visualization of the published benchmark table; horizontal bars keep the collector names readable. ·
source ↗ Temporal Envelope vs Prophet — average fit
grouped-bar · site-table● Prophet● Temporal Envelope
exact · visualized from a published HTML table · Exact visualization of the published univariate-model table. ·
source ↗ VictoriaMetrics and Mimir — total CPU used
line · grafana-light● mimir● victoriametrics
traced/estimated from the published figure · Traced from the published Grafana panel; the dense series preserve the printed 20.3/24.1 and 12.1/13.8 ranges. ·
source ↗ Scraping agents — CPU
bar · site-table● CPU
exact · visualized from a published HTML table · Exact visualization of the published comparison table. ·
source ↗ sync.Map vs map + RWMutex — benchmark cost
grouped-bar · site-table● map + RWMutex● sync.Map
exact · visualized from a published HTML table · Exact visualization of the published ns/op table. ·
source ↗ Benchmarking Kubernetes log collectors — CPU
bar · site-table● CPU
exact · visualized from a published HTML table · Exact visualization of the published benchmark table. ·
source ↗ Temporal Envelope vs Prophet — average inference
grouped-bar · site-table● Prophet● Temporal Envelope
exact · visualized from a published HTML table · Exact visualization of the published univariate-model table. ·
source ↗ Disk space used — Mimir vs VictoriaMetrics
line · grafana-light● mimir● victoriametrics
traced/estimated from the published figure · Traced from the published Grafana disk-space panel; the rising sawtooth and stable VictoriaMetrics line preserve the published comparison. ·
source ↗ Scraping agents — memory
bar · site-table● memory
exact · visualized from a published HTML table · Exact visualization of the published comparison table. ·
source ↗ Grafana Mimir — resource allocation by component
grouped-bar · site-table● CPU● Mem
exact · visualized from a published HTML table · Exact visualization of the published Mimir deployment table. ·
source ↗ Benchmarking Kubernetes log collectors — memory
bar · site-table● memory
exact · visualized from a published HTML table · Exact visualization of the published benchmark table. ·
source ↗ VictoriaMetrics on ARM — CPU cores used
line · grafana-dark● vm-arm-nocgo● vm-arm● vm-x86
traced/estimated from the published figure · Estimated from the published dark Grafana panel; the three dense series preserve its range and overlap. ·
source ↗ VictoriaMetrics cluster — resource allocation by component
grouped-bar · site-table● CPU● Mem
exact · visualized from a published HTML table · Exact visualization of the published VictoriaMetrics deployment table. ·
source ↗ Prometheus vs VictoriaMetrics — resource use as % of baseline
bar · site-table● VictoriaMetrics
exact · visualized from a published HTML table · Exact visualization of the published comparison table; each value is VictoriaMetrics divided by Prometheus. ·
source ↗