Pro & Business Feature

Know before your users do

Real-time metrics, instant alerts, public status pages. sh0 watches every container so you don't have to stare at dashboards all day.

What's included

Every metric that matters for production workloads, collected automatically.

CPU metrics
Per-container CPU usage with historical trends
RAM metrics
Memory consumption, limits, and OOM tracking
Disk I/O
Read/write throughput and IOPS per volume
Network traffic
Ingress/egress bandwidth per container
Container health
Running, stopped, restarting, OOM-killed status
Response time
HTTP latency percentiles (p50, p95, p99)

How it works

01

Enable monitoring per app

Toggle monitoring on for any app in the dashboard. sh0 starts collecting metrics immediately -- no agents to install, no config files to write.

02

Set alert thresholds

Define when you want to be notified: CPU above 90%, RAM above 80%, response time above 500 ms. Set per-app or server-wide defaults.

03

Choose notification channels

Route alerts to Slack, Discord, Telegram, email, or any webhook endpoint. Different apps can use different channels.

04

Relax -- sh0 watches 24/7

Metrics are collected every 15 seconds. Alerts fire within one minute of a threshold breach. You sleep, sh0 watches.

The monitoring pipeline

App Container
Metrics Collector
Threshold Check
Alert Router
Slack / Discord / Email

Metrics collected every 15 seconds -- alerts fire within one minute of a breach

Everything you need

Real-time dashboard

Live CPU, RAM, disk, and network graphs updated every 15 seconds. Zoom into any time range -- last hour, last day, last week.

5 alert channels

Slack, Discord, Telegram, email, and generic webhooks. Configure once, route alerts per app or per severity level.

Uptime checks

HTTP and TCP health checks from your server. Know when an app goes down before your users start complaining.

Public status pages

Generate a public status page for your services with real-time uptime indicators. Share it with your team or your customers.

Incident tracking

Every alert creates an incident with a timeline: when it started, when it was acknowledged, when it resolved. Full audit trail.

Historical metrics

Metrics are retained for 30 days (Pro) or 90 days (Business). Spot trends, plan capacity, and debug issues that happened last Tuesday.

The old way

  • x Install Prometheus + Grafana
  • x Configure exporters per service
  • x Write alert rules in YAML
  • x Set up Alertmanager
  • x Maintain a separate status page
  • x Hope nothing breaks at 3 AM

The sh0 way

  • Toggle monitoring on per app
  • Set thresholds in the dashboard
  • 5 channels built-in
  • Status pages included
  • Incident timeline automatic
  • Sleep through the night

Questions & answers

What metrics are collected? +
CPU usage, memory consumption, disk I/O, network traffic, container health status, and HTTP response times. All metrics are collected per container, so you can see exactly which app is consuming resources.
How often are metrics collected? +
Every 15 seconds by default. Alerts are evaluated on each collection cycle, so you are notified within one minute of a threshold breach.
Can I set custom thresholds? +
Yes. Each metric supports custom thresholds per app. For example, your API server might alert at 80% CPU while your background worker can safely run at 95%. You can also set server-wide defaults.
Is there a public status page? +
Yes. sh0 can generate a public status page showing uptime for your selected services. You get a shareable URL that displays real-time status and incident history -- no external tools needed.
How do alert channels work? +
You configure channels once in the dashboard (e.g., a Slack webhook URL, a Discord channel, an email address). Then you assign channels to apps or alert rules. When a threshold is breached, sh0 sends notifications to all assigned channels.
Does monitoring affect performance? +
Negligible impact. sh0 reads metrics from the Docker stats API and Linux /proc filesystem -- there are no agents running inside your containers. The overhead is less than 1% CPU and a few megabytes of RAM.

Stop flying blind

Real-time metrics, instant alerts, zero config. Know exactly what's happening on your server.