Status - chuckablack/quokka GitHub Wiki
Device Status
Since quokka is regularly monitoring devices for pertinent information, it also stores the retrieved information in a device-status table, expressly for that purpose. Quokka is then able to display graphs of that information, for a specific number of past entries.
The following screen shows status, CPU, and memory utilization for a device:
As you can see, for devices quokka displays availability, response time, cpu utilization, and memory utilization. Availability and response time quokka always has, but cpu and memory are available at the whim of the device, and so these may remain unpopulated.
Host Status
The following screen shows status and hourly summaries for a host:
As you can see, for host status, quokka shows the current most-recent values for availability and response time, but then also, on the right, it displays hourly summaries of these values.
Service Status
The following screen shows status and hourly summaries for a service:
As you can see, for service status, quokka shows the current most-recent values for availability and response time, but then also, on the right, it displays hourly summaries of these values. On those summaries, it is possible to compare the actual values against some type of Service Level Agreement (SLA), which has been configured. When the hourly value does not meet the SLA, and event is generated.
Note: For the hosts display, SLA does not really make sense, since hosts are automaticaly discovered, which does not lend itself to configuration of an SLA. If you wanted an SLA just for a single host, you could modify quokka to create an ICMP service, for which you could then configure your desired host. Of course this feature might also be implemented in a future version of quokka.