The only agent that thinks for itself

Autonomous Monitoring with self-learning AI built-in, operating independently across your entire stack.

Metrics, Logs & Traces
Machine learning & MCP
5% of one CPU core, about 200 MB RAM
3GB disk, >1 year retention
2,000+ integrations, zero config
Dashboards, alerts out of the box
> Discover Netdata Agents

Centralized metrics streaming and storage

Aggregate metrics from multiple agents into centralized Parent nodes for unified monitoring across your infrastructure.

Stream from unlimited agents
Long-term data retention
High availability clustering
Data replication & backup
Scalable architecture
Enterprise-grade security
> Learn about Parents

Fully managed cloud platform

Access your monitoring data from anywhere with our SaaS platform. No infrastructure to manage, automatic updates, and global availability.

Zero infrastructure management
Metrics stay on your nodes
US-hosted metadata
Automatic updates & patches
Enterprise SSO & RBAC
SOC 2 Type 2 certified
> Explore Netdata Cloud

Deploy Netdata Cloud in your infrastructure

Run the full Netdata Cloud platform on-premises for complete data sovereignty and compliance with your security policies.

Complete data sovereignty
Air-gapped deployment
Custom compliance controls
Private network integration
Dedicated support team
Kubernetes & Docker support
> Learn about Cloud On-Premises

Powerful, intuitive monitoring interface

Modern, responsive UI built for real-time troubleshooting with customizable dashboards and advanced visualization capabilities.

Real-time chart updates
Customizable dashboards
Dark & light themes
Advanced filtering & search
Responsive on all devices
Collaboration features
> Explore Netdata UI

Monitor on the go

Native iOS and Android apps bring full monitoring capabilities to your mobile device with real-time alerts and notifications.

iOS & Android apps
Push notifications
Touch-optimized interface
Offline data access
Biometric authentication
Widget support
> Download apps

The future of infrastructure observability

See our strategic direction across AI-native observability, full-stack signals, operational intelligence, and enterprise platform maturity.

AI-native observability
Full-stack signal coverage
Operational intelligence
Enterprise platform maturity
Agent releases every 6 weeks
Cloud continuous delivery
> Explore Product Roadmap

Best energy efficiency

True real-time per-second

100% automated zero config

Centralized observability

Multi-year retention

High availability built-in

Zero maintenance

Always up-to-date

Enterprise security

Complete data control

Air-gap ready

Compliance certified

Millisecond responsiveness

Infinite zoom & pan

Works on any device

Native performance

Instant alerts

Monitor anywhere

AI-native observability

Continuous delivery

Open source foundation

80% Faster Incident Resolution

AI-powered troubleshooting from detection, to root cause and blast radius identification, to reporting.

True Real-Time and Simple, even at Scale

Linearly and infinitely scalable full-stack observability, that can be deployed even mid-crisis.

90% Cost Reduction, Full Fidelity

Instead of centralizing the data, Netdata distributes the code, eliminating pipelines and complexity.

See and Map Your Entire Network

Live topology, flow analytics, and SNMP device and trap monitoring — unified with your full-stack observability.

Single Pane of Glass

Eliminate SSH access for monitoring and troubleshooting systems and applications.

Control Without Surrender

SOC 2 Type 2 certified with every metric kept on your infrastructure.

Integrations

2,000+ collectors and notification channels, auto-discovered and ready out of the box.

2,000+ data collectors
Auto-discovery & zero config
Cloud, infra, app protocols
Notifications out of the box
> Explore integrations
Real Results
46% Cost Reduction

Reduced monitoring costs by 46% while cutting staff overhead by 67%.

— Leonardo Antunez, Codyas

Zero Pipeline

No data shipping. No central storage costs. Query at the edge.

From Our Users
"Out-of-the-Box"

So many out-of-the-box features! I mostly don't have to develop anything.

— Simon Beginn, LANCOM Systems

No Query Language

Point-and-click troubleshooting. No PromQL, no LogQL, no learning curve.

Enterprise Ready
67% Less Staff, 46% Cost Cut

