📈 Setup Netdata — Real-Time Performance Monitoring
Get instant visibility into CPU, memory, disk, network, containers, and thousands of other metrics — no login required, fully open dashboard out of the box.
📦 Resources & Setup Scripts
Grab the automated bash script from GitHub to follow along with the video.
Quick Install:
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/monitoring/netdata/netdata-ubuntu.sh
chmod +x netdata-ubuntu.sh
sudo bash netdata-ubuntu.shTutorial Steps
1 Download & Run the Script
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/monitoring/netdata/netdata-ubuntu.sh
chmod +x netdata-ubuntu.sh
sudo bash netdata-ubuntu.sh2 Open the Dashboard
No login required — the dashboard loads directly:
http://<your-server-ip>:199993 Explore the Metrics
Netdata automatically discovers and monitors hundreds of metrics from your system and any running Docker containers. Browse the left sidebar to explore.
4 Configure Alerts (Optional)
Edit the alert configuration files in /etc/netdata/ to customize thresholds and notification channels (email, Slack, PagerDuty, etc.).
Ports Used
| Port | Purpose |
|---|---|
| 19999 | Netdata Web Dashboard |
Overview
Netdata is an open-source, real-time performance and health monitoring tool that collects thousands of metrics per second from the OS, applications, and services. It provides an interactive dashboard with per-second granularity, anomaly detection, and alerting — all with zero configuration required for most metrics. It can run standalone or as part of a Netdata Cloud fleet.
Why Use It
Netdata provides real-time, per-second performance monitoring with zero configuration for most Linux systems and services. While tools like Prometheus require you to manually set up exporters, configure scrapers, and build dashboards in Grafana, Netdata auto-discovers and monitors Nginx, MySQL, Redis, Docker, Postgres, and hundreds of other services the moment they are running. The result is immediate, deep visibility into your system's behavior without hours of instrumentation setup. For teams that need diagnostic power fast, Netdata's instant dashboards are unmatched.
When You Need It
Who Should Use It
Real Use Cases
Main Features
How to Use After Installation
Security Best Practices
Ports and Firewall Notes
Netdata listens on port 19999 by default. This port should NOT be exposed to the internet without authentication. Restrict it to localhost in netdata.conf (bind to = 127.0.0.1) and use a reverse proxy with HTTPS and authentication for external access. For Netdata Cloud connectivity, the agent connects outbound — no inbound ports are needed. Metric streaming to other tools (Prometheus, InfluxDB) uses their respective ports and can be configured to be outbound-only as well.
Backup and Maintenance
Common Mistakes
Troubleshooting
Alternatives
Prometheus with Node Exporter, cAdvisor, and Grafana is the most popular self-hosted alternative — more configurable and better for long-term metric storage, but requires significant setup and maintenance. Zabbix is a full enterprise monitoring platform with historical data, alerting, and inventory management. Beszel is a simpler, lighter hub-agent monitoring tool focused on fleet overview metrics without per-second granularity. For managed monitoring, Datadog, New Relic, and Grafana Cloud offer Netdata-equivalent coverage as SaaS products. If you're already running Prometheus, adding Netdata as an additional agent creates redundancy — consider using Netdata's Prometheus endpoint instead for native integration.
When Not to Use It
Netdata is not designed for long-term metric retention — by default it stores only hours to days of data depending on configuration. For compliance-grade historical metrics spanning months or years, a dedicated time-series database like InfluxDB or Prometheus with remote storage is required. Netdata also does not handle distributed tracing, structured logs, or application performance monitoring (APM) — for full observability you still need a logging stack (ELK, Loki) and tracing (Jaeger, Tempo). If your team already has a mature Prometheus/Grafana setup, adding Netdata creates overlap rather than value. For extremely resource-constrained servers (under 256 MB RAM), even Netdata's minimal footprint may be too heavy.
Need Help Setting Up Netdata?
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support. Whether you need a single-server setup or a multi-site network, our team ensures your infrastructure is built right, secured properly, and maintained reliably.
Frequently Asked Questions
Does Netdata require configuration to start monitoring services like Nginx or MySQL?
For most services, very little or no configuration is needed. Netdata auto-detects running services and reads their standard metrics endpoints (like Nginx's stub_status or MySQL's performance schema). You may need to create a dedicated read-only user for database monitoring, but no custom scrape jobs or dashboard building is required.
How much disk space does Netdata use for metric storage?
Netdata uses a tiered storage system. With default settings, it typically uses 200-500 MB for per-second metrics stored for a day or two. For longer retention, you can increase the dbengine memory size in netdata.conf. Netdata Cloud stores metrics with longer retention in the cloud without consuming local disk.
Can Netdata send alerts to Slack or PagerDuty?
Yes. Netdata supports dozens of notification targets including Slack, PagerDuty, email, OpsGenie, Twilio, Telegram, and more. Configure notification channels in /etc/netdata/health_alarm_notify.conf. Alert conditions are defined in /etc/netdata/health.d/ — you can customize thresholds or add new alerts.
How does Netdata Cloud work and is it free?
Netdata Cloud provides a centralized dashboard for all your Netdata nodes. Your metrics stay on your servers — the cloud receives only lightweight telemetry for coordination. A free tier is available with unlimited nodes and 14 days of metric retention. Paid tiers add longer retention, more alert rules, and enterprise features.
Can I export Netdata metrics to Prometheus or Grafana?
Yes. Netdata exposes a Prometheus-compatible metrics endpoint at http://localhost:19999/api/v1/allmetrics?format=prometheus. Add this as a scrape target in your Prometheus configuration and use Grafana as normal. Netdata also supports streaming metrics directly to InfluxDB, Graphite, and other backends.
Does Netdata work with Docker and Kubernetes?
Yes. Netdata monitors Docker containers automatically by reading the Docker socket. For Kubernetes, Netdata provides a Helm chart and a DaemonSet deployment that collects node, pod, and container metrics. The Kubernetes integration also correlates metrics with pod labels and namespaces for better filtering.
How do I reduce Netdata's resource usage if it's consuming too much CPU?
Increase the update every value in netdata.conf from 1 to 2 or 5 seconds to reduce collection frequency. Disable collectors you don't need by adding disabled = yes entries. Reduce the number of charts by disabling high-frequency network interface or disk metrics you don't monitor. On very constrained systems, lowering the dbengine memory size also helps.
Is Netdata suitable for production monitoring in regulated environments?
Netdata is suitable for operational monitoring in regulated environments, but should be supplemented with dedicated SIEM and log management solutions for full compliance coverage. Netdata Cloud's data sharing should be reviewed against your data residency requirements. Self-contained Netdata deployments without cloud connectivity can be used in air-gapped environments.