Anonymous telemetry events
By default, Netdata collects anonymous usage information from the open-source Netdata Agent. For events like start, stop, crash, etc., we use our own cloud function in GCP. For frontend telemetry on the dashboard itself, the dashboard loads third-party services: PostHog for product analytics, Google Tag Manager, Reo.dev and Sentry for error reporting.
We are strongly committed to your data privacy.
We use the statistics gathered from this information for two purposes:
-
Quality assurance, to help us understand if Netdata behaves as expected, and to help us classify repeated issues with certain distributions or environments.
-
Usage statistics, to help us interpret how people use the Netdata Agent in real-world environments, and to help us identify how our development/design decisions influence the community.
Netdata collects usage information via two different channels:
- Agent dashboard: When you access an Agent's dashboard, it loads PostHog, Google Tag Manager, Reo.dev and Sentry, which send product usage events and error reports.
- Agent backend: The
netdatadaemon executes theanonymous-statistics.shscript when Netdata starts, stops cleanly, or fails.
What data is collectedβ
Agent Dashboard - third-party servicesβ
When you access an Agent dashboard by visiting http://NODE:19999, and telemetry is not opted out, the dashboard loads these services in your browser:
| Service | What it is used for |
|---|---|
| PostHog | Product usage events (page views, feature use) |
| Google Tag Manager | Marketing and usage tags |
| Reo.dev | Developer activity analytics |
| Sentry | Error and crash reports from the dashboard |
When you sign in to Netdata Cloud from the dashboard, the product usage events are associated with your Netdata Cloud account.
The dashboard loads these services only when the Agent's anonymous_statistics setting is true. The value of this setting is controlled via the opt-out mechanism.
Agent Backend - Anonymous Statistics Scriptβ
Every time the daemon is started or stopped, and every time a fatal condition is encountered, Netdata uses the anonymous statistics script to collect system information and send it to the Netdata telemetry cloud function via an HTTPS call.
Information collected for all events:
- Netdata version, build information, release channel, install type
- OS name, version, ID, and detection method
- Kernel name, version, and architecture
- Virtualization and containerization technology
- System CPU information (model, vendor, frequency, core count)
- System disk and RAM information (total sizes)
- Netdata configuration (streaming, memory mode, web enabled, HTTPS, etc.)
- Alert counts (normal, warning, critical)
- Chart and metric counts
- Collector information
- Cloud connection status and availability
- Streaming/mirroring configuration
For FATAL events only:
The FATAL event sends the Netdata process and thread name, along with the source code function, source code filename, and source code line number of the fatal error.
To see exactly what and how is collected, you can review the script template src/daemon/anonymous-statistics.sh.in. The template is converted to a bash script called anonymous-statistics.sh, installed under the Netdata plugins directory, which is usually /usr/libexec/netdata/plugins.d.
Quick Decision Guideβ
What's your installation type?
π§ Linux (standard) β Use Method 1 (File-based)
π₯οΈ Windows β Use Method 2 (Windows-specific)
π³ Docker β Use Method 3 (Environment variable)
π¦ Manual/Offline β Use Method 1 (File-based)
π· FreeBSD β Use Method 1 (File-based)
All opt-out methods prevent:
- The daemon from executing the anonymous statistics script
- The dashboard from loading PostHog, Google Tag Manager, Reo.dev and Sentry, so it sends them no data
When opt-out is enabled, the anonymous statistics script exits immediately without sending any data.
Opt-out Methodsβ
Method 1: Create opt-out file (Linux/macOS/FreeBSD)
When to use: Standard Linux installations, FreeBSD, manual installations, macOS, or offline setups.
Steps:
- Navigate to your Netdata configuration directory
- Create an empty file called
.opt-out-from-anonymous-statistics
# Linux
touch /etc/netdata/.opt-out-from-anonymous-statistics
# FreeBSD
touch /usr/local/etc/netdata/.opt-out-from-anonymous-statistics
This method works for all installation types including FreeBSD, manual, offline, and macOS installations. The file simply needs to existβthe content doesn't matter.
Method 2: Windows
When to use: Windows Agent installations.
On Windows, the Netdata configuration directory is located at C:\Program Files\Netdata\etc\netdata.
Option A: Create opt-out file
Run PowerShell as Administrator and execute:
New-Item -Path "C:\Program Files\Netdata\etc\netdata\.opt-out-from-anonymous-statistics" -ItemType File -Force
Option B: Set environment variable
Run PowerShell as Administrator and execute:
[Environment]::SetEnvironmentVariable("DISABLE_TELEMETRY", "1", "Machine")
Restart-Service -Name Netdata
After setting the environment variable, restart the Netdata service for the changes to take effect.
Method 3: Docker
When to use: Container-based deployments.
Set the DISABLE_TELEMETRY environment variable when creating the container:
docker run -e DISABLE_TELEMETRY=1 ...
Or using Docker Compose:
environment:
- DISABLE_TELEMETRY=1
You can also use DO_NOT_TRACK=1 as an alternative to DISABLE_TELEMETRY=1.
See the Docker installation guide for complete configuration.
Method 4: Installer scripts
When to use: Initial installation or manual updates.
Pass the --disable-telemetry flag to any installer script:
./netdata-installer.sh --disable-telemetry
Or export the environment variable before running the installer:
export DISABLE_TELEMETRY=1
./kickstart.sh
You can also use DO_NOT_TRACK=1 as an alternative to DISABLE_TELEMETRY=1 when using Netdata installer scripts.
See the installation documentation for available installer scripts.
Installation-specific pathsβ
| Installation Type | Configuration Directory |
|---|---|
| Linux (standard) | /etc/netdata |
| Windows | C:\Program Files\Netdata\etc\netdata |
| Docker | N/A (use environment variable) |
| macOS (Homebrew) | /usr/local/etc/netdata |
| macOS (other) | /etc/netdata |
| FreeBSD | /usr/local/etc/netdata |
Verificationβ
To confirm that telemetry is disabled:
- Check that the
.opt-out-from-anonymous-statisticsfile exists in your config directory, OR - Verify that the
DISABLE_TELEMETRYenvironment variable is set in the environment used to start the Netdata daemon
If you used DO_NOT_TRACK=1 with Docker or a Netdata installer script, confirm that it resulted in the .opt-out-from-anonymous-statistics file being created. The Agent dashboard will no longer load PostHog, Google Tag Manager, Reo.dev or Sentry, and the backend statistics script will not execute.
Related documentationβ
- Installation methods - Complete installation guides
- Docker installation - Container-specific setup
- Windows installation - Windows Agent setup
Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.