Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 37 ยท Dashboards and Reporting

Dashboards and Widgets

Design useful Zabbix dashboards: global, host and template dashboards, key widgets like Problems, Graph and Top hosts, filters, sharing and what to avoid.

Monitoring data is only useful when people can see it at the right moment. A Zabbix dashboard is a page of widgets, each showing one view of your data: current problems, a graph, a status table. Good dashboards answer one question quickly. Bad ones show everything and answer nothing.

This lesson covers the kinds of dashboards, the widgets you will use most, and a design method. Zabbix cannot run on the site, so interface paths are described in words; stand-ins let you practice the ranking and filtering logic.

Types of dashboards

  • Global dashboards (Dashboards menu): shared with users and user groups, owned by someone, good for an NOC wall or a team overview.
  • Host dashboards (Zabbix 6.0 and newer): defined in a template, so every host linked to it gets the same dashboard under Monitoring > Hosts > Dashboards. Perfect for "one page per server".
  • Template dashboards are the way to define host dashboards: edit the template, add the dashboard, and all linked hosts see it. Widgets use the host context automatically.

Each dashboard has pages, which you can rotate for a wall display. Sharing is per user or user group with read-only or read-write rights. A dashboard can also be shown in kiosk mode for a screen without navigation.

The widgets you will use most

Widget Use
Problems Current problems filtered by host group, severity or tags
Problems by severity Count of problems per severity per host group
Graph Items over time, with data set patterns such as net.if.in*
Graph (classic) A single predefined graph
Top hosts Table of hosts with columns for items, with conditional coloring
Item value One big number or text with thresholds
Gauge One value on a dial with min/max
Honeycomb Many hosts or items as colored cells at a glance
Pie chart Share of a total, such as disk usage per directory
Host availability Counts of hosts up, down, unknown by interface
Geomap Hosts on a world map by their inventory location
Map / Map navigation tree Network maps (see graphs, maps and screens)
Clock, URL, Web monitoring Time, embedded pages, web scenario state
SLA report Compliance from SLA definitions (see SLA reports)

Widget names move between versions (Top hosts arrived in 7.0, "Data overview" was retired, "Item navigator" came in 7.0). Check the manual of your version.

Filtering with tags

Tags make dashboards reusable. Instead of listing hosts, a Problems widget can filter on service:checkout or env:prod. Combine that with host group filters and you have a dashboard per team that stays correct when hosts are added. This only works if your templates produce consistent tags, so decide a tag scheme early (service, env, team, component).

Widgets can also be linked: pick "Host" as a widget reference source, and a Problems widget, a Graph and an Item value on the same dashboard will follow whichever host is selected in a Host navigator widget.

A design method

  1. Pick the audience. NOC staff need "what is broken now". Managers need "are we meeting the SLA". Engineers need "why is this host slow".
  2. Put the answer in the top left. Western reading order: the most important widget goes first.
  3. Use color sparingly. Red means act. If half the dashboard is red or yellow all the time, people stop looking.
  4. Limit widgets per page. Eight to twelve is plenty. Use pages or linked dashboards for detail.
  5. Show scale. A graph without units or a fixed axis misleads. Set the Y-axis min/max where it matters.
  6. Test with real incidents. Replay the last outage: would the dashboard have shown the cause?
graph TD
  A["Overview dashboard<br/>Problems + availability"] --> B["Service dashboard<br/>per tag"]
  B --> C["Host dashboard<br/>from template"]
  C --> D["Latest data / graph"]

Drill down from a broad view to a specific host without leaving the dashboards.

Stand-in: ranking hosts for a Top widget

The Top hosts widget ranks hosts by item values and colors cells by thresholds. This Python model shows how the choice of aggregation changes the ranking.

Python Top hosts with thresholds (Python stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice how web01 ranks high only with max: one spike is easy to miss with last and avg.

Stand-in: filtering problems by tag

A Problems widget filters with tag conditions. This stand-in applies the "contains" and "equals" operators and shows why consistent tags matter.

Python Tag filter for a Problems widget (Python stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Mistakes to avoid

  • Dashboards owned by one person who leaves: share with a group and give a second owner.
  • Auto-refresh set to 10 seconds on 30 widgets: it loads the frontend and database. Default refresh intervals of 1 to 2 minutes are enough for most views.
  • Widgets pointing at old, renamed hosts or items. Prefer patterns and tags.
  • Too much text. A tiny table nobody can read on a wall display is wasted.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where do you define a dashboard that every host linked to a template should have?

    Template dashboards appear as host dashboards for every linked host.
  2. 2. Why filter a Problems widget by tags instead of listing hosts?

    Tag filters follow membership automatically.
  3. 3. Which aggregation shows a short spike most reliably in a Top hosts table?

    max over the period keeps spikes visible; last may miss them.
  4. 4. What is a good sign of a well-designed NOC dashboard?

    Focus and meaningful color make a dashboard usable.

Summary

  • Global dashboards serve teams; template dashboards give every host its own page.
  • Learn the common widgets: Problems, Graph, Top hosts, Item value, Honeycomb, Host availability.
  • Filter by tags and host groups so dashboards remain correct as the estate changes.
  • Design for one audience, one question, and limited color; avoid very fast refresh intervals.

Next: Graphs, Maps and Screens