Self-Host Netdata: Real-Time Server Monitoring 2026

TL;DR

Netdata (GPL 3.0, ~72K GitHub stars) is a zero-configuration real-time monitoring agent that automatically detects and monitors everything running on your server — OS metrics, Docker containers, databases, web servers, Nginx, Redis, PostgreSQL, and 800+ other services. Collects metrics at 1-second resolution. Runs as a lightweight daemon (~100MB RAM). Pair it with Netdata Parents for multi-host aggregation, or export to Prometheus/Grafana. Replace DataDog/New Relic for self-hosted infrastructure monitoring.

Key Takeaways

• Netdata: GPL 3.0, ~72K stars — zero-config, 1-second metrics, auto-discovery
• 800+ integrations: Nginx, Apache, Docker, PostgreSQL, MySQL, Redis, and more — auto-detected
• Alerts built-in: 700+ pre-configured alert conditions, Slack/email/PagerDuty notifications
• Parent-Child: Stream metrics from many agents to one parent node for multi-host view
• Resource use: ~100MB RAM, ~1–2% CPU per node
• Grafana export: Export to Prometheus and visualize in Grafana with all the flexibility

---

Netdata vs Alternatives

Feature	Netdata	Prometheus + Grafana	DataDog	Zabbix
License	GPL 3.0	Apache 2.0 / AGPL	Proprietary	AGPL
Cost	Free	Free	$15+/host/mo	Free
Setup complexity	Zero-config	High (manual config)	Agent install	Complex
Metric resolution	1 second	Configurable	15-30s (free)	1 min
Auto-discovery	Yes	No (manual targets)	Yes	Yes
Built-in alerts	700+ rules	None (manual)	Yes	Yes
Multi-host UI	Parent node	Grafana dashboards	Yes	Yes
GitHub Stars	~72K	~56K / ~64K	—	—

---

Part 1: Docker Setup

# docker-compose.yml
services:
  netdata:
    image: netdata/netdata:latest
    container_name: netdata
    restart: unless-stopped
    pid: host
    network_mode: host
    cap_add:
      - SYS_PTRACE
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
    volumes:
      - netdataconfig:/etc/netdata
      - netdatalib:/var/lib/netdata
      - netdatacache:/var/cache/netdata
      - /etc/passwd:/host/etc/passwd:ro
      - /etc/group:/host/etc/group:ro
      - /etc/localtime:/etc/localtime:ro
      - /proc:/host/proc:ro
      - /sys:/host/sys:ro
      - /etc/os-release:/host/etc/os-release:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - NETDATA_CLAIM_TOKEN=${NETDATA_CLAIM_TOKEN:-}    # Optional: connect to Netdata Cloud
      - NETDATA_CLAIM_URL=https://app.netdata.cloud
      - DOCKER_HOST=unix:///var/run/docker.sock

volumes:
  netdataconfig:
  netdatalib:
  netdatacache:

docker compose up -d

Visit http://your-server:19999 — the dashboard is immediately populated with metrics.

---

Part 2: HTTPS with Caddy

metrics.yourdomain.com {
    reverse_proxy localhost:19999
}

Add basic auth to protect the dashboard:

metrics.yourdomain.com {
    basicauth {
        admin $2a$14$hash_here   # Use: caddy hash-password
    }
    reverse_proxy localhost:19999
}

---

Part 3: What Netdata Auto-Detects

On a typical server, Netdata immediately collects:

System metrics (always collected):

CPU: per-core utilization, frequency, interrupts
RAM: usage, swap, page faults
Disk: I/O, latency, utilization per disk
Network: bandwidth, packets, errors per interface
Processes: CPU/RAM per process, forks, context switches

Auto-detected services (examples):

Docker containers: CPU, RAM, network, disk per container
Nginx: requests/s, connections, status codes
Apache: requests/s, workers, scoreboard
PostgreSQL: queries/s, cache hit ratio, locks, vacuum
MySQL/MariaDB: queries, threads, InnoDB buffers
Redis: operations/s, memory, hit rate, clients
MongoDB: operations, connections, memory
Node.js: npm processes detected automatically

Check what's detected on your system:

# List all active collectors:
docker exec netdata netdatacli collectors

---

Part 4: Configure Alerts

Netdata comes with 700+ pre-configured alert conditions. To customize:

# Enter the container to edit alert config:
docker exec -it netdata /bin/bash

# Alert configs are in /etc/netdata/health.d/
ls /etc/netdata/health.d/
# cpu.conf, ram.conf, disk.conf, mysql.conf, nginx.conf, ...

