Scalar

Monitoring

See the slow leak, not just the spike

CPU, memory, disk and network from every server and every container, sampled continuously and plotted over time. It ships with the server and runs itself. Threshold alerts are next on the roadmap.

Snap into it Read the docs

Metrics are included. Alerts ship at no extra cost when they land.

dash.serversinc.io/servers/vps-100/metrics
The server metrics tab plotting CPU, memory, disk and network over the last day

What you can see right now

Server metrics

CPU, memory, disk, network

Per server, sampled continuously and kept as a time series you can scroll back through.

Container metrics

Per application

The same resource view, narrowed to a single container.

History

Trends, not just now

Plotted over time, so you catch the slow leak, not just the spike that already woke you.

Health checks

Host state at a glance

SSH config, updates, Fail2Ban, time sync and firewall, all on one tab.

Logs

Streamed live

Container logs in the dashboard or the CLI, live as they happen.

Deploy activity

What changed, when

Recent deployments sitting right next to the metrics they moved, so the regression names itself.

Metrics

A time series for every resource, no exporter required

Every server reports CPU, memory, disk and network on a short interval. Containers report the same for themselves. The standard setup does it all, so you run nothing extra.

  • Continuous sampling, retained as history you can scroll back through
  • Server-wide or narrowed to a single application
  • Lines up with deploy activity, so a regression points straight at the release that caused it
dash.serversinc.io/servers/vps-100/metrics
A metrics view with CPU and memory charts and a deployment marker on the timeline

Alerts · shipping next

Thresholds that page you

The next release turns any metric into an alert: set a threshold, pick a channel, get told when a server crosses it. Here is what is coming.

  • Thresholds on CPU, memory and disk, per server or per container
  • Delivered to Slack, Discord or a webhook
  • Build failures and unexpected container stops on the same channel
dash.serversinc.io/alerts · shipping next
A mockup of the alert rule form with a metric, threshold and delivery channel

Automation

Pull metrics into your own tools

Every metric the dashboard plots is on the API. Feed a Grafana panel, a status page, whatever you already run. The data is yours.

metrics.sh REST 
curl -s "https://api.serversinc.io/v1/servers/$SERVER_ID/metrics?range=24h" \
  -H "Authorization: Bearer $SERVERSINC_TOKEN" \
  | jq '.data[-1] | {cpu, memory, disk}'
terminal CLI 
$ sinc servers metrics vps-100 --range 1h
TIME   CPU%  MEM%  DISK%  NET IN/OUT
09:15  12    41    58     1.2M / 340K
09:30  18    43    58     2.0M / 510K
09:45  14    42    58     1.1M / 300K

Serversinc, or a monitoring stack to babysit

What changes when metrics arrive with the server.

Feature Traditional Serversinc
Setup Deploy Prometheus, Grafana, exporters, keep them running Metrics land with the server, ready to read
Scope Wire up each host and container by hand Every server and container, wired automatically
History Size and pay for your own retention Time series kept for you, retention handled
Host checks Separate tooling or a manual checklist Health tab on every server
Alerts Alertmanager rules in YAML Thresholds in the dashboard (shipping next)

FAQs

See your fleet

Connect a server and metrics start flowing in minutes. Alerts arrive in the next release.

Create an account Read the docs