The service is slow, not necessarily unavailable
External monitoring records the user-facing result while the host view shows the resource trend around that time.
Linux host metrics · Beta
Monitor VPS and Linux servers alongside the services they run
PingView combines external website, API and service monitoring with Linux host metrics, so an incident can include server context from the same period.
- Linux hosts only
- New sample every 60 seconds
- 30-day metric history
Uptime alone does not show what is happening on the VPS
External checks show the result available to a visitor or API client. Host metrics add operating context without replacing external monitoring.
A VPS can be under pressure before it fails
CPU, memory, swap and disk trends make resource pressure visible in the same PingView workspace.
Give an incident server context
When a monitor is linked to a metrics host, the incident view can show relevant host events and samples from its time window.
Linux host metrics
The VPS signals operators and application teams need
The Linux beta collects these host-level metrics. It does not inspect application content, customer data or user request contents.
CPU
CPU use, I/O wait and steal time help put load and noisy-neighbour pressure in context.
RAM and swap
Available memory and swap use show whether the host is relying on swap.
Disk and inodes
Per-mount usage, free space and inode usage expose capacity problems that disk percentage alone can miss.
Network traffic
Inbound and outbound traffic rates add a network view to the host timeline.
One timeline, without guessing what caused an outage
PingView keeps the external check and host metrics as separate signals, then presents host context for a linked monitor's incident.
- 1
Monitor the website, API or service externally
Use the PingView dashboard or a platform integration to monitor the result available to users.
- 2
Connect a Linux metrics host
The Linux agent sends one host-metric sample every 60 seconds to your PingView workspace.
- 3
Review the incident context
For a monitor linked to that host, the incident view can display matching metrics and host events in its time window.
Host context is additional evidence, not an automatic root-cause diagnosis. It is available only when the relevant monitor is linked to a reporting metrics host.
What the Linux host metrics beta includes
- Linux hosts only
- CPU, RAM, swap, disks, inodes and network traffic
- One-minute collection and 30-day history
- Disk-usage alerting
VPS and Linux host monitoring FAQ
Is Linux host monitoring available now?
It is rolling out in stages as a beta for Linux hosts. The current beta scope includes one host-metric sample every 60 seconds and 30 days of history.
Which Linux metrics does PingView collect?
PingView collects CPU usage, I/O wait, steal time, available memory, swap use, per-mount disk usage, inode usage, free disk space, and inbound and outbound network traffic.
Does the Linux agent collect application content or customer data?
No. The agent sends operational Linux host metrics. The beta does not inspect application content, customer data or user request contents.
Can I see VPS metrics for a service incident?
Yes, when the service monitor is linked to a reporting metrics host. The incident view can show host context from the incident time window; it is evidence, not an automatic root-cause finding.
Practical guides for WordPress on a VPS
Add VPS context to service monitoring
Start with external checks for a website, API or service, then connect a Linux host when you need its metrics alongside an incident.
Create a PingView account