Re-enable datadog_otel_components_ocb_build with new rules

[liustanley]

What does this PR do?

• Re-enables the datadog_otel_components_ocb_build integration test job that was previously disabled
• Adds a new .on_otel_components_changes rule anchor that runs the job on main merges and on changes to cmd/otel-agent/**/*, comp/otelcol/**/*, or test/otel/testdata/**/*
• Requests higher resources for ocb build to pass reliably (from Request higher resources for ocb build #46176)

Motivation

Describe how you validated your changes

Additional Notes

[agent-platform-auto-pr]

Gitlab CI Configuration Changes

Added Jobs

.on_otel_components_changes

.on_otel_components_changes:
- if: $CI_COMMIT_BRANCH =~ /^mq-working-branch-/
  when: never
- if: $CI_COMMIT_BRANCH == "main"
- changes:
    compare_to: $COMPARE_TO_BRANCH
    paths:
    - cmd/otel-agent/**/*
    - comp/otelcol/**/*
    - test/otel/testdata/**/*
  when: on_success

datadog_otel_components_ocb_build

datadog_otel_components_ocb_build:
  artifacts:
    paths:
    - ocb-output.log
    - otelcol-custom.log
    - flare-info.log
    when: always
  before_script:
  - mkdir -p $GOPATH/pkg/mod/cache && tar xJf modcache.tar.xz -C $GOPATH/pkg/mod/cache
  - rm -f modcache.tar.xz
  image: registry.ddbuild.io/ci/datadog-agent-buildimages/linux$CI_IMAGE_LINUX_SUFFIX:$CI_IMAGE_LINUX
  needs:
  - go_deps
  rules:
  - if: $CI_COMMIT_BRANCH =~ /^mq-working-branch-/
    when: never
  - if: $CI_COMMIT_BRANCH == "main"
  - changes:
      compare_to: $COMPARE_TO_BRANCH
      paths:
      - cmd/otel-agent/**/*
      - comp/otelcol/**/*
      - test/otel/testdata/**/*
    when: on_success
  script:
  - echo "Building custom collector with datadog components"
  - test/otel/testdata/ocb_build_script.sh
  - echo "see artifacts for job logs"
  stage: integration_test
  tags:
  - arch:amd64
  - specific:true
  timeout: 15 minutes
  variables:
    KUBERNETES_CPU_REQUEST: 16
    KUBERNETES_MEMORY_LIMIT: 32Gi
    KUBERNETES_MEMORY_REQUEST: 32Gi

Changes Summary

Removed	Modified	Added	Renamed
0	0	2	0

ℹ️ Diff available in the job log.

[agent-platform-auto-pr]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 715b9fb
📊 Static Quality Gates Dashboard
🔗 SQG Job

31 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	756.128 MiB
✅	agent_deb_amd64_fips	715.036 MiB
✅	agent_heroku_amd64	323.701 MiB
✅	agent_msi	622.218 MiB
✅	agent_rpm_amd64	756.111 MiB
✅	agent_rpm_amd64_fips	715.019 MiB
✅	agent_rpm_arm64	734.365 MiB
✅	agent_rpm_arm64_fips	696.189 MiB
✅	agent_suse_amd64	756.111 MiB
✅	agent_suse_amd64_fips	715.019 MiB
✅	agent_suse_arm64	734.365 MiB
✅	agent_suse_arm64_fips	696.189 MiB
✅	docker_agent_amd64	817.177 MiB
✅	docker_agent_arm64	820.151 MiB
✅	docker_agent_jmx_amd64	1008.089 MiB
✅	docker_agent_jmx_arm64	999.845 MiB
✅	docker_cluster_agent_amd64	190.078 MiB
✅	docker_cluster_agent_arm64	205.502 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.496 MiB
✅	docker_dogstatsd_arm64	36.812 MiB
✅	dogstatsd_deb_amd64	29.716 MiB
✅	dogstatsd_deb_arm64	27.876 MiB
✅	dogstatsd_rpm_amd64	29.716 MiB
✅	dogstatsd_suse_amd64	29.716 MiB
✅	iot_agent_deb_amd64	42.609 MiB
✅	iot_agent_deb_arm64	39.710 MiB
✅	iot_agent_deb_armhf	40.439 MiB
✅	iot_agent_rpm_amd64	42.609 MiB
✅	iot_agent_suse_amd64	42.609 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+16.89 KiB (0.01% increase)	185.468 → 185.484 → 186.090
✅	agent_deb_amd64_fips	+33.11 KiB (0.02% increase)	176.148 → 176.180 → 180.330
✅	agent_heroku_amd64	neutral	87.120 MiB → 88.440
✅	agent_msi	-52.0 KiB (0.04% reduction)	138.426 → 138.375 → 143.470
✅	agent_rpm_amd64	+16.56 KiB (0.01% increase)	187.341 → 187.357 → 189.170
✅	agent_rpm_amd64_fips	+3.66 KiB (0.00% increase)	178.299 → 178.303 → 181.060
✅	agent_rpm_arm64	-4.79 KiB (0.00% reduction)	169.401 → 169.397 → 170.020
✅	agent_rpm_arm64_fips	+55.21 KiB (0.03% increase)	162.313 → 162.367 → 164.130
✅	agent_suse_amd64	+16.56 KiB (0.01% increase)	187.341 → 187.357 → 189.170
✅	agent_suse_amd64_fips	+3.66 KiB (0.00% increase)	178.299 → 178.303 → 181.060
✅	agent_suse_arm64	-4.79 KiB (0.00% reduction)	169.401 → 169.397 → 170.020
✅	agent_suse_arm64_fips	+55.21 KiB (0.03% increase)	162.313 → 162.367 → 164.130
✅	docker_agent_amd64	neutral	277.640 MiB → 279.410
✅	docker_agent_arm64	+2.62 KiB (0.00% increase)	264.937 → 264.939 → 267.960
✅	docker_agent_jmx_amd64	neutral	346.294 MiB → 348.040
✅	docker_agent_jmx_arm64	neutral	329.581 MiB → 332.560
✅	docker_cluster_agent_amd64	neutral	66.434 MiB → 67.220
✅	docker_cluster_agent_arm64	neutral	62.488 MiB → 63.640
✅	docker_cws_instrumentation_amd64	neutral	2.995 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	14.902 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.235 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.853 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.740 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.862 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.862 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.235 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.598 MiB → 10.450
✅	iot_agent_deb_armhf	neutral	9.800 MiB → 10.620
✅	iot_agent_rpm_amd64	neutral	11.251 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.251 MiB → 12.060

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: b030b407-2e7b-4cc3-bd89-8b7ba55ba0f9

Baseline: 715b9fb
Comparison: d841f6b
Diff

Optimization Goals: ✅ No significant changes detected

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.91	[-5.93, +0.12]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_metrics_logs	memory utilization	+0.79	[+0.57, +1.00]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	+0.60	[+0.51, +0.70]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	+0.57	[+0.37, +0.77]	1	Logs
➖	quality_gate_idle	memory utilization	+0.44	[+0.40, +0.49]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	+0.40	[+0.35, +0.46]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.17	[+0.01, +0.33]	1	Logs
➖	ddot_logs	memory utilization	+0.16	[+0.10, +0.22]	1	Logs
➖	file_tree	memory utilization	+0.10	[+0.04, +0.15]	1	Logs
➖	docker_containers_memory	memory utilization	+0.09	[+0.01, +0.16]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	+0.04	[-0.19, +0.28]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.04	[-0.46, +0.54]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.03	[-0.01, +0.08]	1	Logs
➖	ddot_metrics	memory utilization	+0.03	[-0.19, +0.25]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.11, +0.15]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.10, +0.10]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.00	[-0.12, +0.12]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.01	[-0.45, +0.43]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.05	[-0.43, +0.32]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.08	[-0.17, +0.01]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.17	[-0.32, -0.01]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.28	[-0.31, -0.24]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-1.84	[-3.35, -0.33]	1	Logs bounds checks dashboard
➖	docker_containers_cpu	% cpu utilization	-2.91	[-5.93, +0.12]	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	lost_bytes	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_metrics_logs, bounds check cpu_usage: 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 lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, 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, 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_logs, bounds check intake_connections: 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.

[Ishirui]

This means your jobs will only run on main (i.e. after the PR is merged). Is this expected, or do you want the build to run on PRs as well ?

[liustanley]

Yes that's intended, we wanted this PR to mainly run on our team's PRs and also main to make sure that the state on main is good (context). I believe it will also run on PRs with the filepath changes, since it ran on this PR

[liustanley]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-02-23 15:00:45 UTC ℹ️ Start processing command /merge

---

2026-02-23 15:00:51 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 1h (p90).

---

2026-02-23 15:53:05 UTC ℹ️ MergeQueue: This merge request was merged