Your servers.
The whole picture.
CPU, memory, disk, network and process activity. Connect the resource spike to the uptime incident, instead of investigating them separately.
Start monitoring ↗Follow the load.
Choose a server and resource to inspect its history and running processes.
Agent reporting
every 60 seconds
Find the process
behind the spike.
CPU history shows when demand changed. Process activity helps identify which workload was using those resources.
From the machine
to the incident.
Resource measurements become useful when you can relate them to the service your customers use.
Lightweight agent
Collect server metrics through the Statance agent on Linux, Windows and macOS. Install it with your account’s API key.
Metric history
Review what changed around the incident. Retention ranges from 24 hours on Free to a year on Business.
Resource alerts
Set alert rules around the metrics you care about. A disk-usage alert can surface a developing problem before a website check fails.
Security context
On Pro and Business, software versions and process findings add security context to the same servers you monitor.
Worth knowing.
Do I need an agent for website uptime checks?
No. Website and API checks run externally. Install the agent when you want CPU, memory, disk, network and process context from the server itself.
Which operating systems are supported?
The agent supports Linux, Windows and macOS. The installation guide covers the commands for each platform.
How long can I look back?
Free includes 24 hours of history, Pro includes 30 days and Business includes one year.