Skip to content

Conversation

@KSerrania
Copy link
Contributor

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

@KSerrania
Copy link
Contributor Author

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

@github-actions github-actions bot added short review PR is simple enough to be reviewed quickly team/agent-devx team/agent-delivery labels Oct 1, 2025
@dd-devflow-routing-codex
Copy link

View all feedbacks in Devflow UI.

2025-10-01 08:39:10 UTC ℹ️ Start processing command /trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on
If you need support, contact us on Slack #devflow!


2025-10-01 08:39:26 UTC ℹ️ Branch synced on Gitlab

Branch kserrania/sint-4056-testing was out-of-sync on Gitlab - it has been resynced

If you need support, contact us on Slack #devflow!


2025-10-01 08:42:28 UTC 🚨 Devflow

Post "https://gitlab.ddbuild.io/api/v4/projects/DataDog%2Fdatadog-agent/pipeline": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Details
child workflow execution error (type: devtools.Devtools_TriggerCiFromPr, workflowID: 6c9b0f24-8681-47d9-93a2-f179f10fafbb_26, runID: eb40dd0e-fafe-4365-86e0-16c177a76bc7, initiatedEventID: 26, startedEventID: 27): child workflow execution error (type: devtools.Devtools_TriggerCi, workflowID: eb40dd0e-fafe-4365-86e0-16c177a76bc7_14, runID: a76633c6-6df4-4be4-8e42-2ffe997c0bd4, initiatedEventID: 14, startedEventID: 15): activity error (type: gitlab.GitlabService_CreatePipeline, scheduledEventID: 55, startedEventID: 56, identity: ): activity ScheduleToClose timeout (type: ScheduleToClose): Post "https://gitlab.ddbuild.io/api/v4/projects/DataDog%2Fdatadog-agent/pipeline": context deadline exceeded (Client.Timeout exceeded while awaiting headers) (type: Error, retryable: true): context deadline exceeded (Client.Timeout exceeded while awaiting headers) (type: timeoutError, retryable: true)

If you need support, contact us on Slack #devflow with those details!

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Oct 1, 2025

Gitlab CI Configuration Changes

Modified Jobs

.agent_release_management_trigger
  .agent_release_management_trigger:
    dependencies: []
    image: registry.ddbuild.io/ci/datadog-agent-buildimages/linux$CI_IMAGE_LINUX_SUFFIX:$CI_IMAGE_LINUX
    script:
    - curl --retry 5 -sSL "https://dd-package-tools.s3.amazonaws.com/dd-pkg/${DD_PKG_VERSION}/dd-pkg_Linux_${DD_PKG_ARCH}.tar.gz"
      | tar -xz -C /usr/local/bin dd-pkg
    - dd-pkg version
    - RELEASE_VERSION="$(dda inv agent.version --url-safe --omnibus-format --pipeline-id
      $PARENT_PIPELINE_ID)-1" || exit $?; export RELEASE_VERSION
    - "dd-pkg promote \\\n  --build-pipeline-id $PARENT_PIPELINE_ID \\\n  --release-product\
      \ $RELEASE_PRODUCT \\\n  --key-id $PIPELINE_KEY_ALIAS \\\n  --release-version\
      \ $RELEASE_VERSION \\\n  --target-repo $TARGET_REPO \\\n  --target-channel $BUCKET_BRANCH\
-     \ \\\n  $AUTO_RELEASE \\\n  $FOLLOW"
+     \ \\\n  --target-branch kserrania/sint-4056-testing-keys\n  $AUTO_RELEASE \\\n\
+     \  $FOLLOW"
    stage: trigger_release
    tags:
    - arch:amd64
    - specific:true
    variables:
      DD_PKG_ARCH: x86_64
      RELEASE_PRODUCT: datadog-agent
