Server monitoring that explains website outages.
Track CPU, memory, disk, load average, network, top processes, and the websites hosted on each server. One dashboard shows infrastructure pressure and customer-facing impact together.
Permanent Free plan, or a 10-day card trial of paid coverage from $6/month.
What Is Server Monitoring?
Server monitoring collects host metrics on a schedule so you can investigate resource pressure separately from public website availability. Visual Sentinel uses a lightweight Linux and macOS Bash agent that reports every 60 seconds over HTTPS. It records CPU usage, memory and swap where available, root-disk capacity, network counters, load averages, uptime, process count, and the top CPU-consuming processes supported by the host. You can set CPU, memory, and disk thresholds and route resulting alerts through the channels available on your paid plan. Server metric history is retained for 14 days on Solo and Starter, 30 days on Business, and 90 days on Agency. Linking a server to its public website monitors puts host evidence and customer-facing incidents in one dashboard, but it does not replace application tracing or service-specific telemetry.
Built for issues
customers actually notice.
CPU, Memory, Disk & Network
Track CPU usage, memory and swap where available, root-disk capacity, and network counters on a 60-second reporting schedule.
Threshold-Based Alerts
Set custom thresholds for CPU, memory, and disk usage. When any metric breaches your limit, get alerted via email, Slack, Discord, Telegram, WhatsApp, or webhooks.
One-Command Agent Install
Install the Bash monitoring agent with a single curl command on supported Linux or macOS hosts. Bash, curl, jq, cron, and standard system tools are required.
Process Monitoring
See the top 10 processes by CPU usage, including the reported memory percentage and user, as investigation context.
Server + Website in One Dashboard
No need for separate infrastructure and application monitoring tools. Server metrics, uptime, SSL, DNS, performance, and visual checks, all in one place.
Plan-Based Historical Charts
Review retained server history for 14 days on Solo and Starter, 30 days on Business, or 90 days on Agency.
Connect server pressure to the website incident.
Server metrics matter most when they explain what users saw. These guides cover traffic spikes, Linux updates, security changes, and the monitoring architecture that keeps alerts useful.
Apache, Tomcat, IIS, and SQL Server monitoring
Visual Sentinel combines supported Linux or macOS host metrics with checks against the public endpoints those services expose. It does not collect application traces, database internals, JMX, IIS counters, or private localhost metrics, so use a service-specific telemetry product when those signals are required.
Apache web server monitoring
Apache failures can include worker-pool exhaustion, slow upstreams, and module errors that return 5xx responses. On a supported Linux or macOS host, Visual Sentinel can place CPU, memory, load, and public endpoint evidence in the same incident view when retained data is available.
The agent does not collect Apache busy-worker counts, requests per second, or scoreboard state, and Visual Sentinel does not fetch localhost or private-network pages. Keep mod_status private and use an Apache-aware metrics platform for those internals. Visual Sentinel can independently monitor the public URLs Apache serves.
Apache Tomcat monitoring
Tomcat sits between the JVM and the application. The common Tomcat failure modes are heap exhaustion (full GC stalls), thread-pool saturation under burst load, and slow JDBC pool exhaustion when a downstream database stalls. Host-level metrics catch the symptoms (high CPU during full GC, memory pressure on heap-bound workloads); the website-layer checks confirm whether requests still get through.
The agent does not collect JMX, Tomcat thread-pool depth, JVM heap, or garbage-collection pause metrics. Keep JMX and private Actuator endpoints on a private network and use a JVM-aware telemetry product for them. Visual Sentinel can pair supported host evidence with checks against the public URLs Tomcat serves.
IIS (Windows) monitoring
IIS failures can include application-pool recycles, request-queue saturation, and 503 responses during worker restarts. Visual Sentinel does not currently ship a Windows or PowerShell host agent. It can monitor the public HTTP or HTTPS URLs served by IIS, including configured status and body assertions.
Use a Windows-aware infrastructure product for IIS counters such as current connections, app-pool queues, and requests per second. Visual Sentinel's role is the external customer path: scheduled uptime, TLS, request-timing, and eligible visual or configured content evidence for public IIS URLs.
SQL Server monitoring
SQL Server failures can involve tempdb pressure, blocking, plan regressions, or replica lag. Visual Sentinel does not query SQL Server, collect wait statistics, or report disk queue depth. On SQL Server for Linux, its host agent can provide general CPU, memory, load, root-disk capacity, and network context; no Windows agent is currently shipped.
Use a database-aware monitoring product for active connections, blocked sessions, wait statistics, and replica lag. Do not expose database internals publicly for Visual Sentinel. Instead, monitor the public application endpoints that depend on the database and review their failures beside any supported host evidence.
Three steps,
no extensions.
Add Your Server
Enter your server name, hostname, and operating system. Visual Sentinel generates a unique agent token for secure communication.
Run the Install Script
Copy the one-line curl command and run it on a supported Linux or macOS server with sudo. After installation, the agent reports metrics every minute via cron.
Set Thresholds & Get Alerts
Configure CPU, memory, and disk thresholds and choose the supported notification channels. A breach observed in a reported sample can trigger the alert workflow.