The daemon configuration file is read from
Depending on your installation method, Netdata will have been installed either directly under
/, or under
/opt/netdata. The paths mentioned here and in the documentation in general assume that your installation is under
/. If it is not, you will find the exact same paths under
/opt/netdata as well. (i.e.
/etc/netdata will be
This config file is not needed by default. Netdata works fine out of the box without it. But it does allow you to adapt the general behavior of Netdata, in great detail. You can find all these settings, with their default values, by accessing the URL
https://netdata.server.hostname:19999/netdata.conf. For example check the configuration file of netdata.firehol.org. HTTP access to this file is limited by default to private IPs, via the web server access lists.
netdata.conf has sections stated with
[section]. You will see the following sections:
[global]to configure the Netdata daemon.
[web]to configure the web server.
[plugins]to configure which collectors to use and PATH settings.
[health]to configure general settings for health monitoring
[registry]for the Netdata registry.
[backend]to set up streaming and replication options.
[statsd]for the general settings of the stats.d.plugin.
[plugin:NAME]sections for each collector plugin, under the comment Per plugin configuration.
[CHART_NAME]sections for each chart defined, under the comment Per chart configuration.
The configuration file is a
name = value dictionary. Netdata will not complain if you set options unknown to it. When you check the running configuration by accessing the URL
/netdata.conf on your Netdata server, Netdata will add a comment on settings it does not currently use.
netdata.conf has been modified, Netdata needs to be restarted for changes to apply:
sudo service netdata restart
If the above does not work, try the following:
sudo killall netdata; sleep 10; sudo netdata
Please note that your data history will be lost if you have modified
history parameter in section
[global] section options¶
|process scheduling policy||
||See Netdata process scheduling policy|
||See OOM score|
|glibc malloc arena max for plugins||
||See Virtual memory.|
|glibc malloc arena max for Netdata||
||See Virtual memory.|
|hostname||auto-detected||The hostname of the computer running Netdata.|
||The number of entries the
||The frequency in seconds, for data collection. For more information see Performance.|
||The directory configuration files are kept.|
|stock config directory||
||The directory in which the log files are kept.|
|web files directory||
||The directory the web static files are kept.|
||The directory the memory database will be stored if and when Netdata exits. Netdata will re-read the database when it will start again, to continue from the same point.|
||Contains the alarm log and the Netdata instance guid.|
||Contains the db files for the collected metrics|
||The directory plugin programs are kept. This setting supports multiple directories, space separated. If any directory path contains spaces, enclose it in single or double quotes.|
||When set to
||This is used in docker environments where /proc, /sys, etc have to be accessed via another path. You may also have to set SYS_PTRACE capability on the docker for this work. Check issue 43.|
|memory deduplication (ksm)||
||When set to
|TZ environment variable||
||Where to find the timezone|
|timezone||auto-detected||The timezone retrieved from the environment variable|
||Bitmap of debug options to enable. For more information check Tracing Options.|
||The filename to save debug information. This file will not be created if debugging is not enabled. You can also set it to
||The filename to save error messages for Netdata daemon and all plugins (
||The filename to save the log of web clients accessing Netdata charts. You can also set it to
|errors flood protection period||
||UNUSED - Length of period (in sec) during which the number of errors should not exceed the
|errors to trigger flood protection||
||UNUSED - Number of errors written to the log in
|run as user||
||The user Netdata will run as.|
|pthread stack size||auto-detected|
|cleanup obsolete charts after seconds||
||See monitoring ephemeral containers, also sets the timeout for cleaning up obsolete dimensions|
|gap when lost iterations above||
|cleanup orphan hosts after seconds||
||How long to wait until automatically removing from the DB a remote Netdata host (slave) that is no longer sending data.|
|delete obsolete charts files||
||See monitoring ephemeral containers, also affects the deletion of files for obsolete dimensions|
|delete orphan hosts files||
|enable zero metrics||
[web] section options¶
Refer to the web server documentation
[plugins] section options¶
In this section you will see be a boolean (
no) option for each plugin (e.g. tc, cgroups, apps, proc etc.). Note that the configuration options in this section for the orchestrator plugins
node.d control all the modules written for that orchestrator. For instance, setting
python.d = no means that all Python modules under
collectors/python.d.plugin will be disabled.
Additionally, there will be the following options:
|PATH environment variable||
|PYTHONPATH environment variable||Used to set a custom python path|
|enable running new plugins||
||When set to
|check for new plugins every||60||The time in seconds to check for new plugins in the plugins directory. This allows having other applications dynamically creating plugins for Netdata.|
||This is a debugging plugin for the internal latency|
[health] section options¶
This section controls the general behavior of the health monitoring capabilities of Netdata.
Specific alarms are configured in per-collector config files under the
health.d directory. For more info, see health monitoring.
Alarm notifications are configured in
|in memory max health log entries||1000||Size of the alarm history held in RAM|
|script to execute on alarm||
||The script that sends alarm notifications. Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under
|stock health configuration directory||
||Contains the stock alarm configuration files for each collector|
|health configuration directory||
||The directory containing the user alarm configuration files, to override the stock configurations|
|run at least every seconds||
||Controls how often all alarm conditions should be evaluated.|
|postpone alarms during hibernation for seconds||
||Prevents false alarms. May need to be increased if you get alarms during hibernation.|
|rotate log every lines||2000||Controls the number of alarm log entries stored in
[registry] section options¶
To understand what this section is and how it should be configured, please refer to the registry documentation.
Refer to the streaming and replication documentation.
Per plugin configuration¶
The configuration options for plugins appear in sections following the pattern
Most internal plugins will provide additional options. Check Internal Plugins for more information.
Please note, that by default Netdata will enable monitoring metrics for disks, memory, and network only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Use
yes instead of
auto in plugin configuration sections to enable these charts permanently. You can also set the
enable zero metrics option to
yes in the
[global] section which enables charts with zero metrics for all internal Netdata plugins.
External plugins will have only 2 options at
|update every||the value of
||The frequency in seconds the plugin should collect values. For more information check Performance.|
|command options||empty||Additional command line options to pass to the plugin.|
External plugins that need additional configuration may support a dedicated file in
/etc/netdata. Check their documentation.
Per chart configuration¶
In this section you will find a separate subsection for each chart shown on the dashboard. You can control all aspects of a specific chart here. You can understand what each option does by reading how charts are defined. If you don’t know how to find the name of a chart, you can learn about it here.