Zabbix Monitoring & alerting
Ask plain-English questions about your own Zabbix monitoring — active alerts, host health, metrics and history — answered from live data.
Connect your Zabbix instance and Sauble can investigate incidents against your real monitoring data — no dashboards to click through. It reads what is broken right now, which hosts and groups are affected, the metrics behind a problem, and the timeline of how it unfolded.
What Sauble can do
7 capabilities, grouped by what you are trying to find out.
See what is wrong right now
get_problemsEverything currently in an alert state — name, severity, which host, and since when.get_eventsThe timeline of problems opening and clearing over a window — how an incident unfolded.get_triggersThe alert rules on your hosts: what condition fires, at what severity, and which are firing now.Explore your estate
get_hostsYour monitored hosts with their status, availability, and network interfaces.get_host_groupsHow your estate is organized into groups, with a host count for each.Read the metrics
get_itemsThe metrics tracked on a host — CPU, memory, traffic and more — with their latest values.get_item_historyThe recent time series behind any metric, to see exactly when it started to move.Full read APIrun_readreaches the rest of Zabbix's read-only query API — anything the curated tools don't cover.
Ask it things like
Natural language — Sauble picks the right tools for you.
How Zabbix organizes your data
The 5 things Sauble reads — and how they connect.
Host groups
Top-level buckets that organize your estate — typically by site, team, or role.
Hosts
The individual servers and devices monitored, each with interfaces and an availability state.
Items (metrics)
The readings collected from a host — CPU, memory, traffic — each with a latest value and history.
Triggers (alert rules)
Conditions evaluated against items. When one is met, a problem is raised.
Problems & events
Problems are active, unresolved alerts; events are the open/close transitions that form the timeline.