Enterprise efficiency without enterprise complexity—real ROI from day one.

— Leonardo Antunez, Codyas

SOC 2 Type 2 Certified

Zero data egress. Only metadata reaches the cloud. Your metrics stay on your infrastructure.

Full Coverage
2,000+ Collectors

Auto-discovered and configured. No manual setup required.

Any Notification Channel

Slack, PagerDuty, Teams, email, webhooks—all built-in.

Built for the People Who Get Paged

Because 3am alerts deserve instant answers, not hour-long hunts.

Every Industry Has Rules. We Master Them.

See how healthcare, finance, and government teams cut monitoring costs 90% while staying audit-ready.

Monitor Any Technology. Configure Nothing.

Install the agent. It already knows your stack.
From Our Users
"A Rare Unicorn"

Netdata gives more than you invest in it. A rare unicorn that obeys the Pareto rule.

— Eduard Porquet Mateu, TMB Barcelona

99% Downtime Reduction

Reduced website downtime by 99% and cloud bill by 30% using Netdata alerts.

— Falkland Islands Government

Real Savings
30% Cloud Cost Reduction

Optimized resource allocation based on Netdata alerts cut cloud spending by 30%.

— Falkland Islands Government

46% Cost Cut

Reduced monitoring staff by 67% while cutting operational costs by 46%.

— Codyas

Real Coverage
"Plugin for Everything"

Netdata has agent capacity or a plugin for everything, including Windows and Kubernetes.

— Eduard Porquet Mateu, TMB Barcelona

"Out-of-the-Box"

So many out-of-the-box features! I mostly don't have to develop anything.

— Simon Beginn, LANCOM Systems

Real Speed
Troubleshooting in 30 Seconds

From 2-3 minutes to 30 seconds—instant visibility into any node issue.

— Matthew Artist, Nodecraft

20% Downtime Reduction

20% less downtime and 40% budget optimization from out-of-the-box monitoring.

— Simon Beginn, LANCOM Systems

Pay per Node. Predictable Pricing.

Pay per node, with unlimited metrics and generous log and trace quotas.

Free tier—forever
No metric limits or caps
Retention you control
Cancel anytime
> See pricing plans

What's Your Monitoring Really Costing You?

Most teams overpay by 40-60%. Let's find out why.

Expose hidden metric charges
Calculate tool consolidation
Customers report 30-67% savings
Results in under 60 seconds
> See what you're really paying

Your Infrastructure Is Unique. Let's Talk.

Because monitoring 10 nodes is different from monitoring 10,000.

On-prem & air-gapped deployment
Volume pricing & agreements
Architecture review for your scale
Compliance & security support
> Start a conversation

Monitoring That Sells Itself

Deploy in minutes. Impress clients in hours. Earn recurring revenue for years.

30-second live demos close deals
Zero config = zero support burden
Competitive margins & deal protection
Response in 48 hours
> Apply to partner

Per-Second Metrics at Homelab Prices

Same engine, same dashboards, same ML. Just priced for tinkerers.

Community: Free forever · 5 nodes
Homelab: $90/yr · personal, non-commercial use
> Get the Homelab Plan

$1,000 Per Referral. Unlimited Referrals.

Your colleagues get 10% off. You get 10% commission. Everyone wins.

10% of subscriptions, up to $1,000 each
Track earnings inside Netdata Cloud
PayPal/Venmo payouts in 3-4 weeks
No caps, no complexity
> Get your referral link
Cost Proof
40% Budget Optimization

"Netdata's significant positive impact" — LANCOM Systems

Calculate Your Savings

Compare vs Datadog, Grafana, Dynatrace

Savings Proof
46% Cost Reduction

"Cut costs by 46%, staff by 67%" — Codyas

30% Cloud Bill Savings

"Reduced cloud bill by 30%" — Falkland Islands Gov

Enterprise Proof
"Better Than Combined Alternatives"

"Better observability with Netdata than combining other tools." — TMB Barcelona

Real Engineers, <24h Response

