Support update feedback on Business plugins

This post is to provide feedback for the support update regarding the Business Text/Chart/Table plugins created by Volkov Labs.

We run shift-based manufacturing dashboards — equipment efficiency, downtime root-cause, production comparison, material traceability. The things we built below are impossible in stock Grafana and are the reason we depend on the Business plugins. Each is a standard analytics pattern that core panels don’t cover.

Disclaimer: written by AI after analysing our dashboards, with human review afterwards.

1. Multi-level drilldown with a breadcrumb trail (Business Text)

  • Click a bar → navigate to the next dashboard down (efficiency → line → machine → reason), carrying the active filters and time range.
  • A breadcrumb panel (reused unchanged on every dashboard) shows the trail: Overview › Line 4 › Machine 12 › Unplanned downtime.
  • Each crumb restores the exact prior state — variables and time range, relative ranges kept relative.

Stock data links can jump between dashboards, but there’s no drill stack, no breadcrumb, and no “return to exactly where I was.” Operators navigate root-cause paths dozens of times a shift; without the trail they get lost.

2. Pareto chart (Business Charts)

  • Bars = downtime share per reason (left axis), sorted descending.
  • Cumulative % line on a second right-hand axis — the 80/20 read.
  • Bars are clickable and drill into that reason.

Pareto is the prioritisation tool for downtime, and stock Grafana has no dual-axis bar+cumulative-line combo with a clickable drilldown — you’d get two disconnected panels and no interaction.

3. Waterfall / bridge chart (Business Charts)

  • A running-total bridge across the efficiency components (planned, unplanned, speed loss, quality loss, operating time), always showing all categories, sorted by size.
  • Segments are clickable and drill into the matching detail dashboard.

There is no waterfall panel in core Grafana at all, yet this is the one view that shows where efficiency is lost as an additive breakdown.

4. Two datasets side by side, independent time ranges (Business Text + panels)

  • Build two comparison “sets,” each with its own date range and its own machine/material/entry/sequence selection.
  • Selections write to dashboard variables; queries use those windows instead of the global time picker, so both sets render together for direct comparison.

A Grafana dashboard has one global time range, so comparing yesterday’s run against last month’s — different windows, same axes — is simply not possible with stock panels. This breaks that limit.

5. Shared, database-driven landing page for every organisation (Business Text)

  • A single landing panel renders a sectioned menu of dashboard buttons (with icons), built entirely from a query — not hand-authored HTML.
  • The menu config lives in the database, so one provisioned panel serves every organisation and each sees the sections and links meant for it.
  • Enable/disable a section or link, or reorder the menu, by editing data — no dashboard edits, no re-provisioning.

Stock Grafana has no configurable home/landing page beyond pinning one static dashboard. Driving the menu from data lets us maintain one shared entry point across many organisations centrally, instead of copying and hand-editing a dashboard per organisation.

6. Material-flow (Sankey) diagram with traceability (Business Charts)

  • A flow diagram where nodes are lots/sublots at each process stage and links are material flow weighted by quantity — colour-coded by operation and by stage.
  • Click a link and it locks the full trajectory: every lot upstream and downstream of that flow is highlighted and everything else dims — answering “where did this material come from and where did it go” in one click.
  • Click a node to set a variable that re-drives a linked detail table below; shift-click a link for a secondary drill.

Core Grafana’s node graph is force-directed and unweighted — there is no Sankey or flow panel at all, so quantity-weighted material flow across stages can’t be shown natively. The trajectory lock and click-to-set-variable are, again, interaction core panels don’t offer.

7. Diagram generated from arbitrary data (Business Text)

  • A query returns diagram markup (Mermaid text) built from whatever data model we point it at — entity definitions and their relationships — and the panel renders it as a live diagram, with pan and zoom.
  • The diagram shape is data-driven: change the underlying records and the rendered diagram changes, with no manual drawing.

Core Grafana can’t turn query results into a relationship/flow diagram. This lets any structured data — model definitions, dependencies, hierarchies — become an auto-generated, always-current diagram instead of a picture someone maintains by hand.

8. Hierarchical data grid with subtotals (Business Table)

  • Rows group into an expandable tree — shift, then machine, then production run — with quantity columns rolled up as subtotals at each group level.
  • Key columns are frozen (pinned left/right) so identifiers stay visible while scrolling across dozens of measurement columns.
  • Target columns are colour-coded against their limits (in-spec vs out-of-spec cells), with per-column sort and filter.
  • A column manager lets each user show, hide, and reorder columns, and their layout is remembered; the whole grid exports to file.

Grafana’s core table is flat: no row grouping, no subtotals, no frozen columns, and no per-user column layout. For a wide record set that operators read top-down (shift → machine → run) this is the difference between a usable grid and an unreadable wall of columns.

Overview

Pattern Stock Grafana With these plugins
Drilldown + breadcrumb + state restore Data links only, no stack or return Navigation stack + clickable trail
Pareto (bars + cumulative line + drill) Not available Dual-axis, clickable
Waterfall / bridge No panel exists Additive breakdown
Two windows compared side by side One global time range Per-dataset time ranges
Shared, data-driven landing page Pin one static dashboard Menu built from a query, one panel for all organisations
Material-flow / Sankey with traceability Force-directed node graph only, no Sankey Weighted flow + upstream/downstream trajectory lock
Diagram generated from query data Not available Data-driven Mermaid diagram, pan/zoom
Hierarchical table with subtotals Flat table only Grouping tree, frozen columns, per-user layout

Happy to share redacted examples of any of the above.

Thanks for putting this together as it shows the actual workflows that would be difficult to recreate with stock Grafana today.

These are about missing chart types , interaction patterns and operator workflows →
breadcrumb based drilldowns with state restoration, independent comparison windows, data driven navigation, Sankey based traceability, and hierarchical tables.
Those are capabilities that go beyond visualization alone.

Since you’ve already mentioned you’re happy to share redacted examples, a few screenshots of the breadcrumb navigation, Pareto drilldown, Sankey traceability, and hierarchical table would make this feedback even stronger. They would give the maintainers concrete references when evaluating future support or deciding which capabilities should eventually have first class alternatives.

This is very useful post thank you. So do you have a question or is this just informational?

Grafana Labs could encourage pro developers (those who make plugins full-time) to stay around and prevent their impact from becoming legacy.

Volkov lab’s features are considered essential by many. This functionality wasn’t developed in the core because the team can’t spend the same amount of time on all directions as independent developers can. And for some compatibility matters, of course.

To incentivize pro developers, a marketplace platform could also be used to store paid extentions for the OSS plugins.

For now marketplace is designated for sole proprietary plugins, while Grafana team supports Business plugins on their best efforts, spending time on features they didn’t own.

And I personally wouldn’t publish full-proprietary plugins on the marketplace because of a small coverage and adoption… open source is in our hearts!

What stops me from having both an OSS plugin and a commercial subscription with Grafana for publishing the extended version? Well, I provide some generic Node graph and Geomap functionality that is ahead of the official.

Just as Volkov labs had unique tables and external JS treatment.

Some pro plugins are not a bridge to vendored solutions. So probably they aren’t really eligible for commercial subscription? They cover up areas where official Grafana plugins are temporarily behind.