Bump github.com/DataDog/agent-payload/v5 from 5.0.122 to 5.0.123 in /test/new-e2e

[dependabot]

Bumps github.com/DataDog/agent-payload/v5 from 5.0.122 to 5.0.123.

Release notes

Sourced from github.com/DataDog/agent-payload/v5's releases.

v5.0.123

What's Changed

• Rename statsByStatusCode to statsByErrorCode by @​DanielLavie in DataDog/agent-payload#320

Full Changelog: DataDog/agent-payload@v5.0.122...v5.0.123

Commits

• eefe2a6 Merge pull request #320 from DataDog/daniel.lavie/USMON-718-rename-kafka-stat...
• 0dc7b99 Rename statsByStatusCode to statsByErrorCode
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 70094b9d-1844-4b10-b506-17dd3a912032 Metrics dashboard Target profiles

Baseline: 1eba586
Comparison: 8c2f0b2

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	tcp_syslog_to_blackhole	ingress throughput	+9.25	[-4.31, +22.80]	Logs
➖	otel_to_otel_logs	ingress throughput	+0.39	[-0.42, +1.20]	Logs
➖	idle	memory utilization	+0.13	[+0.09, +0.16]	Logs
➖	file_tree	memory utilization	+0.11	[+0.06, +0.16]	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.21	[-2.09, -0.32]	Logs
➖	pycheck_1000_100byte_tags	% cpu utilization	-1.82	[-6.58, +2.95]	Logs
➖	basic_py_check	% cpu utilization	-2.90	[-5.47, -0.32]	Logs

Explanation

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".

[pducolin]

/merge

[dd-devflow]

🚂 MergeQueue: pull request added to the queue

The median merge time in main is 24m.

Use /merge -c to cancel this operation!

[dd-devflow]

❌ MergeQueue: This merge request has conflicts

This merge request conflicts with another merge request ahead in the queue.

The merge requests in front of this one are:

• #26802 with merge sha 9ababcc
• #26980 with merge sha cb3044b
• #25983 with merge sha f6f5dc5

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

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.