trigger_auto_staging_release
  trigger_auto_staging_release:
    dependencies: []
    image: registry.ddbuild.io/ci/datadog-agent-buildimages/linux$CI_IMAGE_LINUX_SUFFIX:$CI_IMAGE_LINUX
    rules:
    - if: $CI_COMMIT_TAG =~ /^[0-9]+\.[0-9]+\.[0-9]+-v[0-9]+\.[0-9]+\.[0-9]+(-rc\.[0-9]+){0,1}$/
      when: never
    - when: always
    script:
    - curl --retry 5 -sSL "https://dd-package-tools.s3.amazonaws.com/dd-pkg/${DD_PKG_VERSION}/dd-pkg_Linux_${DD_PKG_ARCH}.tar.gz"
      | tar -xz -C /usr/local/bin dd-pkg
    - dd-pkg version
    - RELEASE_VERSION="$(dda inv agent.version --url-safe --omnibus-format --pipeline-id
      $PARENT_PIPELINE_ID)-1" || exit $?; export RELEASE_VERSION
    - "dd-pkg promote \\\n  --build-pipeline-id $PARENT_PIPELINE_ID \\\n  --release-product\
      \ $RELEASE_PRODUCT \\\n  --key-id $PIPELINE_KEY_ALIAS \\\n  --release-version\
      \ $RELEASE_VERSION \\\n  --target-repo $TARGET_REPO \\\n  --target-channel $BUCKET_BRANCH\
-     \ \\\n  $AUTO_RELEASE \\\n  $FOLLOW"
+     \ \\\n  --target-branch kserrania/sint-4056-testing-keys\n  $AUTO_RELEASE \\\n\
+     \  $FOLLOW"
    stage: trigger_release
    tags:
    - arch:amd64
    - specific:true
    timeout: 2h 30m
    variables:
      AUTO_RELEASE: --auto-release
      DD_PKG_ARCH: x86_64
      FOLLOW: --follow
      RELEASE_PRODUCT: datadog-agent
      TARGET_REPO: staging
trigger_manual_prod_release
  trigger_manual_prod_release:
    dependencies: []
    image: registry.ddbuild.io/ci/datadog-agent-buildimages/linux$CI_IMAGE_LINUX_SUFFIX:$CI_IMAGE_LINUX
    rules:
    - if: $CI_COMMIT_TAG =~ /^[0-9]+\.[0-9]+\.[0-9]+-v[0-9]+\.[0-9]+\.[0-9]+(-rc\.[0-9]+){0,1}$/
      when: never
    - if: $BUCKET_BRANCH != "beta" && $BUCKET_BRANCH != "stable"
      when: never
    - allow_failure: true
      if: $BUCKET_BRANCH != "stable"
      when: manual
    - when: always
    script:
    - curl --retry 5 -sSL "https://dd-package-tools.s3.amazonaws.com/dd-pkg/${DD_PKG_VERSION}/dd-pkg_Linux_${DD_PKG_ARCH}.tar.gz"
      | tar -xz -C /usr/local/bin dd-pkg
    - dd-pkg version
    - RELEASE_VERSION="$(dda inv agent.version --url-safe --omnibus-format --pipeline-id
      $PARENT_PIPELINE_ID)-1" || exit $?; export RELEASE_VERSION
    - "dd-pkg promote \\\n  --build-pipeline-id $PARENT_PIPELINE_ID \\\n  --release-product\
      \ $RELEASE_PRODUCT \\\n  --key-id $PIPELINE_KEY_ALIAS \\\n  --release-version\
      \ $RELEASE_VERSION \\\n  --target-repo $TARGET_REPO \\\n  --target-channel $BUCKET_BRANCH\
-     \ \\\n  $AUTO_RELEASE \\\n  $FOLLOW"
+     \ \\\n  --target-branch kserrania/sint-4056-testing-keys\n  $AUTO_RELEASE \\\n\
+     \  $FOLLOW"
    stage: trigger_release
    tags:
    - arch:amd64
    - specific:true
    variables:
      DD_PKG_ARCH: x86_64
      RELEASE_PRODUCT: datadog-agent
      TARGET_REPO: prod

Changes Summary

Removed Modified Added Renamed
0 3 0 0

ℹ️ Diff available in the job log.

@KSerrania KSerrania added changelog/no-changelog qa/no-code-change No code change in Agent code requiring validation labels Oct 1, 2025
@cit-pr-commenter
Copy link

cit-pr-commenter bot commented Oct 1, 2025

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 3d0d51d1-5a8f-4e78-8c09-03bbeef29a5e

Baseline: 105c432
Comparison: 7ccd105
Diff