DPA, SLAs, on-prem, volume pricing

Why Partners Win
Demo Live Infrastructure

One-line install, real data—no sandbox needed

Zero Tickets, High Margins

Auto-config + per-node pricing = predictable profit

Homelab Ready
Free Video Course

8-episode Netdata tutorial by LearnLinux.tv

80k+ GitHub Stars

Open source, 690+ contributors

Worth Recommending
Product That Delivers

Customers report 90% cost cuts, 99% downtime reduction

Zero Risk to Your Rep

Free tier lets them try before they buy

AI Support Assistant, Available 24/7

Nedi has access to all official documentation, source code, and resources. Ask any question about Netdata—responds in your language.

Deployment & configuration
Troubleshooting & sizing
Alerts & notifications
Evidence-based answers
> Ask Nedi now

Never Fight Fires Alone

Docs, community, and expert help—pick your path to resolution.

Learn.netdata.cloud docs
Discord, Forums, GitHub
Premium support available
> Get answers now

60 Seconds to First Dashboard

One command to install. Zero config. 2,000+ integrations documented.

Linux, Windows, K8s, Docker
Auto-discovers your stack
> Read our documentation

80,000+ Engineers Strong

690+ contributors. 1.5M daily downloads. One mission: simplify observability.

Per-Second. 90% Cheaper. Data Stays Home.

Side-by-side comparisons: costs, real-time granularity, and data sovereignty for every major tool.

See why teams switch from Datadog, Prometheus, Grafana, and more.

> Browse all comparisons
Edge-Native Observability, Born Open Source
Per-second visibility, ML on every metric, and data that never leaves your infrastructure.
Founded in 2016
690+ contributors worldwide
Remote-first, engineering-driven
Open source first
> Read our story
Promises We Publish—and Prove
12 principles backed by open code, independent validation, and measurable outcomes.
Open source, peer-reviewed
Zero config, instant value
Data sovereignty by design
Aligned pricing, no surprises
> See all 12 principles
Edge-Native, AI-Ready, 100% Open
80k+ stars. Full ML, AI, and automation—GPLv3+, not premium add-ons.
80,000+ GitHub stars
GPLv3+ licensed forever
ML on every metric, included
Zero vendor lock-in
> Explore our open source
Build Real-Time Observability for the World
Remote-first team shipping per-second monitoring with ML on every metric.
Remote-first, fully distributed
Open source (80k+ stars)
Challenging technical problems
Your code on millions of systems
> See open roles
Meet the Team Behind Netdata
Conferences, meetups, and tradeshows where you can see Netdata in action and talk to the engineers who build it.
Live demos and deep dives
Book 1-on-1 meetings
Talks and panel sessions
Event recaps and photos
> See all events
Talk to a Netdata Human in <24 Hours
Sales, partnerships, press, or professional services—real engineers, fast answers.
Discuss your observability needs
Pricing and volume discounts
Partnership opportunities
Media and press inquiries
> Book a conversation
Your Data. Your Rules.
On-prem data, cloud control plane, transparent terms.
Trust & Scale
80,000+ GitHub Stars

One of the most popular open-source monitoring projects

SOC 2 Type 2 Certified

Enterprise-grade security and compliance

Data Sovereignty

Your metrics stay on your infrastructure

Validated
University of Amsterdam

"Most energy-efficient monitoring solution" — ICSOC 2023, peer-reviewed

ADASTEC (Autonomous Driving)

"Doesn't miss alerts—mission-critical trust for safety software"

Community Stats
690+ Contributors

Global community improving monitoring for everyone

1.5M+ Downloads/Day

Trusted by teams worldwide

GPLv3+ Licensed

Free forever, fully open source agent

Why Join?
Remote-First

Work from anywhere, async-friendly culture

Impact at Scale

Your work helps millions of systems

RUM Receiver

Plugin: dem.plugin Module: receiver

Overview

Monitor the endpoint that receives browser reports for Real User Monitoring: whether it serves and how its requests end.

The RUM receiver is the HTTP listener that websites load the RUM script from and send their visitors’ reports to. One receiver serves every RUM site on the Agent, and its charts show:

  • Whether the receiver is serving.
  • Requests per second that succeed, are refused (client errors, such as a refused origin, a rate limit or an unknown site) or fail on the server side.

The receiver starts with the DEM plugin and listens on 127.0.0.1:19938 by default, so only this host can reach it. To accept reports from visitors, put an HTTPS reverse proxy in front of it, or give it a TLS certificate and a public address. It serves the RUM script and the Grafana Faro Web SDK under /rum/, accepts each site’s reports at /rum/ followed by the site key and /collect, and contacts no external service.

The visitor’s IP address is taken from the connection, or from the X-Forwarded-For or X-Real-IP header when the connection comes from a trusted proxy. It is used for the rate limits and to look up the visitor’s location in a local database, and is not stored.

This collector is only supported on the following platforms:

  • Linux

This collector only supports collecting metrics from a single instance of this integration.

PermissionNeeded when
The Netdata service account (usually netdata) can read tls_cert and tls_key.The receiver serves HTTPS itself.
The Netdata service account can read the location database.geoip_db is set, or the Agent provides a database.

Default Behavior

Auto-Detection

The receiver starts with the stock dem/receiver.conf, listening on 127.0.0.1:19938. It receives nothing until a RUM site is configured and its script is on a website.

Limits

  • One receiver serves every RUM site on the Agent, and its settings apply to all of them.
  • Each visitor IP address can send 120 requests per minute and each site 500 per second (rate_limit); requests beyond that get HTTP 429.
  • Reports larger than 256 KiB get HTTP 413 (max_body_bytes).
  • Visitors arriving from loopback or private addresses get no location.

Performance Impact

The receiver parses and decodes every report, so its CPU use grows with the number of reports per second. In Netdata’s tests, receiving 1,000 reports per second took about a quarter of a CPU core. On busy websites, lower measure_sample_rate in the RUM site jobs to receive fewer reports.

Setup

Prerequisites

Make the receiver reachable over HTTPS

Visitors’ browsers must reach the receiver at a public HTTPS address; browsers do not let HTTPS pages send reports to plain HTTP. The usual setup keeps the default listen and adds the /rum/ path to an HTTPS reverse proxy on the same host. For NGINX:

