Datadog Process Agent Not Reporting — Quick Fix

In this tutorial, you'll learn about Datadog Process Agent Not Reporting. We cover key concepts, practical examples, and best practices.

The Problem

Live processes are not showing up in the Datadog Live Processes view. The process agent may not be running, or process collection may be disabled in the configuration. Container processes may also be missing.

Error example:

process-agent: not running
Process collection is disabled in datadog.yaml
Cannot connect to process agent socket: permission denied

The Fix

Step 1: Enable process collection

WRONG — assuming process collection is enabled by default:

# Process collection is opt-in starting from Datadog Agent 7

RIGHT — enable process collection in datadog.yaml:

# /etc/datadog-agent/datadog.yaml
process_config:
  enabled: "true"
  # For container environments:
  scrub_args: true
  strip_proc_arguments: false

Restart the agent:

systemctl restart datadog-agent

Step 2: Verify the process agent is running

WRONG — checking only the core agent status:

# The core agent can be healthy while the process agent is down

RIGHT — check the process agent status:

datadog-agent status

Output:

===========
Process Agent
===========
  Instance: process-agent
  Status: Running
  Check Runners: 4
  Processes: 0 (no access to other containers)

If the status is "Not running" or "Error," check the process agent log:

journalctl -u datadog-agent-process -n 50

Use DodaTech's Datadog Agent Health Dashboard to monitor all agent sub-processes and their reporting status across your infrastructure.

Prevention Tips

• Enable Process_config.enabled: "true" in agent configuration
• For container environments, mount the /etc/passwd file for user name resolution
• Run the agent with SYS_PTRACE capability for full process details
• Configure scrub_args to hide sensitive command-line arguments
• Use DodaTech's Datadog Agent Config Validator to check process agent settings

Common Mistakes with process agent

1. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
2. Using head and tail instead of pattern matching, causing runtime errors on empty lists
3. Forgetting that lazy evaluation defers computation until the value is forced, causing space leaks with unevaluated thunks

These mistakes appear frequently in real-world DATADOG code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Related: DodaTech's Datadog Agent Tuning Guide provides configuration recommendations for process collection, resource limits, and container integration in various environments.