Skip to main content


Plugin: go.d.plugin Module: puppet


This collector monitors Puppet metrics, including JVM heap and non-heap memory, CPU usage, and file descriptors.

It uses Puppet's metrics API endpoint /status/v1/services to gather the metrics.

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 Puppet instances running on localhost that are listening on port 8140. On startup, it tries to collect metrics from:


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 Puppet instance

These metrics refer to the entire monitored application.

This scope has no labels.


puppet.jvm_heapcommitted, usedMiB
puppet.jvm_nonheapcommitted, usedMiB
puppet.cpuexecution, GCpercentage


There are no alerts configured by default for this integration.



No action required.



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


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

urlThe base URL where the Puppet instance can be accessed.
timeoutHTTPS request timeout.1no
usernameUsername for basic HTTPS
passwordPassword for basic HTTPS
proxy_usernameUsername for proxy basic HTTPS
proxy_passwordPassword for proxy basic HTTPS
methodHTTPS request method.POSTno
bodyHTTPS request
headersHTTPS 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


Basic with self-signed certificate

Puppet with self-signed TLS certificate.

- name: local
tls_skip_verify: yes


Note: When you define multiple jobs, their names must be unique.

Collecting metrics from local and remote instances.

- name: local
tls_skip_verify: yes

- name: remote
tls_skip_verify: yes


Debug Mode

To troubleshoot issues with the puppet 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 puppet

Getting Logs

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

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

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