location /rum/ {
    proxy_pass http://127.0.0.1:19938;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

Forward every path under /rum/, not only the script. Then set public_url to the proxy’s public address and trusted_proxies to the address the proxy connects from (see the first example).

If several Agents answer for the same public address, run the same Agent version on all of them: a page loads its SDK files from whichever server answers, and each must serve the files its script refers to.

To check the route, open https://rum.example.org/rum/ping in a browser; it only shows that this browser reaches the receiver. /rum/demo?key=SITE serves a test page with a site’s script. Neither proves that your website loads the script.

Optional - provide a location database

Countries and cities come from a local MMDB database. The receiver reads the file in geoip_db when it is set, and otherwise the database the Agent provides, if there is one. Without a database, reports are still collected, without location. Supported types are Netdata-Topology-GEO, GeoLite2-City, GeoLite2-Country, GeoIP2-City, GeoIP2-Country, DBIP-City-Lite and DBIP-Country-Lite; a country database gives no cities.

The collector.geoip object in the response of the rum-sites Function shows whether a database is loaded.

Configuration

Options

The receiver is a single job named receiver; there is one per Agent.

GroupOptionDescriptionDefaultRequired
ConnectionlistenAddress and port to listen on. The default accepts connections from this host only.127.0.0.1:19938no
public_urlPublic base URL of the receiver, such as https://rum.example.org, used in the sites’ script tags. Leave empty and no script tag is offered unless a site sets its own.no
tls_certCertificate file for serving HTTPS directly. Set together with tls_key; leave both empty to serve plain HTTP.no
tls_keyPrivate key file of the certificate. Set together with tls_cert.no
trusted_proxiesIP addresses or CIDR ranges of reverse proxies whose X-Forwarded-For and X-Real-IP headers are trusted for the visitor’s address. Leave empty to use the connection’s address.no
Limitsmax_body_bytesLargest report accepted, in bytes. Larger reports are refused with HTTP 413.262144no
rate_limitRequest limits that protect the Agent from floods of reports.no
rate_limit.per_ip_per_minRequests accepted per visitor IP address per minute. More are refused with HTTP 429.120no
rate_limit.per_site_per_secRequests accepted per site per second, from all visitors together. More are refused with HTTP 429.500no
Collectionupdate_everyData collection interval, in seconds.10no
geoip_dbLocation database (MMDB file) for looking up visitors’ countries and cities. Leave empty to use the database the Agent provides, if there is one.no

listen

Keep the default behind a reverse proxy on the same host. To accept connections from other hosts directly, listen on this host’s external address or on 0.0.0.0:19938, and set tls_cert and tls_key. The address is opened when the receiver starts; the job editor’s Test does not check that the port is free.

public_url

Use the address that visitors’ browsers reach, including any path prefix of your reverse proxy, such as https://www.example.org/edge. The receiver never derives it from the listen address or from request headers.

trusted_proxies

Behind a proxy, set this to the address the proxy connects from, such as 127.0.0.1/32 for a proxy on the same host. Without it, every visitor appears to come from the proxy, so they all share one rate limit and get no location. List only the proxies that actually connect to the receiver, because a trusted address can claim any visitor IP.

geoip_db

With an empty path, the receiver tries topology-ip-intel/topology-ip-geo.mmdb in the Agent’s cache directory, then in its stock data directory (NETDATA_CACHE_DIR and NETDATA_STOCK_DATA_DIR override the built-in directories). A path uses only that file. The database is checked when the receiver starts and every minute after. To update it, write a new file and rename it over the old one; never edit or truncate the file in use.

DEM never downloads a database. Agent packaging, the topology IP intelligence downloader or you provide and update it, and not every installation has one. Give the Netdata service account read access to the file and its directories.

via File

The configuration file name for this integration is dem/receiver.conf.

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config dem/receiver.conf
Examples
Behind a reverse proxy on the same host

The usual setup. The proxy serves https://rum.example.org and forwards /rum/ to the receiver.

jobs:
  - name: receiver
    listen: 127.0.0.1:19938
    public_url: https://rum.example.org
    trusted_proxies:
      - 127.0.0.1/32
Serve HTTPS directly

Accepts reports from other hosts on port 19938 with the receiver’s own certificate.

jobs:
  - name: receiver
    listen: 0.0.0.0:19938
    public_url: https://rum.example.org:19938
    tls_cert: /etc/netdata/ssl/rum.crt
    tls_key: /etc/netdata/ssl/rum.key
Use your own location database

Reads visitor locations from a GeoLite2 City database that you keep up to date.

jobs:
  - name: receiver
    public_url: https://rum.example.org
    trusted_proxies:
      - 127.0.0.1/32
    geoip_db: /var/lib/geoip/GeoLite2-City.mmdb
Allow more requests per visitor

Raises the per-IP limit for websites whose visitors share an address, such as offices behind one gateway.

jobs:
  - name: receiver
    public_url: https://rum.example.org
    trusted_proxies:
      - 127.0.0.1/32
    rate_limit:
      per_ip_per_min: 600
      per_site_per_sec: 500

Metrics

Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

The receiver’s charts are on this Agent’s host. Requests count every HTTP response of the receiver: success is a status below 400, including the 204 sent for reports that are excluded on purpose; client errors are 4xx, such as refused origins, rate limits, oversized reports and unknown sites; server errors are 5xx.

Per RUM Receiver instance

The Agent’s RUM receiver.

This scope has no labels.

Metrics:

MetricDescriptionDimensionsUnit
dem_receiver.stateRUM receiver availabilityserving, unavailablestate
dem_receiver.requestsRUM HTTP requestssuccess, client_errors, server_errorsrequests/s

Alerts

There are no alerts configured by default for this integration.

Troubleshooting

Known Errors

opening DEM history: load journal identity: journalhost: machine id: no machine id found

When

The Agent’s log shows this when dem.plugin starts on Linux. The plugin then exits, so no DEM job runs, whichever modules are enabled.

Cause

DEM keeps its history in journal files, which need the host’s machine ID, and none was found. Neither /etc/machine-id nor /var/lib/dbus/machine-id holds a valid ID, and neither file exists under the Netdata host prefix (/host in the official Docker image). This is common in minimal containers.

Fix

On a host, create the machine ID with sudo systemd-machine-id-setup (or sudo dbus-uuidgen --ensure=/etc/machine-id without systemd), then restart the Agent.

In the official Docker image, mount the host’s machine ID under the Netdata host prefix: add -v /etc/machine-id:/host/etc/machine-id:ro to docker run, or the same mount under volumes: in Docker Compose, then recreate the container. Check first that the host has /etc/machine-id: Docker creates a missing source path as an empty directory, which DEM rejects.

listen tcp 127.0.0.1:19938: bind: address already in use

Cause

Another process, or another Netdata Agent, already listens on that address and port.

Fix

Find the process with sudo ss -ltnp | grep 19938, then stop it or change listen to a free port, and update the reverse proxy to match.

listen tcp 0.0.0.0:443: bind: permission denied

Cause

listen uses a port below 1024, which the Netdata service account is not allowed to bind.

Fix

Use a port above 1024, such as the default 19938, and serve port 443 from a reverse proxy.

listen: address 19938: missing port in address

Cause

listen has no host part.

Fix

Use 127.0.0.1:19938, or :19938 to listen on all addresses.

tls_cert and tls_key must be set together

Cause

Only one of tls_cert and tls_key is set.

Fix

Set both to serve HTTPS, or neither to serve plain HTTP.

listener TLS: could not read certificate "/etc/netdata/ssl/rum.crt": open "/etc/netdata/ssl/rum.crt": permission denied

Cause

The certificate or key file does not exist or the Netdata service account cannot read it. A similar message names the key file.

Fix

Check the path, and make the files readable by the Netdata service account (usually netdata).

body and rate limits must be positive

Cause

max_body_bytes, rate_limit.per_ip_per_min or rate_limit.per_site_per_sec is zero or negative.

Fix

Set them to positive values, or remove them to use the defaults.

trusted proxy "10.0.0.0/33": <parse error>

Cause

A trusted_proxies entry is not a valid IP address or CIDR range.

Fix

Use addresses such as 127.0.0.1 or ranges such as 10.0.0.0/8.

public_url must be an http(s) base URL without credentials, query or fragment

Cause

public_url is not an absolute http:// or https:// URL, or it has a username, a query string or a fragment. A RUM site’s own public_url reports the same message.

Fix

Use a URL such as https://rum.example.org, with an optional path prefix.

GeoIP refresh: <error>; provision a supported database using atomic file replacement

When

The message is a warning in the Agent’s log; collection continues without location or with the previous database.

Cause

The location database could not be loaded - it is missing, unreadable, of an unsupported type, or was changed while in use.

Fix

Make a supported database readable by the Netdata service account, and update it by writing a new file and renaming it over the old one. collector.geoip in the rum-sites Function shows the state and a reason code.

RUM charts have no country breakdown

Cause

There is no usable location database (collector.geoip.state is unavailable in rum-sites), the site sets capture.geolocation: 'off', or visitors arrive from loopback or private addresses - which is what a reverse proxy looks like when trusted_proxies is not set.

Fix

Provide a location database (see Prerequisites), and set trusted_proxies to the reverse proxy’s address.

Every visitor gets HTTP 429 behind a reverse proxy

Cause

Without trusted_proxies, all requests appear to come from the proxy’s address and share the per-IP limit.

Fix

Set trusted_proxies to the address the proxy connects from.

The observability platform companies need to succeed

Sign up for free

Want a personalised demo of Netdata for your use case?

Contact Sales