Usage ideas

StateTip is designed as a data backend for dashboards in monitoring system. The consequence is that data sent to StateTip in real time as a stream, but retrieved on request. This operation mode comes handy in a number of scenarios.

Monitoring display

The most obvious is the original need: monitoring. Let’s assume a StateTip instance receives from a monitoring system data from probes, like server availability, CPUs, or filesystems. This StateTip allows to build a dashboard with all known servers along with their status (up/down) and another one that for a specified server displays disk space usage for server’s filesystems (disk usage graphs need to be retrieved from somewhere else, but list of what needs to be retrieved is read from StateTip).

A similar use is to make StateTip to remember result of a task job is run not too often. Some good examples include a cron script that finds X.509 certificates in /etc and lists their expiry time and backup jobs. These can be then displayed on a dashboard.

In the above examples a dashboard is supposed to query StateTip to discover objects to display. This allows sysadmin to avoid registering any new server or service in the dashboard.


StateTip can be used to keep an inventory of system elements, like status of OS updates or versions of software running on servers. The status would be collected by a cron script and sent to StateTip, which then can be queried at later time.

Inventory can also be generated indirectly. Identity of VPN clients can be extracted VPN gateway logs, or MAC+IP can be extracted from DHCP leases. Once these are sent to StateTip, sysadmin can check in a single place where a specific VPN client or device is connected to.

Table Of Contents

Previous topic

Operating StateTip

Next topic

StateTip client

This Page