Datadog Agent High CPU or Memory Usage
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. Find the culprit check
- Run datadog-agent check <name> -m for suspected integrations
Did this fix it?2. Capture a profile
- Run sudo datadog-agent flare --profile 30 during high usage
- Send it to Datadog support
Did this fix it?3. Reduce load
- Disable unused integrations and scope Autodiscovery
- Cut log volume at the source
Did this fix it?4. Fix APM limits
- Compare max CPU setting with datadog.trace_agent.cpu_percent
- 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 usOther Datadog errors
- How to Cancel Datadog Subscription
- Datadog Agent Not Reporting Metrics or Host Missing
- Datadog Duplicate Hosts After AWS Integration
- Datadog Logs Not Showing in Log Explorer
- Datadog APM Traces Not Showing Up
- Datadog Monitor No Data Alerts Not Working
- Why Is My Datadog Bill So High: Custom Metrics
- Datadog Agent 403 API Key Invalid in Kubernetes