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

[ASCII-1613] Split dogstatsd/replay into new component hierarchy #25512

Merged
merged 12 commits into from May 24, 2024

Conversation

pgimalac
Copy link
Contributor

@pgimalac pgimalac commented May 10, 2024

What does this PR do?

Split comp/dogstats/replay into multiple packages for the component, fx, and implementations.

Motivation

Removing some dependencies from serverless.
When everything is in the same package you get everything at once whether you want it or not.

Additional Notes

This PR should be easier to review commit by commit:

  1. component interface, exported types, variables/consts
  2. mock interface and fx mock module
  3. implementation fx module
  4. everything else into implementation

Remaining commits are small and address review comments.

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

QA is handled in #25442

@pgimalac pgimalac added changelog/no-changelog team/agent-metrics-logs component framework qa/done Skip QA week as QA was done before merge and regressions are covered by tests labels May 10, 2024
Copy link

cit-pr-commenter bot commented May 10, 2024

Go Package Import Differences

Baseline: d9ff65e
Comparison: ea7b716

binaryosarchchange
agentlinuxamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
agentlinuxarm64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
agentwindowsamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
agentdarwinamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
agentdarwinarm64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
iot-agentlinuxamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
iot-agentlinuxarm64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
heroku-agentlinuxamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
cluster-agentlinuxamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
cluster-agentlinuxarm64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
dogstatsdlinuxamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
dogstatsdlinuxarm64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
security-agentlinuxamd64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
security-agentlinuxarm64
+3, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/fx
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
serverlesslinuxamd64
+2, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl
serverlesslinuxarm64
+2, -1
-github.com/DataDog/datadog-agent/comp/dogstatsd/replay
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def
+github.com/DataDog/datadog-agent/comp/dogstatsd/replay/impl

@pr-commenter
Copy link

pr-commenter bot commented May 10, 2024

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=35062935 --os-family=ubuntu

@pr-commenter
Copy link

pr-commenter bot commented May 10, 2024

Regression Detector

Regression Detector Results

Run ID: 9d6df802-6e65-4bc9-a2ab-9e68b8f525e5
Baseline: 451bf20
Comparison: 3c8aded

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
basic_py_check % cpu utilization +1.75 [-0.71, +4.22]
uds_dogstatsd_to_api_cpu % cpu utilization +0.76 [-2.17, +3.69]
idle memory utilization +0.18 [+0.15, +0.22]
tcp_dd_logs_filter_exclude ingress throughput +0.03 [+0.00, +0.06]
trace_agent_msgpack ingress throughput +0.01 [-0.00, +0.01]
trace_agent_json ingress throughput +0.00 [-0.01, +0.02]
uds_dogstatsd_to_api ingress throughput -0.02 [-0.22, +0.19]
otel_to_otel_logs ingress throughput -0.04 [-0.39, +0.32]
file_tree memory utilization -0.68 [-0.76, -0.60]
pycheck_1000_100byte_tags % cpu utilization -2.70 [-7.23, +1.83]
tcp_syslog_to_blackhole ingress throughput -3.10 [-23.38, +17.17]

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

@pgimalac pgimalac marked this pull request as ready for review May 13, 2024 15:04
@pgimalac pgimalac requested review from a team as code owners May 13, 2024 15:04
comp/dogstatsd/replay/def/component.go Outdated Show resolved Hide resolved
comp/dogstatsd/replay/mock/mock.go Outdated Show resolved Hide resolved
Copy link

codecov bot commented May 22, 2024

Codecov Report

Attention: Patch coverage is 40.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 46.82%. Comparing base (d9ff65e) to head (ea7b716).
Report is 1 commits behind head on main.

Files Patch % Lines
comp/dogstatsd/replay/impl/capture.go 0.00% 4 Missing ⚠️
comp/dogstatsd/listeners/uds_common.go 0.00% 1 Missing ⚠️
comp/dogstatsd/replay/impl/util_linux.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##             main   #25512       +/-   ##
===========================================
+ Coverage   44.95%   46.82%    +1.87%     
===========================================
  Files        2328      251     -2077     
  Lines      268349    21912   -246437     
===========================================
- Hits       120644    10261   -110383     
+ Misses     138111    11155   -126956     
+ Partials     9594      496     -9098     
Flag Coverage Δ
amzn_aarch64 46.77% <40.00%> (+0.99%) ⬆️
centos_x86_64 46.79% <40.00%> (+1.10%) ⬆️
ubuntu_aarch64 46.78% <40.00%> (+1.00%) ⬆️
ubuntu_x86_64 46.74% <40.00%> (+0.97%) ⬆️
windows_amd64 50.19% <44.44%> (-1.03%) ⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@GustavoCaso GustavoCaso left a comment

Choose a reason for hiding this comment

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

I can see there are a few of replaydef "github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def" in the PR. Maybe for consistency, we should rename them all to replay "github.com/DataDog/datadog-agent/comp/dogstatsd/replay/def"

@pgimalac pgimalac requested a review from hush-hush May 24, 2024 10:55
@pgimalac pgimalac dismissed hush-hush’s stale review May 24, 2024 10:57

out of date, and blocking me now 😄

@pgimalac
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

🚂 MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 30m)

Use /merge -c to cancel this operation!

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

❌ MergeQueue

Build pipeline has failing jobs for 7e41d6b

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.

You should have a look at the pipeline, wait for the build to finish and investigate the failures.
When you are ready, re-add your pull request to the queue!

⚠️ Do NOT retry failed jobs directly.

They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.

Details

List of failed jobs:

Go to failed Gitlab pipeline.

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

@pgimalac pgimalac requested a review from a team as a code owner May 24, 2024 11:15
@pgimalac
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

🚂 MergeQueue

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

@pgimalac
Copy link
Contributor Author

/merge -c

@pgimalac
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

⚠️ MergeQueue

This merge request was unqueued

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

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

🚂 MergeQueue

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

Copy link
Contributor

Serverless Benchmark Results

BenchmarkStartEndInvocation comparison between d9ff65e and 16419b9.

tl;dr

Use these benchmarks as an insight tool during development.

  1. Skim down the vs base column in each chart. If there is a ~, then there was no statistically significant change to the benchmark. Otherwise, ensure the estimated percent change is either negative or very small.

  2. The last row of each chart is the geomean. Ensure this percentage is either negative or very small.

What is this benchmarking?

The BenchmarkStartEndInvocation compares the amount of time it takes to call the start-invocation and end-invocation endpoints. For universal instrumentation languages (Dotnet, Golang, Java, Ruby), this represents the majority of the duration overhead added by our tracing layer.

The benchmark is run using a large variety of lambda request payloads. In the charts below, there is one row for each event payload type.

How do I interpret these charts?

The charts below comes from benchstat. They represent the statistical change in duration (sec/op), memory overhead (B/op), and allocations (allocs/op).

The benchstat docs explain how to interpret these charts.

Before the comparison table, we see common file-level configuration. If there are benchmarks with different configuration (for example, from different packages), benchstat will print separate tables for each configuration.

The table then compares the two input files for each benchmark. It shows the median and 95% confidence interval summaries for each benchmark before and after the change, and an A/B comparison under "vs base". ... The p-value measures how likely it is that any differences were due to random chance (i.e., noise). The "~" means benchstat did not detect a statistically significant difference between the two inputs. ...

Note that "statistically significant" is not the same as "large": with enough low-noise data, even very small changes can be distinguished from noise and considered statistically significant. It is, of course, generally easier to distinguish large changes from noise.

Finally, the last row of the table shows the geometric mean of each column, giving an overall picture of how the benchmarks changed. Proportional changes in the geomean reflect proportional changes in the benchmarks. For example, given n benchmarks, if sec/op for one of them increases by a factor of 2, then the sec/op geomean will increase by a factor of ⁿ√2.

I need more help

First off, do not worry if the benchmarks are failing. They are not tests. The intention is for them to be a tool for you to use during development.

If you would like a hand interpreting the results come chat with us in #serverless-agent in the internal DataDog slack or in #serverless in the public DataDog slack. We're happy to help!

Benchmark stats
goos: linux
goarch: amd64
pkg: github.com/DataDog/datadog-agent/pkg/serverless/daemon
cpu: AMD EPYC 7763 64-Core Processor                
                                      │ baseline/benchmark.log │       current/benchmark.log        │
                                      │         sec/op         │   sec/op     vs base               │
api-gateway-appsec.json                            88.48µ ± 4%   86.16µ ± 4%       ~ (p=0.579 n=10)
api-gateway-kong-appsec.json                       66.32µ ± 1%   68.49µ ± 5%  +3.28% (p=0.000 n=10)
api-gateway-kong.json                              64.21µ ± 1%   67.55µ ± 2%  +5.21% (p=0.000 n=10)
api-gateway-non-proxy-async.json                   102.1µ ± 2%   107.8µ ± 1%  +5.48% (p=0.000 n=10)
api-gateway-non-proxy.json                         101.8µ ± 1%   103.1µ ± 2%  +1.27% (p=0.001 n=10)
api-gateway-websocket-connect.json                 67.66µ ± 1%   68.72µ ± 2%  +1.57% (p=0.004 n=10)
api-gateway-websocket-default.json                 60.66µ ± 1%   62.79µ ± 2%  +3.50% (p=0.000 n=10)
api-gateway-websocket-disconnect.json              60.62µ ± 1%   62.71µ ± 2%  +3.45% (p=0.000 n=10)
api-gateway.json                                   112.5µ ± 1%   114.0µ ± 2%  +1.36% (p=0.009 n=10)
application-load-balancer.json                     61.59µ ± 1%   63.43µ ± 3%  +2.97% (p=0.000 n=10)
cloudfront.json                                    46.69µ ± 1%   47.36µ ± 1%  +1.45% (p=0.004 n=10)
cloudwatch-events.json                             38.16µ ± 2%   38.36µ ± 2%       ~ (p=0.225 n=10)
cloudwatch-logs.json                               65.39µ ± 1%   65.81µ ± 2%       ~ (p=0.123 n=10)
custom.json                                        30.47µ ± 2%   30.52µ ± 1%       ~ (p=0.645 n=10)
dynamodb.json                                      92.88µ ± 0%   92.83µ ± 1%       ~ (p=0.838 n=10)
empty.json                                         28.86µ ± 2%   29.07µ ± 2%       ~ (p=0.190 n=10)
eventbridge-custom.json                            42.24µ ± 3%   42.20µ ± 2%       ~ (p=0.579 n=10)
http-api.json                                      73.52µ ± 2%   74.40µ ± 1%       ~ (p=0.353 n=10)
kinesis-batch.json                                 71.65µ ± 2%   72.03µ ± 2%       ~ (p=0.315 n=10)
kinesis.json                                       54.58µ ± 2%   54.00µ ± 1%       ~ (p=0.247 n=10)
s3.json                                            59.09µ ± 2%   59.91µ ± 2%       ~ (p=0.143 n=10)
sns-batch.json                                     90.73µ ± 1%   91.14µ ± 2%       ~ (p=0.631 n=10)
sns.json                                           65.02µ ± 2%   65.02µ ± 1%       ~ (p=0.218 n=10)
snssqs.json                                        112.5µ ± 2%   111.4µ ± 1%       ~ (p=0.190 n=10)
snssqs_no_dd_context.json                          99.07µ ± 1%   99.69µ ± 2%       ~ (p=0.796 n=10)
sqs-aws-header.json                                55.30µ ± 1%   55.18µ ± 2%       ~ (p=0.796 n=10)
sqs-batch.json                                     95.32µ ± 2%   93.87µ ± 2%       ~ (p=0.089 n=10)
sqs.json                                           69.19µ ± 1%   69.71µ ± 2%       ~ (p=0.190 n=10)
sqs_no_dd_context.json                             62.13µ ± 2%   62.53µ ± 2%       ~ (p=0.393 n=10)
geomean                                            66.37µ        67.06µ       +1.04%

                                      │ baseline/benchmark.log │        current/benchmark.log        │
                                      │          B/op          │     B/op      vs base               │