Optimization Goals: ❌ Regression(s) detected

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_logs % cpu utilization +5.33 [+2.51, +8.15] 1 Logs bounds checks dashboard

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI trials links
docker_containers_cpu % cpu utilization +2.03 [-1.39, +5.44] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_logs % cpu utilization +5.33 [+2.51, +8.15] 1 Logs bounds checks dashboard
docker_containers_cpu % cpu utilization +2.03 [-1.39, +5.44] 1 Logs
quality_gate_metrics_logs memory utilization +1.87 [+1.67, +2.08] 1 Logs bounds checks dashboard
ddot_metrics_sum_cumulative memory utilization +0.51 [+0.40, +0.63] 1 Logs
ddot_metrics memory utilization +0.39 [+0.22, +0.56] 1 Logs
tcp_syslog_to_blackhole ingress throughput +0.24 [+0.18, +0.29] 1 Logs
quality_gate_idle_all_features memory utilization +0.22 [+0.18, +0.26] 1 Logs bounds checks dashboard
uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization +0.16 [+0.12, +0.20] 1 Logs
otlp_ingest_metrics memory utilization +0.09 [-0.02, +0.21] 1 Logs
file_to_blackhole_1000ms_latency egress throughput +0.08 [-0.49, +0.65] 1 Logs
file_to_blackhole_0ms_latency egress throughput +0.07 [-0.47, +0.62] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.05 [-0.56, +0.67] 1 Logs
file_to_blackhole_100ms_latency egress throughput +0.02 [-0.54, +0.58] 1 Logs
ddot_logs memory utilization +0.02 [-0.05, +0.08] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.01 [-0.24, +0.27] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.01, +0.01] 1 Logs
ddot_metrics_sum_delta memory utilization -0.11 [-0.27, +0.05] 1 Logs
file_tree memory utilization -0.23 [-0.27, -0.19] 1 Logs
ddot_metrics_sum_cumulativetodelta_exporter memory utilization -0.29 [-0.48, -0.10] 1 Logs
otlp_ingest_logs memory utilization -0.42 [-0.53, -0.30] 1 Logs
quality_gate_idle memory utilization -0.51 [-0.55, -0.47] 1 Logs bounds checks dashboard
docker_containers_memory memory utilization -0.63 [-0.80, -0.47] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed links
docker_containers_cpu simple_check_run 10/10
docker_containers_memory memory_usage 10/10
docker_containers_memory simple_check_run 10/10
file_to_blackhole_0ms_latency lost_bytes 10/10
file_to_blackhole_0ms_latency memory_usage 10/10
file_to_blackhole_1000ms_latency memory_usage 10/10
file_to_blackhole_100ms_latency lost_bytes 10/10
file_to_blackhole_100ms_latency memory_usage 10/10
file_to_blackhole_500ms_latency lost_bytes 10/10
file_to_blackhole_500ms_latency memory_usage 10/10
quality_gate_idle intake_connections 10/10 bounds checks dashboard
quality_gate_idle memory_usage 10/10 bounds checks dashboard
quality_gate_idle_all_features intake_connections 10/10 bounds checks dashboard
quality_gate_idle_all_features memory_usage 10/10 bounds checks dashboard
quality_gate_logs intake_connections 10/10 bounds checks dashboard
quality_gate_logs lost_bytes 10/10 bounds checks dashboard
quality_gate_logs memory_usage 10/10 bounds checks dashboard
quality_gate_metrics_logs cpu_usage 10/10 bounds checks dashboard
quality_gate_metrics_logs intake_connections 10/10 bounds checks dashboard
quality_gate_metrics_logs lost_bytes 10/10 bounds checks dashboard
quality_gate_metrics_logs memory_usage 10/10 bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

Passed. All Quality Gates passed.

  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Oct 1, 2025

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 893f5ef

Successful checks

Info

