Datadog Process Monitoring allows for real-time visibility of the most granular elements in a deployment. Taking inspiration from bedrock tools like
htop, this centralized view, combined with existing tagging capabilities, allows you to understand what is going on at any level of your system and drill all the way down into the most fine details.
Live Processes has been introduced in Datadog Agent version 5.16.0.
Refer to the instructions for standard Agent installation for platform-specific details.
Once the Datadog Agent is installed, enable Live Processes collection by editing the configuration file at :
and adding the following line to the
After configuration is complete, restart the Agent.
Note: To collect container information in the standard install, the dd-agent user needs to have permissions to access docker.sock.
Update to the Datadog Agent image version 5.16.0 or above:
$ docker pull datadog/docker-dd-agent
Follow the instructions for docker-dd-agent, passing in the following attributes, in addition to any other custom settings as appropriate:
-v /etc/passwd:/etc/passwd:ro -e DD_PROCESS_AGENT_ENABLED=true
In the dd-agent.yaml manifest used to create the daemonset, add the following environmental variables, volume mount, and volume:
env: - name: DD_PROCESS_AGENT_ENABLED value: "true" volumeMounts: - name: passwd mountPath: /etc/passwd readOnly: true volumes: - hostPath: path: /etc/passwd name: passwd
Processes and containers are by their nature extremely high cardinality objects. Our fuzzy string search gives you a view into exactly what you want. Below is our Demo environment, filtered with the string
/9. has matched in the command path, and
postgres matches the command itself.
Making sense of hundreds of thousands or millions of processes can seem overwhelming! Using tagging makes navigation easy. In addition to all existing host-level tags, processes are tagged by
First, we can filter down to role:McNulty-Query, which is our front end query service, in order to narrow our search. Then we can search for our NGINX master processes, and pivot the table by Availability-Zone, to be confident about that service staying highly available.
Here, I am checking the Elasticsearch processes for an individual feature team. I’ve also added metrics for voluntary and involuntary context switches, available in the gear menu on the upper-right of the table.
Below, we have searched for ssh processes and pivoted by
user to understand who is logged into which hosts.
Ok, so I guess that one is less exciting after redaction!
Live Processes adds extra visibility to your container deployments. The Live Containers feature gives you a similarly comprehensive view of your container and orcestrator environment. When Live Processes is enabled, the process tree for each container is included in the container inspection panel on that page.
While actively working with the Live Processes, metrics are collected at 2s resolution. This is very important for highly volatile metrics such as CPU. In the background, for historical context, metrics are collected at 10s resolution.
Collection of open files and current working directory is limited based on the level of privilege of the user running dd-process-agent. In the event that dd-process-agent is able to access these fields, they are collected automatically.
Real-time (2s) data collection is turned off after 30 minutes. To resume real-time collection, refresh the page.
The Process Agent is available for the default Debian docker-dd-agent image only. It is not included in the Alpine image.
In container deployments, the
/etc/passwd file mounted into the docker-dd-agent is necessary to collect usernames for each process. This is a public file and the Process Agent does not use any fields except the username. All features except the
user metadata field will function without access to this file.
passwdfile and will not perform username resolution for users created within containers.
Additional helpful documentation, links, and articles: