Skip to main content

Netatmo sensors

Plugin: go.d.plugin Module: prometheus


Keep an eye on Netatmo smart home device metrics for efficient home automation and energy management.

Metrics are gathered by periodically sending HTTP requests to Netatmo exporter.

This collector is supported on all platforms.

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

Default Behavior


By default, it detects instances running on the local host by trying to connect to known ports that are allocated to exporters.


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.


This collector has built-in grouping logic based on the type of metrics.

Gaugefor each label setone, the metric nameabsolute
Counterfor each label setone, the metric nameincremental
Summary (quantiles)for each label set (excluding 'quantile')for each quantileabsolute
Summary (sum and count)for each label setthe metric nameincremental
Histogram (buckets)for each label set (excluding 'le')for each bucketincremental
Histogram (sum and count)for each label setthe metric nameincremental

Untyped metrics (have no '# TYPE') processing:

  • As Counter or Gauge depending on pattern match when 'fallback_type' is used.
  • As Counter if it has suffix '_total'.
  • As Summary if it has 'quantile' label.
  • As Histogram if it has 'le' label.

The rest are ignored.


There are no alerts configured by default for this integration.



Install Exporter

Install Netatmo exporter by following the instructions mentioned in the exporter README.



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


The following options can be defined globally: update_every, autodetection_retry.

Config options
update_everyData collection frequency.10no
autodetection_retryRecheck interval in seconds. Zero means no recheck will be scheduled.0no
urlServer URL.yes
selectorTime series selector (filter).no
fallback_typeTime series selector (filter).no
max_time_seriesGlobal time series limit. If an endpoint returns number of time series > limit the data is not processed.2000no
max_time_series_per_metricTime series per metric (metric name) limit. Metrics with number of time series > limit are skipped.200no
timeoutHTTP request timeout.10no
usernameUsername for basic HTTP
passwordPassword for basic HTTP
proxy_usernameUsername for proxy basic HTTP
proxy_passwordPassword for proxy basic HTTP
methodHTTP request method.GETno
bodyHTTP request
headersHTTP request
not_follow_redirectsRedirect handling policy. Controls whether the client follows redirects.nono
tls_skip_verifyServer certificate chain and hostname validation policy. Controls whether the client performs this check.nono
tls_caCertification authority that the client uses when verifying the server's
tls_certClient TLS
tls_keyClient TLS

This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.

  • Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
  • Pattern syntax: selector.
  • Option syntax:
- pattern1
- pattern2
- pattern3
- pattern4

This option allows you to process Untyped metrics as Counter or Gauge instead of ignoring them.

- metric_name_pattern1
- metric_name_pattern2
- metric_name_pattern3
- metric_name_pattern4



Note: Change the port of the monitored application on which it provides metrics.

A basic example configuration.

- name: local

Read metrics from a file

An example configuration to read metrics from a file.

# use "file://" scheme
- name: myapp
url: file:///opt/metrics/myapp/metrics.txt

HTTP authentication

Note: Change the port of the monitored application on which it provides metrics.

Basic HTTP authentication.

- name: local
username: username
password: password

HTTPS with self-signed certificate

Note: Change the port of the monitored application on which it provides metrics.

Do not validate server certificate chain and hostname.

- name: local
tls_skip_verify: yes


Note: When you define multiple jobs, their names must be unique. Note: Change the port of the monitored application on which it provides metrics.

Collecting metrics from local and remote instances.

- name: local

- name: remote


Debug Mode

To troubleshoot issues with the prometheus collector, run the go.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 go.d.plugin to debug the collector:

    ./go.d.plugin -d -m prometheus

Getting Logs

If you're encountering problems with the prometheus 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 prometheus

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 prometheus /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 prometheus

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