Quality gate Delta On disk size (MiB) Delta On wire size (MiB)
agent_deb_amd64 $${+0}$$ $${697.28}$$ < $${703.13}$$ $${+0.01}$$ $${175.48}$$ < $${178.38}$$
agent_deb_amd64_fips $${+0}$$ $${691.77}$$ < $${697.61}$$ $${+0.01}$$ $${174.08}$$ < $${177.15}$$
agent_heroku_amd64 $${0}$$ $${335.96}$$ < $${341.62}$$ $${+0}$$ $${88.95}$$ < $${91.52}$$
agent_msi $${+0}$$ $${989.06}$$ < $${990.42}$$ $${-0.02}$$ $${150.92}$$ < $${152.42}$$
agent_rpm_amd64 $${+0}$$ $${697.27}$$ < $${703.12}$$ $${+0}$$ $${177.76}$$ < $${180.53}$$
agent_rpm_amd64_fips $${+0}$$ $${691.76}$$ < $${697.6}$$ $${+0.02}$$ $${176.22}$$ < $${178.87}$$
agent_rpm_arm64 $${+0}$$ $${683.38}$$ < $${689.82}$$ $${-0.02}$$ $${159.02}$$ < $${162.16}$$
agent_rpm_arm64_fips $${+0}$$ $${678.9}$$ < $${685.08}$$ $${-0.02}$$ $${157.97}$$ < $${161.11}$$
agent_suse_amd64 $${+0}$$ $${697.27}$$ < $${703.12}$$ $${+0}$$ $${177.76}$$ < $${180.53}$$
agent_suse_amd64_fips $${+0}$$ $${691.76}$$ < $${697.6}$$ $${+0.02}$$ $${176.22}$$ < $${178.87}$$
agent_suse_arm64 $${+0}$$ $${683.38}$$ < $${689.82}$$ $${-0.02}$$ $${159.02}$$ < $${162.16}$$
agent_suse_arm64_fips $${+0}$$ $${678.9}$$ < $${685.08}$$ $${-0.02}$$ $${157.97}$$ < $${161.11}$$
docker_agent_amd64 $${+0}$$ $${768.65}$$ < $${774.54}$$ $${-0}$$ $${263.24}$$ < $${266.46}$$
docker_agent_arm64 $${+0}$$ $${778.72}$$ < $${785.2}$$ $${-0.01}$$ $${249.3}$$ < $${252.92}$$
docker_agent_jmx_amd64 $${+0}$$ $${959.52}$$ < $${965.41}$$ $${+0}$$ $${331.86}$$ < $${335.08}$$
docker_agent_jmx_arm64 $${+0}$$ $${958.18}$$ < $${964.66}$$ $${+0.01}$$ $${313.92}$$ < $${317.54}$$
docker_cluster_agent_amd64 $${+0}$$ $${212.92}$$ < $${213.74}$$ $${+0}$$ $${72.23}$$ < $${73.2}$$
docker_cluster_agent_arm64 $${0}$$ $${228.86}$$ < $${229.68}$$ $${+0}$$ $${68.5}$$ < $${69.48}$$
docker_cws_instrumentation_amd64 $${0}$$ $${7.06}$$ < $${7.12}$$ $${+0}$$ $${2.95}$$ < $${3.29}$$
docker_cws_instrumentation_arm64 $${0}$$ $${6.69}$$ < $${6.92}$$ $${-0}$$ $${2.7}$$ < $${3.07}$$
docker_dogstatsd_amd64 $${0}$$ $${38.41}$$ < $${39.3}$$ $${+0}$$ $${14.84}$$ < $${15.76}$$
docker_dogstatsd_arm64 $${-0.06}$$ $${37.05}$$ < $${37.94}$$ $${+0}$$ $${14.29}$$ < $${14.83}$$
dogstatsd_deb_amd64 $${0}$$ $${29.64}$$ < $${30.53}$$ $${-0}$$ $${7.82}$$ < $${8.75}$$
dogstatsd_deb_arm64 $${0}$$ $${28.23}$$ < $${29.12}$$ $${-0}$$ $${6.78}$$ < $${7.71}$$
dogstatsd_rpm_amd64 $${0}$$ $${29.64}$$ < $${30.53}$$ $${+0}$$ $${7.84}$$ < $${8.77}$$
dogstatsd_suse_amd64 $${0}$$ $${29.64}$$ < $${30.53}$$ $${+0}$$ $${7.84}$$ < $${8.77}$$
iot_agent_deb_amd64 $${0}$$ $${54.59}$$ < $${54.97}$$ $${+0}$$ $${13.65}$$ < $${14.45}$$
iot_agent_deb_arm64 $${0}$$ $${51.87}$$ < $${51.9}$$ $${-0}$$ $${11.77}$$ < $${12.63}$$
iot_agent_deb_armhf $${0}$$ $${51.41}$$ < $${51.84}$$ $${+0}$$ $${11.84}$$ < $${12.74}$$
iot_agent_rpm_amd64 $${0}$$ $${54.59}$$ < $${54.97}$$ $${+0}$$ $${13.66}$$ < $${14.47}$$
iot_agent_suse_amd64 $${0}$$ $${54.59}$$ < $${54.97}$$ $${+0}$$ $${13.66}$$ < $${14.47}$$

@dd-octo-sts
Copy link
Contributor

dd-octo-sts bot commented Oct 25, 2025

This pull request has been automatically marked as stale because it has not had activity in the past 15 days.

It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window.

Thank you for your contributions!

@dd-octo-sts dd-octo-sts bot added the stale label Oct 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/no-changelog qa/no-code-change No code change in Agent code requiring validation short review PR is simple enough to be reviewed quickly stale team/agent-delivery team/agent-devx

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants