EveryUp · Self-hosted monitoringService health and errors in one place

Monitor uptime, logs, API response times, and server resources.
Configure notification channels and rules to receive alerts when their conditions are met.

Get started

Live Demo

GitHub

The EveryUp overview. payment-worker flagged as down, a monitoring scope of 2 Docker environments, 4 uptime monitors, 3 directly connected services and 2 infrastructure resources, and 3 recent incidents.

The uptime screen. Summary of 3 healthy, 0 down, 1 paused or pending, and a list of 4 HTTP and TCP monitors.

The logs screen. ERROR and WARN counts and trends per service, and a list of frequent errors.

The infrastructure screen for edge-host-01. Tiles for CPU 42%, memory 68%, disk 89% (critical), network 18 MB/s, and CPU, memory, disk I/O, and network trend charts.

The API requests tab of the api service. A request trend chart with request and error bars per 10 minutes, a dashed last-week line and a deploy marker, p95 latency of 121 ms, and recent requests.

The trace panel for a payment request. SERVER and CLIENT spans in error, a masked request JSON and an upstream_timeout response, the API request that ended in 503, and 2 related error logs.

The alerts screen. 178 sent and 9 failed in 7 days, 95% success, and the Telegram, Discord, and Slack channels.

OverviewThe services that need attention, your monitoring scope, and recent incidents on one screen.

The dashboard UI is Korean only. Try it in the live demo.

Stopped services, full disks

Choose container state, logs, and host resources to collect with the Docker Collector. Use uptime monitors to check public URLs and TCP ports.

See what is collected

Slow APIs

Collect API response times and traces without app changes on supported Linux hosts using the eBPF Observer. Cross-service trace correlation has additional requirements.

Check automatic API collection requirements

Why a request failed

Capture request and response headers and bodies with OpenTelemetry to investigate failures. Automatic body capture is opt-in for Node.js; Java requires application code.

Set up header and body capture

Incident alerts

Configure channels and alert rules. When an enabled rule's conditions are met, receive notifications in Telegram, Discord, or Slack.

Set up notifications

Monitored server

existingApp containersNo code or image changes

docker.sock:roreads state & logs

installDocker CollectorContainer state · stdout/stderr logs · host metrics

OTLP/HTTP :4318sends traces

optionaleBPF ObserverAPI response times · traces, no app code changes

HTTP(S) :3001no inbound ports

Dashboard server

installEveryUp WebUI · REST API · SQLite · alert rule evaluation

Without the Collector

Uptime monitorsResponse checks on public HTTP/TCP endpoints
OTLP endpoint/api/v1/otlp for services outside Docker

HTTPSnotifications

Alert channels

Telegram
Discord
Slack

The Collector on each monitored server sends the selected data to Web. Web notifies your connected channels when enabled rule conditions are met. Monitored servers need no inbound ports.