Device Statuses

Connection status

octoja shows the connection state of each device as a coloured ring around the device-kind icon. The same five-variant staleness scale is used in both the device list and on the device detail page.

On devices that run an octoja agent, the state comes from the agent's own connection. Network devices you add without an agent — switches, firewalls, printers and the like — use the online-state check you picked when you registered them: Ping (ICMP), TCP port, SNMP or Always online. The monitoring device you assigned runs that check from inside the customer network and reports the result; devices set to Always online are never probed.

Device list view

The S. column at the left of the table shows the device-kind icon wrapped in a coloured ring that follows the same staleness thresholds as the device detail page. In the list the ring colour is the only signal — the online badge, the extra server emphasis and the cobweb overlay described below appear only on the detail page. Point at the icon to read the exact state: Online, or "Last seen" with the relative time.

Device detail page

A badge sits above the device-kind icon and reads Online on green or Offline on red. The ring around the icon adds the detail: when a device is offline, the ring changes colour based on time since Last seen.

The icon's tooltip gives the last-seen time as relative time ("2 hours ago", "3 days ago").

Understand maintenance status

While a maintenance window is active, device details show Maintenance mode active, its end and the areas actually paused: alerts, checks, automations, software deployments or patches. Named active windows appear as the reason or reasons. Multiple windows can apply together; maintenance does not automatically mean that all work is paused. How to set maintenance windows on a device or plan them in config packages is described in Maintenance mode and maintenance windows.

With the Maintenance mode device action, you can select Clear maintenance. This removes only the window set directly on the device. Windows from configuration packages remain; if one is still active, the maintenance banner stays visible. For multiple devices, use Maintenance → Clear maintenance in the device actions.

When a patch policy has Automatic maintenance mode enabled, it appears as a maintenance reason during patch execution. The option is off by default. This automatic window suppresses alerts only, at most until the patch window ends; other maintenance windows remain unchanged.

Change a device's type

Every device that runs an octoja agent is classified as either a workstation or a server. octoja auto-detects the type from the operating system the agent reports, so most devices are classified correctly without any action from you. When the auto-detected type is wrong — for example a workstation that actually runs as a server — you can override it manually.

Open the device detail page, click the actions menu (the "..." button at the top right), and choose Change Device Type. Pick Workstation/Endpoint or Server and select Save. Your manual choice overrides the operating-system-based classification, and the device-kind icon updates to match. The device's operating-system family stays the same — only the workstation-versus-server role changes.

The action needs the Edit Device permission on that device and appears for Windows, Linux and macOS devices. Network devices added without an agent keep the kind you picked when you registered them — change that with Edit network device in the same menu.

Availability in check history

Open the online-state check's history to inspect recorded availability. The window spans the first to the last displayed result; each state holds until the next sample. Even brief recorded outages prevent a 100% uptime display. Very small outage shares appear as Online >99.9% and Offline <0.1%. This does not prove uninterrupted availability outside the recorded window.

You can temporarily acknowledge known check issues without stopping monitoring or its history. This affects the evaluated check status, not the device's actual connection state.

Last seen

Last seen is the most recent contact of any kind from the device — a heartbeat, a connection, or an inventory upload. To count as Online, the device must have an active connection state and sufficiently recent contact. When it is offline, time since Last seen sets the staleness ring colour; it does not measure the exact time since disconnection. octoja shows it as relative time ("2 hours ago", "3 days ago") so you can tell at a glance how stale the data is.

Last Inventory is a separate timestamp: when the device last uploaded a full hardware and software inventory. It can lag well behind Last seen — a device that is online right now may have last reported hours ago. The device detail page shows it in the "Last Inventory" row, and both timestamps are available as columns in the device list.

If a device should be online but shows an unexpected offline state, check the device's network connectivity and confirm the octoja agent service is running.

FAQ

Can I change the Device online check interval?

No. The check uses a fixed five-minute interval. For agent devices, connection changes also trigger evaluation, so detecting a disconnect does not have to wait for the next interval. Brief disconnects have a grace period.