Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Datadog Agent stops processing traces and spans over time #33071

Open
ngoduykhanh opened this issue Jan 17, 2025 · 1 comment
Open

[BUG] Datadog Agent stops processing traces and spans over time #33071

ngoduykhanh opened this issue Jan 17, 2025 · 1 comment

Comments

@ngoduykhanh
Copy link

ngoduykhanh commented Jan 17, 2025

Agent Environment

  • ECS Fargate
  • Datadog agent deployed as a sidecar
  • Use latest version (7.61.0) via image public.ecr.aws/datadog/agent:latest

Notable Env vars:

  • DD_APM_ENABLED: true
  • ECS_FARGATE: true
  • DD_APM_MAX_TPS: 100
  • DD_APM_ERROR_TPS: 1000

Describe what happened:

The number of traces sent to Datadog from the Agent has significantly reduced over time. Whenever this happened, I redeployed the ECS task and it started working again. The number of ingested/indexed traces increased. But after 2-3 hours, the issue happened again.

Looking at the graphs, it seems to me, that for some reason, the Datadog agent stopped processing the traces although it received the traces from the application.

Image

express.request trace metric
Image

Describe what you expected:

Datadog agent processes all the traces it receives and I don't see a drop in traces on the Datadog dashboard.

Steps to reproduce the issue:

Additional environment details (Operating System, Cloud provider, etc):

  • AWS ECS Fargate.
  • The task's container resource usage looks good. There was no issue with CPU/memory allocation.
@ajgajg1134
Copy link
Contributor

Hello! Thanks for opening an issue, to better investigate this for your specific setup / traffic pattern could you please open a support ticket? This will allow us to gather more specific information and determine what's going on here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants