Collector configuration
Find available collectors in the Collecting Metrics guide and on our Integrations page.
Each collector's documentation includes detailed setup instructions and configuration options. Most collectors either work automatically without configuration or require minimal setup to begin collecting data.
Info
Enable and configure Go collectors directly through the UI using the Dynamic Configuration Manager.
Enable or disable Collectors and Plugins
Most collectors and plugins are enabled by default. You can selectively disable them to optimize performance.
To disable plugins:
- Open
netdata.confusingedit-config. - Navigate to the
[plugins]section - Uncomment the relevant line and set it to
no
[plugins]
proc = yes
python.d = no
To disable specific collectors:
- Open the corresponding plugin configuration file:
bash sudo ./edit-config go.d.conf - Uncomment the collector's line and set it to
no:yaml modules: xyz_collector: no - Restart the Agent after making changes.
Adjust data collection frequency
You can modify how often collectors gather metrics to optimize CPU usage. This can be done globally or for specific collectors.
Global
- Open
netdata.confusingedit-config. Set the
update everyvalue (default is1, meaning one-second intervals):text [global] update every = 2Restart the Agent after making changes.
Specific Plugin or Collector
For Plugins:
- Open
netdata.confusingedit-config. Locate the plugin's section and set its frequency:
[plugin:apps] update every = 5Restart the Agent after making changes.
For Collectors:
Each collector has its own configuration format and options. Refer to the collector's documentation for specific instructions on adjusting its data collection frequency.
Troubleshoot a collector
- Navigate to the plugins directory. If not found, check the
plugins directorysetting innetdata.conf.bash cd /usr/libexec/netdata/plugins.d/ - Switch to the netdata user.
bash sudo su -s /bin/bash netdata - Run debug mode
# Go collectors
./go.d.plugin -d -m <MODULE_NAME>
# Python collectors
./python.d.plugin <MODULE_NAME> debug trace
# Bash collectors
./charts.d.plugin debug 1 <MODULE_NAME>
- Analyze output
The debug output will show:
- Configuration issues
- Connection problems
- Permission errors
- Other potential failures
Need help interpreting the results? Join our Discord community for expert assistance.