// the take
Statusmap is an older Grafana panel plugin for rendering discrete status values (ok/warn/fail) as a grid over time, aimed at people tracking server or Kubernetes pod health history. It was built by Flant to fill a gap in pre-9.x Grafana, and the README itself tells you not to use it anymore.
Feature set is genuinely thorough for what it does: pagination for large row counts, discrete/spectrum/opacity color modes, configurable tooltips with clickable URL templates, and percentual bucket spans for zooming around an incident. Datasource docs are unusually specific and correct — the Prometheus section walks through the exact PromQL trick (count_values + multiply-by-status-value) needed to get discrete statuses into buckets, which most panel plugins never bother explaining.
Archived and unmaintained since 2024, and the maintainers explicitly point you at Grafana's built-in status-history and state-timeline panels as the replacement — there's no reason to adopt this over those unless you're stuck on Grafana <9. It only renders whatever buckets the datasource hands it with zero server-side aggregation, so you must pre-shape one query per status value with matching timestamps across all targets (issue #53, still open, is exactly this pain). Angular-style panel (module.html, angular event bus in util/grafana/events) rather than the React panel API Grafana has standardized on, so it'll keep getting harder to run as Grafana versions advance even if someone forks it.
We read the README, the directory tree and a key source file in September 2026. Nobody pays to be listed. How we judge →