What does Notory monitor, and how do I read the status overview?

Requires Pro

Quick answer

The Monitoring home page shows three count tiles at the top — Up, Down and Unknown — followed by the list of all systems (agent-based or manually checked) with their status and “Last seen”, plus recent alerts. Clicking a system name opens its history.

Prerequisites

Monitoring is part of the Operations module and available from the Pro tier. Without this license, the page shows the notice “Monitoring is not included in your license” (403).

Open Monitoring. Choose Monitoring in the left-hand navigation. At the top are the three count tiles:
- Up — systems with status up.
- Down — systems with status down.
- Unknown — systems without a current reading (unknown, e.g. newly created).
Screenshot pending monitoring-status-01 Monitoring home page with the Up, Down and Unknown count tiles

The three status tiles summarize all monitored systems.
Read the system list. The Systems table shows, per row, Name, Type (Agent or Manual), Address, Status and Last seen. Agent systems are reported by the agent; manual systems are checked server-side.

Screenshot pending monitoring-status-02 System list with columns Name, Type, Address, Status and Last seen

The system list distinguishes agent-based from manually checked systems.
Keep an eye on alerts. On the right, Recent alerts lists the latest events with state Firing (firing) or Resolved (resolved). Clicking a system name opens its history with resource usage charts.

Overview — GET /api/v1/monitoring/overview returns the counts and the recent alerts:

curl -H "Authorization: Bearer inv_dein_token" \
  https://demo.notory.io/api/v1/monitoring/overview

{
  "total": 12,
  "up": 9,
  "down": 1,
  "unknown": 2,
  "recent_alerts": [
    {
      "id": "al_7f3a…",
      "rule_id": "rl_1c2d…",
      "host_id": "hs_9a8b…",
      "state": "firing",
      "value": 96.4,
      "started_at": "2026-07-08T10:41:00Z",
      "resolved_at": null
    }
  ]
}

List systems — GET /api/v1/monitoring/hosts:

curl -H "Authorization: Bearer inv_dein_token" \
  https://demo.notory.io/api/v1/monitoring/hosts

Each host carries, among other fields, name, host_type (agent/manual), address, current_status (up/down/unknown) and last_seen_at.

Possible errors: 401 (token missing/invalid), 403 (the Operations module is not in your tier).

What happens behind the scenes?

Two data sources, one history: Manual systems are checked by a periodic server job (TCP/HTTP); agent systems send their own values. Both feed into the same time series.
unknown is normal for new systems: A freshly created system shows Unknown until the first check or agent report arrives.
Read-only: The overview doesn’t change anything; it is strictly scoped to your tenant.
Alerts converge here: “Recent alerts” reflects the events from your alert rules.