Skip to content
KONIGI Patterns

Dashboards · Genres

Operational

Watched continuously. Something is happening now and someone has to act on it.

12 captures

Patterns seen in this genre 42

Captures

Newest first.

Ignition — Water Treatment / Overview
Process mimic. Equipment and values follow the process flow. Dense small-multiple layout. Repeated filter panels make their states easier to compare. Gauge and dial. Tank fill uses a bounded vertical scale. Grayscale with alerts. Green identifies running equipment throughout the diagram. Process mimic. A setting switches pump and pipe appearance between simple and realistic rendering. Semantic status color. Stopped equipment has a text label as well as a gray treatment.
Ignition · Water Treatment / Overview September 11, 2026 Ignition Perspective public demo, Water Treatment (signed out) dense · dark · desktop-web
The demo uses simulated plant data in a process diagram arranged from incoming water through treatment and storage. Values appear beside the relevant equipment. Green means running, while stopped filters are gray and explicitly labeled. This makes normal operation colorful, unlike a display that reserves color for warnings. Repeated filter panels and clear process connections help people compare equipment.
Kraken Pro — Trade / BTC-USD
Time series. Candles show opening, high, low, and closing values for each interval. Order book and depth. Buy and sell ladders show quantities with depth bars and a labeled spread. Red/green direction coloring. Asks are above the spread as well as colored red. Ratio and rate. The spread appears as both an amount and a percentage. Delta indicator. The price change includes an amount, percentage, and named period. Order book and depth. The price-increment control changes how levels are grouped.
Kraken Pro · Trade / BTC-USD September 11, 2026 Kraken Pro, signed out (public market data) dense · dark · desktop-web
The order book separates asks and bids by position as well as red and green. A labeled spread sits between them and includes both an absolute value and a percentage. Depth bars behind the rows help compare quantities that are difficult to scan as long decimal values. A price-increment control changes how orders are grouped into levels.
Netdata — Anomalies / Anomaly advisor
Anomaly band. A separate anomaly-rate chart summarizes many metrics. Empty state. The empty panel explains which action will produce results. Cross-filter. Selecting a time period reveals the contributing metrics. Explain this metric. Definitions appear directly beneath section headings. Share and embed. A report control is available above the charts.
Netdata · Anomalies / Anomaly advisor September 11, 2026 Netdata Agent, Anomaly advisor (public registry node, signed out) medium · dark · desktop-web
Netdata shows the share and count of measurements flagged as unusual in separate charts. This provides a compact overview across many metrics rather than drawing an expected range on each one. People then select a time period to see which metrics contributed. The empty detail panel explains that a selection is needed before results will appear.
  • Anomaly band A separate anomaly-rate chart summarizes many metrics.
  • Explain this metric Definitions appear directly beneath section headings.
  • Cross-filter Selecting a time period reveals the contributing metrics.
  • Empty state The empty panel explains which action will produce results.
  • Share and embed A report control is available above the charts.
Grafana — Examples / Alert List
Alert rule attached to panel. Alert names use different conventions and do not consistently identify the affected system. Alert rule attached to panel. This alert has been firing for more than seventeen days. Semantic status color. Pending is labeled separately from firing. Drill-down. Each row links back to the alert rule. Filter bar. The row states how many instances are hidden by filters.
Grafana · Examples / Alert List September 10, 2026 Grafana Play (signed out; no version string exposed) medium · dark · desktop-web
This list shows seven alerts with their states and durations. Several have been firing for days, which raises a question about whether the rules still prompt a useful response. The names use inconsistent conventions and often do not describe the affected system clearly. Pending and firing states are labeled separately, and each row links back to its rule.
Grafana — Demo / Annotations
Annotation. Frequent event markers compete with the request-rate line. Annotation. The event list provides readable timestamps and tags. Time-range picker. The selected twenty-four-hour range affects how densely markers appear. Filter bar. A tag filter is already applied to the annotations.
Grafana · Demo / Annotations September 10, 2026 Grafana Play (signed out; no version string exposed) medium · dark · desktop-web
Frequent red event markers make the request-rate line difficult to follow across this twenty-four-hour view. The tag filter is already active, so filtering alone has not reduced the crowding enough. The event list below is easier to read because it separates timestamps and tags into individual entries. This example shows why event density matters as much as recording the events.
  • Annotation Frequent event markers compete with the request-rate line.
  • Annotation The event list provides readable timestamps and tags.
  • Filter bar A tag filter is already applied to the annotations.
  • Time-range picker The selected twenty-four-hour range affects how densely markers appear.
Grafana — Examples / Logs Panel
Drill-down. The trace ID connects the log event to its request. Stacked composition. Stacked log counts show volume by level over time. Log tail. Log rows are truncated and contain timestamps in two timezones.
Grafana · Examples / Logs Panel September 10, 2026 Grafana Play (signed out; no version string exposed) medium · dark · desktop-web
A stacked volume chart sits above the individual log events, linking the overall pattern to specific lines. Each row shows a local timestamp and a UTC timestamp, but their timezones are not clearly labeled. That can make the same instant look like two different times. Expanded event details include a trace ID, providing a route to the request behind the message.
  • Stacked composition Stacked log counts show volume by level over time.
  • Log tail Log rows are truncated and contain timestamps in two timezones.
  • Drill-down The trace ID connects the log event to its request.