api-gateway-appsec.json                           37.20Ki ± 0%   37.19Ki ± 0%       ~ (p=0.926 n=10)
api-gateway-kong-appsec.json                      26.80Ki ± 0%   26.80Ki ± 0%       ~ (p=0.342 n=10)
api-gateway-kong.json                             24.28Ki ± 0%   24.29Ki ± 0%       ~ (p=0.343 n=10)
api-gateway-non-proxy-async.json                  47.99Ki ± 0%   48.00Ki ± 0%  +0.03% (p=0.024 n=10)
api-gateway-non-proxy.json                        47.20Ki ± 0%   47.20Ki ± 0%       ~ (p=0.137 n=10)
api-gateway-websocket-connect.json                25.40Ki ± 0%   25.40Ki ± 0%       ~ (p=0.644 n=10)
api-gateway-websocket-default.json                21.30Ki ± 0%   21.30Ki ± 0%       ~ (p=1.000 n=10)
api-gateway-websocket-disconnect.json             21.08Ki ± 0%   21.09Ki ± 0%       ~ (p=0.210 n=10)
api-gateway.json                                  49.45Ki ± 0%   49.46Ki ± 0%       ~ (p=0.093 n=10)
application-load-balancer.json                    23.17Ki ± 0%   23.18Ki ± 0%       ~ (p=0.109 n=10)
cloudfront.json                                   17.58Ki ± 0%   17.58Ki ± 0%       ~ (p=0.516 n=10)
cloudwatch-events.json                            11.64Ki ± 0%   11.65Ki ± 0%       ~ (p=0.126 n=10)
cloudwatch-logs.json                              53.29Ki ± 0%   53.29Ki ± 0%       ~ (p=1.000 n=10)
custom.json                                       9.667Ki ± 0%   9.660Ki ± 0%       ~ (p=0.210 n=10)
dynamodb.json                                     40.62Ki ± 0%   40.62Ki ± 0%       ~ (p=0.956 n=10)
empty.json                                        9.223Ki ± 0%   9.218Ki ± 0%       ~ (p=0.868 n=10)
eventbridge-custom.json                           13.36Ki ± 0%   13.36Ki ± 0%       ~ (p=0.837 n=10)
http-api.json                                     23.68Ki ± 0%   23.69Ki ± 0%       ~ (p=0.631 n=10)
kinesis-batch.json                                26.97Ki ± 0%   26.94Ki ± 0%       ~ (p=0.061 n=10)
kinesis.json                                      17.75Ki ± 0%   17.74Ki ± 0%       ~ (p=0.305 n=10)
s3.json                                           20.29Ki ± 0%   20.27Ki ± 0%       ~ (p=0.271 n=10)
sns-batch.json                                    38.58Ki ± 0%   38.55Ki ± 0%       ~ (p=0.197 n=10)
sns.json                                          23.92Ki ± 0%   23.91Ki ± 0%       ~ (p=0.578 n=10)
snssqs.json                                       50.58Ki ± 0%   50.56Ki ± 0%       ~ (p=0.516 n=10)
snssqs_no_dd_context.json                         44.76Ki ± 0%   44.77Ki ± 0%       ~ (p=0.566 n=10)
sqs-aws-header.json                               18.75Ki ± 0%   18.77Ki ± 1%       ~ (p=0.929 n=10)
sqs-batch.json                                    41.61Ki ± 0%   41.52Ki ± 0%  -0.21% (p=0.027 n=10)
sqs.json                                          25.44Ki ± 1%   25.45Ki ± 0%       ~ (p=0.481 n=10)
sqs_no_dd_context.json                            20.63Ki ± 1%   20.67Ki ± 1%       ~ (p=0.912 n=10)
geomean                                           25.67Ki        25.67Ki       -0.00%

                                      │ baseline/benchmark.log │        current/benchmark.log        │
                                      │       allocs/op        │ allocs/op   vs base                 │
