Skip to main content

Linux Sensors (sysfs)

Plugin: charts.d.plugin Module: sensors


Use this collector when lm-sensors doesn't work on your device (e.g. for RPi temperatures). For all other cases use the Go collector, which supports multiple jobs, is more efficient and performs calculations on top of the kernel provided values."

It will provide charts for all configured system sensors, by reading sensors directly from the kernel. The values graphed are the raw hardware values of the sensors.

This collector is only supported on the following platforms:

  • Linux

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

Default Behavior


By default, the collector will try to read entries under /sys/devices


The default configuration for this integration does not impose any limits on data collection.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.


Metrics grouped by scope.

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

Per sensor chip

Metrics related to sensor chips. Each chip provides its own set of the following metrics.

This scope has no labels.


sensors.power{filename}Watt{filename}Rotations / Minute{filename}Joule


There are no alerts configured by default for this integration.



Install charts.d plugin

If using our official native DEB/RPM packages, make sure netdata-plugin-chartsd is installed.

Enable the sensors collector

The sensors collector is disabled by default. To enable it, use edit-config from the Netdata config directory, which is typically at /etc/netdata, to edit the charts.d.conf file.

cd /etc/netdata   # Replace this path with your Netdata config directory, if different
sudo ./edit-config charts.d.conf

Change the value of the sensors setting to force and uncomment the line. Save the file and restart the Netdata Agent with sudo systemctl restart netdata, or the appropriate method for your system.



The configuration file name for this integration is charts.d/sensors.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 charts.d/sensors.conf


The config file is sourced by the charts.d plugin. It's a standard bash file.

The following collapsed table contains all the options that can be configured for the sensors collector.

Config options
sensors_sys_dirThe directory the kernel exposes sensor data./sys/devicesno
sensors_sys_depthHow deep in the tree to check for sensor data.10no
sensors_source_updateIf set to 1, the script will overwrite internal script functions with code generated ones.1no
sensors_update_everyThe data collection frequency. If unset, will inherit the netdata update frequency.1no
sensors_priorityThe charts priority on the dashboard.90000no
sensors_retriesThe number of retries to do in case of failure before disabling the collector.10no


Set sensors path depth

Set a different sensors path depth

# the directory the kernel keeps sensor data

# how deep in the tree to check for sensor data

# if set to 1, the script will overwrite internal
# script functions with code generated ones
# leave to 1, is faster

# the data collection frequency
# if unset, will inherit the netdata update frequency

# the charts priority on the dashboard

# the number of retries to do in case of failure
# before disabling the module


Debug Mode

To troubleshoot issues with the sensors collector, run the charts.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/
  • Switch to the netdata user.

    sudo -u netdata -s
  • Run the charts.d.plugin to debug the collector:

    ./charts.d.plugin debug 1 sensors

Getting Logs

If you're encountering problems with the sensors collector, follow these steps to retrieve logs and identify potential issues:

  • Run the command specific to your system (systemd, non-systemd, or Docker container).
  • Examine the output for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.

System with systemd

Use the following command to view logs generated since the last Netdata service restart:

journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep sensors

System without systemd

Locate the collector log file, typically at /var/log/netdata/collector.log, and use grep to filter for collector's name:

grep sensors /var/log/netdata/collector.log

Note: This method shows logs from all restarts. Focus on the latest entries for troubleshooting current issues.

Docker Container

If your Netdata runs in a Docker container named "netdata" (replace if different), use this command:

docker logs netdata 2>&1 | grep sensors

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.