Docker Engine icon

Docker Engine

Docker Engine

Plugin: go.d.plugin Module: docker_engine


This collector monitors the activity and health of Docker Engine and Docker Swarm.

The built-in Prometheus exporter is used to get 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


It discovers instances running on localhost by attempting to connect to a known Docker TCP socket:


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.



Enable built-in Prometheus exporter

To enable built-in Prometheus exporter, follow the official documentation.



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


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

Name Description Default Required
update_every Data collection frequency. 1 no
autodetection_retry Recheck interval in seconds. Zero means no recheck will be scheduled. 0 no
url Server URL. yes
username Username for basic HTTP authentication. no
password Password for basic HTTP authentication. no
proxy_url Proxy URL. no
proxy_username Username for proxy basic HTTP authentication. no
proxy_password Password for proxy basic HTTP authentication. no
timeout HTTP request timeout. 1 no
method HTTP request method. GET no
body HTTP request body. no
headers HTTP request headers. no
not_follow_redirects Redirect handling policy. Controls whether the client follows redirects. no no
tls_skip_verify Server certificate chain and hostname validation policy. Controls whether the client performs this check. no no
tls_ca Certification authority that the client uses when verifying the server’s certificates. no
tls_cert Client TLS certificate. no
tls_key Client TLS key. no



A basic example configuration.

  - name: local

HTTP authentication

Basic HTTP authentication.

  - name: local
    username: username
    password: password

HTTPS with self-signed certificate

Configuration with enabled HTTPS and self-signed 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

  - name: remote


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 Docker Engine instance

These metrics refer to the entire monitored application.

This scope has no labels.


Metric Dimensions Unit
docker_engine.engine_daemon_container_actions changes, commit, create, delete, start actions/s
docker_engine.engine_daemon_container_states_containers running, paused, stopped containers
docker_engine.builder_builds_failed_total build_canceled, build_target_not_reachable_error, command_not_supported_error, dockerfile_empty_error, dockerfile_syntax_error, error_processing_commands_error, missing_onbuild_arguments_error, unknown_instruction_error fails/s
docker_engine.engine_daemon_health_checks_failed_total fails events/s
docker_engine.swarm_manager_leader is_leader bool
docker_engine.swarm_manager_object_store nodes, services, tasks, networks, secrets, configs objects
docker_engine.swarm_manager_nodes_per_state ready, down, unknown, disconnected nodes
docker_engine.swarm_manager_tasks_per_state running, failed, ready, rejected, starting, shutdown, new, orphaned, preparing, pending, complete, remove, accepted, assigned tasks


There are no alerts configured by default for this integration.


Debug Mode

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

Getting Logs

If you’re encountering problems with the docker_engine 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 docker_engine

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

Get Netdata

Sign up for free

Want to see a demonstration of Netdata for multiple use cases?

Go to Live Demo