Skip to content

E2E Dogstatsd validation#3033

Merged
tbavelier merged 3 commits into
mainfrom
tbavelier/e2e-dsd-workload-validation
May 21, 2026
Merged

E2E Dogstatsd validation#3033
tbavelier merged 3 commits into
mainfrom
tbavelier/e2e-dsd-workload-validation

Conversation

@tbavelier

Copy link
Copy Markdown
Member

What does this PR do?

  • Adds DSD clients for DSD e2e tests and assert metrics are collected

Motivation

  • Greater functional coverage

Additional Notes

Anything else we should know when reviewing?

Minimum Agent Versions

Are there minimum versions of the Datadog Agent and/or Cluster Agent required?

  • Agent: vX.Y.Z
  • Cluster Agent: vX.Y.Z

Describe your test plan

Write there any instructions and details you may have to test your PR.

Checklist

  • PR has at least one valid label: bug, enhancement, refactoring, documentation, tooling, and/or dependencies
  • PR has a milestone or the qa/skip-qa label
  • All commits are signed (see: signing commits)

tbavelier and others added 2 commits May 21, 2026 12:09
…narios

Add a lightweight Python-based sender workload for each DSD transport:
- dsd-udp-sender: Deployment that emits e2e.dsd.udp.counter via UDP to
  the node's hostIP:8125 (used by both UDP with/without ADP subtests)
- dsd-uds-sender: Deployment that emits e2e.dsd.uds.counter via Unix
  DGRAM socket at /var/run/datadog/dsd.socket (used by both UDS
  with/without ADP subtests)

Each DSD subtest now:
1. Deploys the relevant sender alongside the DatadogAgent
2. Flushes the fakeintake after provisioning to start from a clean slate
3. Verifies pod spec as before
4. Waits up to 3 minutes for the DSD metric to appear in the fakeintake,
   confirming the full path from workload → agent/ADP → fakeintake works

Co-Authored-By: Claude Sonnet 4.6 (1M context) <[email protected]>
@datadog-datadog-prod-us1

This comment has been minimized.

@codecov-commenter

codecov-commenter commented May 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 42.24%. Comparing base (efb068e) to head (ba5982e).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #3033   +/-   ##
=======================================
  Coverage   42.24%   42.24%           
=======================================
  Files         337      337           
  Lines       28952    28952           
=======================================
  Hits        12230    12230           
  Misses      15917    15917           
  Partials      805      805           
Flag Coverage Δ
unittests 42.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update efb068e...ba5982e. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tbavelier
tbavelier marked this pull request as ready for review May 21, 2026 12:34
@tbavelier
tbavelier requested a review from a team May 21, 2026 12:34
spec:
containers:
- name: sender
image: public.ecr.aws/docker/library/python:3-alpine

@Mathew-Estafanous Mathew-Estafanous May 21, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it ok to rely on an external registry here? Should an internal registry be used instead? I know our datadog agent e2e framework pull from internal registries to avoid rate limiting or third party issues.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's the pattern we use, these tests are ran on kind inside AWS EC2, so the rate limit of 10 pulls/second is more than enough for our use case and no need to setup credentials or anything

@tbavelier
tbavelier merged commit 03e4b46 into main May 21, 2026
39 checks passed
@tbavelier
tbavelier deleted the tbavelier/e2e-dsd-workload-validation branch May 21, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants