chore(tests): Add end-to-end tests with the Datadog Agent #18538

neuronull · 2023-09-11T20:18:37Z

closes: #18534
closes: #18829
closes: #18535
epic: #18533

Adds complete e2e tests with the Datadog Agent, and the datadog_agent source, datadog_logs sink and datadog_metrics sink.

The vdev infrastructure for running integration tests was refactored to be re-used for e2e tests, and a new subcommand to vdev was added to execute them, vdev e2e.

The main aspect of this setup that is different from existing integration tests is that the Vector components under test are run in a more black box fashion, by running a Vector instance in one of the containers along side the other services in the compose files. To accomplish this, the same image that is built to execute the test runner, is re-utilized for the vector compose service.

For emission of events, an "Emitter" is spun up to either generate fake logs or in the case of metrics, generate metrics with DogStatsD.

On the receiving end, a fakeintake instance receives the log events that are either sent from the Agent or sent from Vector.

This reverts commit 758a06a.

This reverts commit 7a69290.

netlify · 2023-09-11T20:18:41Z

✅ Deploy Preview for vector-project ready!

Name	Link
🔨 Latest commit	`5012f7f`
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/6529c3d966fecb000837c553
😎 Deploy Preview	https://deploy-preview-18538--vector-project.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

netlify · 2023-09-11T20:18:42Z

✅ Deploy Preview for vrl-playground ready!

Name	Link
🔨 Latest commit	`5012f7f`
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/6529c3d974edf500081fb2a7
😎 Deploy Preview	https://deploy-preview-18538--vrl-playground.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

aws-amplify-us-east-1 · 2023-09-11T20:19:48Z

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-18538.d1hoyoksbulg25.amplifyapp.com

aws-amplify-us-east-1 · 2023-09-11T20:19:55Z

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-18538.d2lr4eds605rpz.amplifyapp.com

aws-amplify-us-east-1 · 2023-09-11T20:20:14Z

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-18538.d1a7j77663uxsc.amplifyapp.com

github-advanced-security

check-spelling found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.

github-actions · 2024-01-31T18:02:53Z

Regression Detector Results

Run ID: cc081c6f-e1e2-4c2d-9770-9fd6f61ac059
Baseline: 899fd7e
Comparison: 1bb088e
Total CPUs: 7

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
➖	syslog_log2metric_humio_metrics	ingress throughput	+1.47	[+1.38, +1.56]
➖	otlp_http_to_blackhole	ingress throughput	+0.85	[+0.69, +1.01]
➖	splunk_hec_route_s3	ingress throughput	+0.81	[+0.31, +1.30]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.60	[+0.50, +0.71]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.48	[+0.38, +0.59]
➖	http_elasticsearch	ingress throughput	+0.38	[+0.30, +0.45]
➖	http_to_http_noack	ingress throughput	+0.23	[+0.14, +0.33]
➖	http_to_s3	ingress throughput	+0.13	[-0.15, +0.41]
➖	socket_to_socket_blackhole	ingress throughput	+0.10	[+0.03, +0.17]
➖	http_to_http_json	ingress throughput	+0.03	[-0.05, +0.10]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.16, +0.16]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.15, +0.15]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.01	[-0.12, +0.10]
➖	enterprise_http_to_http	ingress throughput	-0.06	[-0.11, -0.01]
➖	http_text_to_http_json	ingress throughput	-0.31	[-0.44, -0.19]
➖	syslog_humio_logs	ingress throughput	-0.48	[-0.59, -0.38]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.55	[-0.69, -0.40]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.64	[-0.73, -0.55]
➖	http_to_http_acks	ingress throughput	-0.64	[-1.95, +0.67]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.70	[-0.78, -0.61]
➖	syslog_loki	ingress throughput	-0.99	[-1.06, -0.92]
➖	fluent_elasticsearch	ingress throughput	-1.16	[-1.62, -0.69]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-1.20	[-1.31, -1.08]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-1.38	[-1.46, -1.29]
➖	syslog_splunk_hec_logs	ingress throughput	-1.81	[-1.89, -1.73]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-1.94	[-2.07, -1.81]
➖	file_to_blackhole	egress throughput	-2.82	[-5.25, -0.39]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

github-actions · 2024-01-31T18:23:14Z

Regression Detector Results

Run ID: 600a602d-bc6f-49dc-b507-3ea8dc3cbfa1
Baseline: 13ac2df
Comparison: 8f13e2a
Total CPUs: 7

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
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+2.07	[+1.96, +2.19]
➖	syslog_splunk_hec_logs	ingress throughput	+1.41	[+1.36, +1.45]
➖	fluent_elasticsearch	ingress throughput	+0.66	[+0.19, +1.13]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.65	[+0.56, +0.73]
➖	syslog_log2metric_humio_metrics	ingress throughput	+0.51	[+0.40, +0.62]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+0.46	[+0.38, +0.53]
➖	http_to_s3	ingress throughput	+0.33	[+0.05, +0.61]
➖	otlp_http_to_blackhole	ingress throughput	+0.32	[+0.16, +0.49]
➖	socket_to_socket_blackhole	ingress throughput	+0.18	[+0.09, +0.26]
➖	http_to_http_noack	ingress throughput	+0.18	[+0.07, +0.28]
➖	datadog_agent_remap_blackhole	ingress throughput	+0.11	[+0.01, +0.22]
➖	http_to_http_json	ingress throughput	+0.05	[-0.03, +0.13]
➖	http_elasticsearch	ingress throughput	+0.02	[-0.04, +0.09]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.14, +0.15]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.16, +0.16]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.03	[-0.14, +0.09]
➖	enterprise_http_to_http	ingress throughput	-0.06	[-0.14, +0.02]
➖	syslog_loki	ingress throughput	-0.16	[-0.23, -0.09]
➖	file_to_blackhole	egress throughput	-0.17	[-2.62, +2.28]
➖	splunk_hec_route_s3	ingress throughput	-0.29	[-0.79, +0.21]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.36	[-0.44, -0.27]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.37	[-0.45, -0.30]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.64	[-0.78, -0.50]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.92	[-1.05, -0.79]
➖	syslog_humio_logs	ingress throughput	-1.25	[-1.38, -1.12]
➖	http_to_http_acks	ingress throughput	-1.74	[-3.05, -0.44]
➖	http_text_to_http_json	ingress throughput	-2.46	[-2.59, -2.32]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

neuronull · 2024-01-31T18:56:29Z

I realized what was causing the integration test suite to fail in the MQ.

It's due to the change to the integration test's Dockerfile, which added the FEATURES arg , and additional build steps. This results in a net increase in the compilation time for the images used.
I think Doug's suggestion to re-use the image for the vector service as the runner is still a good one, but that only is necessary for the e2e tests.
Since the design now has a clear separation between the e2e tests and the integration tests, it makes sense to have a separate Dockerfile for the e2e tests.

This should solve the issue with the integration tests failing in the MQ.

github-actions · 2024-01-31T20:23:42Z

Regression Detector Results

Run ID: 0b4465eb-67d3-4027-8cf1-e1f39c81fea9
Baseline: 13ac2df
Comparison: 10eb713
Total CPUs: 7

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
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	+1.95	[+1.80, +2.10]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+1.14	[+1.07, +1.22]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.76	[+0.67, +0.85]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.50	[+0.42, +0.58]
➖	http_to_http_acks	ingress throughput	+0.48	[-0.84, +1.79]
➖	socket_to_socket_blackhole	ingress throughput	+0.22	[+0.16, +0.28]
➖	syslog_log2metric_humio_metrics	ingress throughput	+0.18	[+0.06, +0.29]
➖	http_to_http_noack	ingress throughput	+0.17	[+0.08, +0.27]
➖	syslog_humio_logs	ingress throughput	+0.17	[+0.07, +0.27]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.16	[+0.07, +0.24]
➖	file_to_blackhole	egress throughput	+0.11	[-2.35, +2.57]
➖	http_to_http_json	ingress throughput	+0.07	[-0.01, +0.15]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.16, +0.16]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.00	[-0.15, +0.14]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.03	[-0.14, +0.09]
➖	http_to_s3	ingress throughput	-0.07	[-0.35, +0.21]
➖	splunk_hec_route_s3	ingress throughput	-0.08	[-0.57, +0.42]
➖	enterprise_http_to_http	ingress throughput	-0.10	[-0.18, -0.01]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.19	[-0.28, -0.10]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.22	[-0.34, -0.09]
➖	otlp_http_to_blackhole	ingress throughput	-0.26	[-0.40, -0.11]
➖	syslog_splunk_hec_logs	ingress throughput	-0.28	[-0.33, -0.23]
➖	http_elasticsearch	ingress throughput	-0.53	[-0.60, -0.47]
➖	fluent_elasticsearch	ingress throughput	-0.90	[-1.36, -0.43]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.93	[-1.02, -0.85]
➖	syslog_loki	ingress throughput	-1.03	[-1.08, -0.97]
➖	http_text_to_http_json	ingress throughput	-1.56	[-1.68, -1.45]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

github-actions · 2024-01-31T21:21:39Z

Regression Detector Results

Run ID: b1d11b08-aaac-4266-8e73-05d2d50f02f5
Baseline: 13ac2df
Comparison: 43a9a36
Total CPUs: 7

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
➖	syslog_log2metric_humio_metrics	ingress throughput	+2.05	[+1.93, +2.17]
➖	otlp_grpc_to_blackhole	ingress throughput	+1.45	[+1.36, +1.55]
➖	splunk_hec_route_s3	ingress throughput	+1.41	[+0.90, +1.91]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	+1.38	[+1.24, +1.53]
➖	datadog_agent_remap_blackhole	ingress throughput	+1.27	[+1.19, +1.35]
➖	fluent_elasticsearch	ingress throughput	+0.62	[+0.15, +1.09]
➖	syslog_loki	ingress throughput	+0.22	[+0.17, +0.27]
➖	http_to_http_noack	ingress throughput	+0.18	[+0.09, +0.28]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	+0.07	[-0.02, +0.16]
➖	http_to_s3	ingress throughput	+0.06	[-0.22, +0.33]
➖	http_to_http_json	ingress throughput	+0.05	[-0.02, +0.13]
➖	http_elasticsearch	ingress throughput	+0.00	[-0.06, +0.07]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.14, +0.15]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.00	[-0.16, +0.16]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-0.01	[-0.09, +0.08]
➖	enterprise_http_to_http	ingress throughput	-0.03	[-0.12, +0.05]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.06	[-0.17, +0.05]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.28	[-0.36, -0.19]
➖	otlp_http_to_blackhole	ingress throughput	-0.33	[-0.48, -0.18]
➖	socket_to_socket_blackhole	ingress throughput	-0.38	[-0.44, -0.32]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.40	[-0.53, -0.26]
➖	syslog_humio_logs	ingress throughput	-0.44	[-0.55, -0.34]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-0.46	[-0.57, -0.35]
➖	syslog_splunk_hec_logs	ingress throughput	-0.48	[-0.53, -0.42]
➖	http_text_to_http_json	ingress throughput	-0.52	[-0.65, -0.39]
➖	file_to_blackhole	egress throughput	-0.59	[-3.07, +1.90]
➖	http_to_http_acks	ingress throughput	-1.10	[-2.41, +0.22]

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:

Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
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.
Its configuration does not mark it "erratic".

…ev#18538) * start * check spelling allow * reorg * try consume a log * trying on logs * saving progress on vdev changes * more vdev drafts * Revert "more vdev drafts" This reverts commit 758a06a. * Revert "saving progress on vdev changes" This reverts commit 7a69290. * extract Vector instance to its own container * cleanup the compose file * Generate logs on fly * cleanup * cleanup * cleanup * remove sleep * add to CI * spell checker * fix issue with DD changes detection * more workflow fix * increase timeout as experiment * update vector config for log endpoint field * touch up * start * CI * feedback bg * add scaffolding for the differentiation of series API versions * fix(datadog_metrics sink): fix the integration tests which weren't actually validating anything * fix workflows * clippy * fix filter for traces * add first pass * add testing coverage * cargo.lock * reduce duplicated code * cleanup * clippy * feedback ds: remove check for sort by name * feedback ds: extend unit tests for v2 * feedback ds: extend the int test coverage * Revert "feedback ds: remove check for sort by name" This reverts commit c95a326. * add explicit sort check * add env var for v1 support * check events * add note in deprecations * feedback ds * ds feedback logs PR * config pain; start aggregation * feedback ds: move to scripts/e2e * add v6 and v7 agent versions to test against * remove dead code allow * move to e2e dir * improve comparison logic * code reduction * add sketches, some reorg * cleanup * add notes about the e2e prefix needed * re-use runner image * fixes * e2e tests now run in CI * clippy * remove unused struct * true up the int test comment changes * cleanup * rework the massaging and comparison model * compare to all versions * cleanup and address TODO for sketches * feedback ds: workflows * feedback ds: simpler compose * feedback ds: agent versions clarity * feedback ds: comments * clippy * touchups * feedback bg: assert_eq * increase timeout workflow * run in 8 core runner * check * separate e2e workflow * comment * fix workflows * prune timing * allow build_all option to start subcommand * hack to bypass this temporary issue with CI * feedback bg * feedback bg * feedback ds: metric type check * add descriptive comment * spelling * chore(vdev): refactor e2e tests into own subcommand (vectordotdev#19666) * merge conflict * update workflows * rename * fix e2e logic * fix e2e * fix e2e * script usage * touchups to workflows * separate dockerfile for the e2e tests * add the Dockerfile

neuronull added 17 commits May 17, 2023 16:54

start

a58ae6f

check spelling allow

98b9712

reorg

62211ab

try consume a log

ae1d41a

trying on logs

8edd7f4

Merge branch 'master' into neuronull/dd_e2e_infra_logs

136650f

saving progress on vdev changes

7a69290

more vdev drafts

758a06a

Revert "more vdev drafts"

9396764

This reverts commit 758a06a.

Revert "saving progress on vdev changes"

7df74ba

This reverts commit 7a69290.

extract Vector instance to its own container

f4b2f6c

cleanup the compose file

90ac09b

Generate logs on fly

d95f708

cleanup

1cc6f8d

cleanup

6923875

cleanup

7400659

remove sleep

a2ceff5

neuronull self-assigned this Sep 11, 2023

github-actions bot added domain: ci Anything related to Vector's CI environment domain: vdev Anything related to the vdev tooling labels Sep 11, 2023

neuronull added sink: datadog_logs Anything `datadog_logs` sink related source: datadog_agent Anything `datadog_agent` source related domain: tests Anything related to Vector's internal tests labels Sep 11, 2023

github-advanced-security bot found potential problems Sep 11, 2023

View reviewed changes

add to CI

070c69e

neuronull added 9 commits January 30, 2024 15:02

chore(vdev): refactor e2e tests into own subcommand (#19666)

6da0b03

Merge branch 'neuronull/dd_e2e_infra_logs' into neuronull/dd_e2e_metrics

ce73f67

merge conflict

34f9e7a

update workflows

12318fb

rename

68d0fb7

fix e2e logic

5820a0b

fix e2e

32e133c

fix e2e

f11099a

script usage

5933c06

neuronull changed the title ~~chore(datadog_agent source, datadog_logs sink): Add end to end tests with the Datadog Agent.~~ chore(tests): Add end-to-end tests with the Datadog Agent Jan 31, 2024

touchups to workflows

731b278

neuronull added the sink: datadog_metrics Anything `datadog_metrics` sink related label Jan 31, 2024

neuronull enabled auto-merge January 31, 2024 16:59

neuronull added this pull request to the merge queue Jan 31, 2024

github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 31, 2024

separate dockerfile for the e2e tests

87ffb7c

neuronull enabled auto-merge January 31, 2024 18:57

add the Dockerfile

81f2229

neuronull added this pull request to the merge queue Jan 31, 2024

github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 31, 2024

neuronull added this pull request to the merge queue Jan 31, 2024

Merged via the queue into master with commit 43a9a36 Jan 31, 2024
50 checks passed

neuronull deleted the neuronull/dd_e2e_infra_logs branch January 31, 2024 21:45

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(tests): Add end-to-end tests with the Datadog Agent #18538

chore(tests): Add end-to-end tests with the Datadog Agent #18538

neuronull commented Sep 11, 2023 •

edited

Loading

netlify bot commented Sep 11, 2023 •

edited

Loading

netlify bot commented Sep 11, 2023 •

edited

Loading

aws-amplify-us-east-1 bot commented Sep 11, 2023

aws-amplify-us-east-1 bot commented Sep 11, 2023

aws-amplify-us-east-1 bot commented Sep 11, 2023

github-advanced-security bot left a comment

github-actions bot commented Jan 31, 2024

Fine details of change detection per experiment

Explanation

github-actions bot commented Jan 31, 2024

Fine details of change detection per experiment

Explanation

neuronull commented Jan 31, 2024 •

edited

Loading

github-actions bot commented Jan 31, 2024

Fine details of change detection per experiment

Explanation

github-actions bot commented Jan 31, 2024

Fine details of change detection per experiment

Explanation

chore(tests): Add end-to-end tests with the Datadog Agent #18538

chore(tests): Add end-to-end tests with the Datadog Agent #18538

Conversation

neuronull commented Sep 11, 2023 • edited Loading

netlify bot commented Sep 11, 2023 • edited Loading

✅ Deploy Preview for vector-project ready!

netlify bot commented Sep 11, 2023 • edited Loading

✅ Deploy Preview for vrl-playground ready!

aws-amplify-us-east-1 bot commented Sep 11, 2023

aws-amplify-us-east-1 bot commented Sep 11, 2023

aws-amplify-us-east-1 bot commented Sep 11, 2023

github-advanced-security bot left a comment

Choose a reason for hiding this comment

github-actions bot commented Jan 31, 2024

Regression Detector Results

No significant changes in experiment optimization goals

Fine details of change detection per experiment

Explanation

github-actions bot commented Jan 31, 2024

Regression Detector Results

No significant changes in experiment optimization goals

Fine details of change detection per experiment

Explanation

neuronull commented Jan 31, 2024 • edited Loading

github-actions bot commented Jan 31, 2024

Regression Detector Results

No significant changes in experiment optimization goals

Fine details of change detection per experiment

Explanation

github-actions bot commented Jan 31, 2024

Regression Detector Results

No significant changes in experiment optimization goals

Fine details of change detection per experiment

Explanation

neuronull commented Sep 11, 2023 •

edited

Loading

netlify bot commented Sep 11, 2023 •

edited

Loading

netlify bot commented Sep 11, 2023 •

edited

Loading

neuronull commented Jan 31, 2024 •

edited

Loading