Datadog Agent High CPU or Memory Usage

Share
Workaround available Linux, Windows, Kubernetes Updated November 13, 2026Based on 3 user reportsHow we research

Quick answer

Heavy Agent resource use usually comes from a single check, very high log or DogStatsD volume, or APM limits. Capture a profiled flare to find it.

Most likely fix: Find the culprit check

How to fix it

Try these in order — the most common fix is first.

  1. 1. Find the culprit check

    1. Run datadog-agent check <name> -m for suspected integrations
    Did this fix it?
  2. 2. Capture a profile

    1. Run sudo datadog-agent flare --profile 30 during high usage
    2. Send it to Datadog support
    Did this fix it?
  3. 3. Reduce load

    1. Disable unused integrations and scope Autodiscovery
    2. Cut log volume at the source
    Did this fix it?
  4. 4. Fix APM limits

    1. Compare max CPU setting with datadog.trace_agent.cpu_percent
    2. Raise container CPU limit
    Did this fix it?

Symptoms

Agent process consumes unexpected CPU or RAM, or is killed (OOM).

Why it happens

  • Integration returning thousands of metrics
  • Many check instances
  • High log line or DogStatsD volume
  • Windows antivirus interference
  • APM CPU throttling

This guide also covers

  • datadog agent high cpu
  • datadog agent high memory usage

Still not working?

If Datadog keeps failing, you're not alone. See every Datadog problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other Datadog errors

All 10 Datadog errors and fixes →