Custom Alert Example

# /etc/netdata/health.d/custom.conf

alarm: disk_space_warning
on: disk.space
lookup: average -5m percentage used
units: %
warn: $this > 80
crit: $this > 90
delay: down 5m multiplier 1.5 max 1h
info: Disk space usage on disk $label:device

Alert Notifications

Configure in /etc/netdata/health_alarm_notify.conf:

# Slack:
SEND_SLACK="YES"
SLACK_WEBHOOK_URL="https://hooks.slack.com/services/YOUR/WEBHOOK"
DEFAULT_RECIPIENT_SLACK="#alerts"

# Email:
SEND_EMAIL="YES"
EMAIL_SENDER="netdata@yourdomain.com"
DEFAULT_RECIPIENT_EMAIL="ops@yourdomain.com"

# ntfy (self-hosted push):
SEND_NTFY="YES"
NTFY_SERVER="https://ntfy.yourdomain.com"
NTFY_TOPIC="netdata-alerts"

---

Part 5: Multi-Host Streaming (Parent-Child)

Stream metrics from multiple servers to one central Netdata Parent:

On the parent (receiver):

# /etc/netdata/stream.conf (in parent container volume)
[11111111-2222-3333-4444-555555555555]    # Child's machine GUID
    enabled = yes
    history = 3600
    default memory mode = dbengine
    health enabled by default = auto
    allow from = *

On the child (sender):

# /etc/netdata/stream.conf
[stream]
    enabled = yes
    destination = parent.yourdomain.com:19999
    api key = 11111111-2222-3333-4444-555555555555

Now the parent's dashboard shows all child nodes in one view.

---

Part 6: Prometheus Export for Grafana

Export Netdata metrics to Prometheus:

Add to Prometheus scrape_configs:

scrape_configs:
  - job_name: "netdata"
    metrics_path: "/api/v1/allmetrics"
    params:
      format: ["prometheus"]
    static_configs:
      - targets:
          - "localhost:19999"
          - "server2.yourdomain.com:19999"

Then use Grafana with the Prometheus data source. Netdata has pre-built Grafana dashboards:

1. Grafana → + → Import → Dashboard ID: 7107 (Netdata Overview)
2. Select your Prometheus data source → Import

---

Part 7: Kubernetes and Docker Monitoring

Netdata automatically collects Docker container metrics via the Docker socket. For Kubernetes:

# Install Netdata on Kubernetes via Helm:
helm repo add netdata https://netdata.github.io/helmchart/
helm install netdata netdata/netdata \
  --namespace netdata --create-namespace \
  --set persistence.enabled=true

For Docker — container stats are auto-collected. View per-container CPU/RAM/network in the dashboard under Docker Containers.

---

Part 8: Database Monitoring

PostgreSQL

# /etc/netdata/go.d/postgres.conf
jobs:
  - name: local
    dsn: postgresql://netdata:netdata_password@localhost:5432/postgres

Create the monitoring user:

CREATE USER netdata WITH PASSWORD 'netdata_password';
GRANT pg_monitor TO netdata;

Redis

# /etc/netdata/go.d/redis.conf
jobs:
  - name: local
    address: redis://localhost:6379

Netdata shows: ops/s, hit rate, memory, connected clients, keyspace.

---

Performance Tuning

# /etc/netdata/netdata.conf

[global]
    # Retention period (in seconds):
    history = 86400    # 1 day (default), increase for longer retention

    # Memory mode (for longer retention):
    memory mode = dbengine
    page cache size = 32    # MB

[web]
    # Disable remote access (if using reverse proxy):
    bind to = localhost

[plugins]
    # Disable unused plugins to reduce CPU:
    apps = no    # Per-process metrics (CPU intensive on large servers)

---

Maintenance

# Update Netdata:
docker compose pull
docker compose up -d

# Logs:
docker compose logs -f netdata

# Check collector status:
docker exec netdata netdatacli collectors

# Run health check:
docker exec netdata netdatacli cmd_version

Why Self-Host Netdata?

The case for self-hosting Netdata comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Netdata means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Netdata, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Netdata headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Netdata data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Netdata without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Netdata's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Netdata backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Netdata's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Netdata's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Netdata's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Netdata's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f netdata

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Netdata's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats netdata. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Netdata Updated

Netdata follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Netdata is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

---

See all open source monitoring tools at OSSAlt.com/categories/monitoring.