Download and install the package
Download docker-module.json and checksums.txt from the same module release and verify SHA-256. Upload the JSON through Modules and assign Docker to a server. Create separate assignments for other nodes.
The package contains Linux amd64, Linux arm64 and Windows amd64 collectors. Go and Node.js are not needed to execute them. The collector inherits the agent’s permissions, so use a trusted source.
sha256sum docker-module.json
# PowerShell:
Get-FileHash ./docker-module.json -Algorithm SHA256Configure the selected Docker Engine
Leave socket empty for the platform default: /var/run/docker.sock on Linux or \\.\pipe\docker_engine on Windows. For rootless Docker, specify the user’s socket.
The agent service must be able to access that socket or pipe. Docker daemon access is privileged even though this collector only reads data. Do not publish Docker API to the Internet for this module.
Interpret total CPU and total memory
CPU uses two statistics passes one second apart. 100% represents one fully occupied core, so values above 100% are possible. Total CPU describes containers, not every host process.
Memory total sums running-container working-set memory rather than installed host RAM. Linux file cache is excluded. If a running container metric is unavailable, its corresponding total stays unknown; a dash does not mean zero.
Understand network, logs and history
Module network values are cumulative received and transmitted byte counters, not current rates. Use the main Pulse network view for host interface rates.
Set logContainer to a container ID of at least 12 characters. The module reads the latest 50 lines rather than a full archive. Charts keep recent measurements in the current view. The container list is limited to 100; truncated indicates that limit.
Diagnose each server independently
For error, check Engine availability, the socket or pipe path, service permissions and container ID. Logging drivers can limit logs. unsupported means a suitable platform binary is absent.
Upload a new package version for upgrades and verify every assigned node. Do not replace a released version’s contents: the monitor rejects conflicting binaries under the same ID and version.
These instructions are based on the release documentation linked below. Commands containing example.com or SERVER_ID are templates: substitute values from your own dashboard. Check the matching release documentation when upgrading.