Grafana — Examples / Node graph panel
Service map. Nodes represent services and lines represent their connections. Semantic status color. Each node combines two values with a success/error ring. Legend and series toggle. The legend explains the measures shown inside and around nodes. Zoom and pan on time. Zoom controls help reveal nodes outside the visible panel.
Grafana · Examples / Node graph panel September 10, 2026 Grafana Play (signed out; no version string exposed) sparse · dark · desktop-web
Several service nodes extend beyond the panel’s right edge, so the full graph is not visible at once. Each node contains two values and a colored ring, with a legend explaining the measures. This adds detail but makes the map harder to scan for a single overall state. The zoom control helps reach the clipped nodes, though a clearer initial fit would make the relationships easier to inspect.
Grafana — Examples / Polystat Visualization Showcase
Host map. Touching hexagons make adjacent cells read as a group. Host map. Circles leave gaps between neighboring cells. Semantic status color. Cell fills represent OK, warning, and critical states. Ranked list. Descending order brings the highest values first. KPI tile. Label-only cells show a name and color without a numeric value.
Grafana · Examples / Polystat Visualization Showcase September 10, 2026 Grafana Play (signed out; no version string exposed) medium · dark · desktop-web
This showcase displays the same threshold-colored cells in several shapes. Hexagons touch along their edges, while circles leave gaps, changing how adjacent cells form visible groups. The choice matters when scanning many items together. Other panels demonstrate named states, sorting, and label-only cells, each emphasizing a different part of the reading.
  • Host map Touching hexagons make adjacent cells read as a group.
  • Host map Circles leave gaps between neighboring cells.
  • Semantic status color Cell fills represent OK, warning, and critical states.
  • Ranked list Descending order brings the highest values first.
  • KPI tile Label-only cells show a name and color without a numeric value.
Grafana — Examples / State timeline and Status history
Semantic status color. Both states have text labels as well as colors. Sequential and diverging scales. Separate sample marks use color for temperature rather than health. Status history. State names appear inside continuous time regions. Threshold line and region. Thresholds convert numeric values into named bands. Time series. The line chart preserves the numeric values behind the state view.
Grafana · Examples / State timeline and Status history September 10, 2026 Grafana Play (signed out; no version string exposed) medium · dark · desktop-web
This page places a state timeline above a time-series view of the same query. The timeline converts numeric ranges into named states, making the periods easier to scan. The line chart keeps the numeric variation available for closer reading. Labels inside the colored regions explain their meaning, reducing reliance on color alone.
Netdata — Metrics / System
Header KPI strip. The summary tiles use several arrangements across two rows. Sidebar and canvas. The rail organizes collected metrics into a hierarchy. Gauge and dial. Rate gauges need meaningful scale limits to make their arcs interpretable. Dashboard builder. Chart headers include controls for grouping and aggregation. Search across panels. Search helps locate a chart within the large collection. Semantic grouping. Sections follow the collector’s metric categories. Compare periods. Period comparison is configured per chart, so panels may use different settings. Freshness indicator. The header explicitly separates live and stale nodes.
Netdata · Metrics / System September 10, 2026 Netdata Agent v2.10.0-686-nightly (public registry node, signed out) dense · dark · desktop-web
The navigation reports 720 charts organized by the metrics collected from the system. The main page follows the same nested structure, giving broad coverage but little indication of which charts matter most to a particular task. Search helps navigate that volume. The header also distinguishes live and stale nodes, making missing updates visible instead of presenting every node as current.
Netdata — Metrics / System › Compute › CPU
Gauge and dial. The gauges mix bounded percentages with rates whose limits need explanation. Collapsible row. Nested headings use leading dashes to show depth. Legend and series toggle. The legend includes values and bars for the listed series. Dashboard builder. Each chart header exposes query controls. Overview then detail. The breadcrumb identifies the current section within the larger collection.
Netdata · Metrics / System › Compute › CPU September 10, 2026 Netdata Agent (public registry node, signed out) dense · dark · desktop-web
This section follows several nested levels of the generated metric hierarchy. Leading dashes indicate depth, while a breadcrumb identifies the current CPU section. Each chart includes its own grouping and aggregation controls. The Anomaly Rate option is visible but switched off, so this capture demonstrates the control rather than the resulting anomaly display.
Grafana — Linux node / fleet overview
Empty state. The chart reports No data but gives little help with the cause. Header KPI strip. Status tiles sit above the charts. Error and stale state. The red tile reports missing metrics and suggests checking configuration. Freshness indicator. The freshness tile reports No data without an update time. Data source badge. The integration version remains available while measurements are missing.
Grafana · Linux node / fleet overview September 9, 2026 Grafana Play (signed out; no version string exposed) medium · dark · desktop-web
The data source was returning no measurements when this overview was captured. A red tile says no metrics were received and suggests checking configuration. The freshness tile says No data, while another panel says No errors. Those messages need clearer distinctions: missing measurements do not establish that a system has no errors.