api-gateway-appsec.json                             630.0 ± 0%   629.0 ± 0%       ~ (p=0.656 n=10)
api-gateway-kong-appsec.json                        488.0 ± 0%   488.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-kong.json                               466.0 ± 0%   466.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-non-proxy-async.json                    725.0 ± 0%   725.0 ± 0%       ~ (p=0.582 n=10)
api-gateway-non-proxy.json                          715.5 ± 0%   716.0 ± 0%       ~ (p=0.350 n=10)
api-gateway-websocket-connect.json                  453.0 ± 0%   453.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-websocket-default.json                  379.0 ± 0%   379.0 ± 0%       ~ (p=1.000 n=10) ¹
api-gateway-websocket-disconnect.json               369.0 ± 0%   369.0 ± 0%       ~ (p=1.000 n=10)
api-gateway.json                                    790.0 ± 0%   790.0 ± 0%       ~ (p=0.303 n=10)
application-load-balancer.json                      352.0 ± 0%   353.0 ± 0%       ~ (p=0.179 n=10)
cloudfront.json                                     283.0 ± 0%   283.5 ± 0%       ~ (p=0.650 n=10)
cloudwatch-events.json                              220.0 ± 0%   220.0 ± 0%       ~ (p=1.000 n=10) ¹
cloudwatch-logs.json                                215.0 ± 0%   215.0 ± 0%       ~ (p=1.000 n=10)
custom.json                                         168.0 ± 0%   168.0 ± 0%       ~ (p=1.000 n=10)
dynamodb.json                                       589.0 ± 0%   589.0 ± 0%       ~ (p=1.000 n=10)
empty.json                                          159.0 ± 1%   159.0 ± 1%       ~ (p=1.000 n=10)
eventbridge-custom.json                             253.0 ± 0%   253.5 ± 0%       ~ (p=1.000 n=10)
http-api.json                                       432.0 ± 0%   432.0 ± 0%       ~ (p=0.777 n=10)
kinesis-batch.json                                  390.0 ± 0%   390.0 ± 0%       ~ (p=0.420 n=10)
kinesis.json                                        285.0 ± 0%   285.0 ± 0%       ~ (p=1.000 n=10)
s3.json                                             358.0 ± 0%   357.0 ± 0%       ~ (p=0.465 n=10)
sns-batch.json                                      455.0 ± 0%   454.5 ± 0%       ~ (p=0.470 n=10)
sns.json                                            323.0 ± 0%   323.0 ± 0%       ~ (p=0.973 n=10)
snssqs.json                                         445.5 ± 0%   445.0 ± 0%       ~ (p=0.550 n=10)
snssqs_no_dd_context.json                           399.0 ± 0%   398.5 ± 0%       ~ (p=0.768 n=10)
sqs-aws-header.json                                 273.0 ± 0%   273.0 ± 0%       ~ (p=0.777 n=10)
sqs-batch.json                                      504.0 ± 0%   503.0 ± 0%       ~ (p=0.068 n=10)
sqs.json                                            350.0 ± 1%   350.5 ± 0%       ~ (p=0.372 n=10)
sqs_no_dd_context.json                              324.0 ± 1%   325.0 ± 1%       ~ (p=0.508 n=10)
geomean                                             376.3        376.3       +0.01%
¹ all samples are equal

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

⚠️ MergeQueue

This merge request was unqueued

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

@pgimalac
Copy link
Contributor Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

🚂 MergeQueue

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

@dd-devflow
Copy link

dd-devflow bot commented May 24, 2024

🚂 MergeQueue

Pull request added to the queue.

There are 2 builds ahead! (estimated merge in less than 1h)

Use /merge -c to cancel this operation!

@dd-mergequeue dd-mergequeue bot merged commit 2beb26a into main May 24, 2024
206 checks passed
@dd-mergequeue dd-mergequeue bot deleted the pgimalac/dsd-replay-split branch May 24, 2024 16:17
@github-actions github-actions bot added this to the 7.55.0 milestone May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog component framework qa/done Skip QA week as QA was done before merge and regressions are covered by tests team/agent-metrics-logs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants