vector icon indicating copy to clipboard operation
vector copied to clipboard
verified publisher icon vectordotdev

chore(deps): Bump syslog from 6.1.1 to 7.0.0

Open dependabot[bot] opened this issue 1 year ago • 10 comments

Bumps syslog from 6.1.1 to 7.0.0.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

dependabot[bot] avatar Jul 29 '24 04:07 dependabot[bot]

Datadog Report

Branch report: dependabot/cargo/syslog-7.0.0 Commit report: 14ca6a2 Test service: vector

:white_check_mark: 0 Failed, 7 Passed, 0 Skipped, 25.48s Total Time

datadog-vectordotdev[bot] avatar Jul 30 '24 21:07 datadog-vectordotdev[bot]

Regression Detector Results

Run ID: 7c0b84ef-b55c-4b86-90e5-396a65b1e9e8 Metrics dashboard

Baseline: 202fe723c71d25e1f7be64b8be5f734e04d9886f Comparison: 3a954b3fe67f2d46ca78b590a92f35e56883c2cb

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.

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
❌ file_to_blackhole egress throughput -11.69 [-18.16, -5.23]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
➖ syslog_loki ingress throughput +2.70 [+2.59, +2.80]
➖ http_to_http_acks ingress throughput +1.97 [+0.65, +3.30]
➖ syslog_splunk_hec_logs ingress throughput +1.70 [+1.60, +1.80]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +1.70 [+1.60, +1.80]
➖ syslog_humio_logs ingress throughput +1.35 [+1.22, +1.47]
➖ datadog_agent_remap_blackhole ingress throughput +0.97 [+0.87, +1.08]
➖ http_elasticsearch ingress throughput +0.81 [+0.65, +0.98]
➖ datadog_agent_remap_blackhole_acks ingress throughput +0.75 [+0.65, +0.85]
➖ syslog_regex_logs2metric_ddmetrics ingress throughput +0.57 [+0.41, +0.73]
➖ syslog_log2metric_humio_metrics ingress throughput +0.51 [+0.41, +0.62]
➖ http_to_http_noack ingress throughput +0.16 [+0.08, +0.24]
➖ datadog_agent_remap_datadog_logs ingress throughput +0.11 [-0.07, +0.29]
➖ otlp_grpc_to_blackhole ingress throughput +0.06 [-0.06, +0.17]
➖ fluent_elasticsearch ingress throughput +0.04 [-0.45, +0.52]
➖ http_to_http_json ingress throughput +0.03 [-0.01, +0.06]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.00 [-0.10, +0.10]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.00 [-0.12, +0.12]
➖ splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.09, +0.08]
➖ splunk_hec_route_s3 ingress throughput -0.05 [-0.36, +0.25]
➖ http_to_s3 ingress throughput -0.10 [-0.37, +0.17]
➖ otlp_http_to_blackhole ingress throughput -0.21 [-0.33, -0.09]
➖ socket_to_socket_blackhole ingress throughput -0.51 [-0.55, -0.48]
➖ http_text_to_http_json ingress throughput -0.61 [-0.72, -0.50]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput -1.36 [-1.53, -1.19]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput -1.62 [-1.74, -1.49]
❌ file_to_blackhole egress throughput -11.69 [-18.16, -5.23]

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

github-actions[bot] avatar Jul 31 '24 05:07 github-actions[bot]

Regression Detector Results

Run ID: f72d82a9-abfd-4921-aee5-dc026a1d0f8f Metrics dashboard

Baseline: f56a1e086121a445e56a2514e971fa7f8a176639 Comparison: 473df374944e5d97db3964851dfe7febbfd10a72

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.

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
✅ file_to_blackhole egress throughput +15.60 [+7.89, +23.31]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
✅ file_to_blackhole egress throughput +15.60 [+7.89, +23.31]
➖ splunk_hec_route_s3 ingress throughput +4.55 [+4.24, +4.86]
➖ syslog_log2metric_humio_metrics ingress throughput +4.43 [+4.28, +4.58]
➖ datadog_agent_remap_datadog_logs ingress throughput +1.60 [+1.40, +1.79]
➖ http_text_to_http_json ingress throughput +1.50 [+1.38, +1.63]
➖ http_elasticsearch ingress throughput +1.45 [+1.26, +1.64]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +1.41 [+1.32, +1.49]
➖ otlp_http_to_blackhole ingress throughput +1.18 [+1.05, +1.31]
➖ http_to_http_acks ingress throughput +1.11 [-0.22, +2.43]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput +1.03 [+0.87, +1.18]
➖ syslog_loki ingress throughput +0.83 [+0.75, +0.91]
➖ otlp_grpc_to_blackhole ingress throughput +0.67 [+0.55, +0.79]
➖ fluent_elasticsearch ingress throughput +0.54 [+0.05, +1.03]
➖ datadog_agent_remap_blackhole ingress throughput +0.36 [+0.25, +0.47]
➖ http_to_http_noack ingress throughput +0.14 [+0.06, +0.21]
➖ http_to_http_json ingress throughput +0.02 [-0.02, +0.07]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.10, +0.11]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.01 [-0.14, +0.12]
➖ splunk_hec_indexer_ack_blackhole ingress throughput -0.01 [-0.09, +0.07]
➖ http_to_s3 ingress throughput -0.23 [-0.50, +0.04]
➖ syslog_splunk_hec_logs ingress throughput -0.46 [-0.55, -0.36]
➖ socket_to_socket_blackhole ingress throughput -0.61 [-0.67, -0.54]
➖ syslog_humio_logs ingress throughput -1.82 [-1.95, -1.70]
➖ datadog_agent_remap_blackhole_acks ingress throughput -1.85 [-1.97, -1.74]
➖ syslog_regex_logs2metric_ddmetrics ingress throughput -2.32 [-2.45, -2.19]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput -2.68 [-2.78, -2.58]

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

github-actions[bot] avatar Jul 31 '24 06:07 github-actions[bot]

Regression Detector Results

Run ID: 8241523e-2be9-499e-a105-a6ac2961e4d2 Metrics dashboard

Baseline: 7d61cd9c6eea4e76c8dc0093e080dbd84e49ad1c Comparison: e277011b0c244d04d0c0a00991ba6542736737d2

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

Significant changes in experiment optimization goals

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

perf experiment goal Δ mean % Δ mean % CI links
✅ syslog_regex_logs2metric_ddmetrics ingress throughput +6.81 [+6.59, +7.03]

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
✅ file_to_blackhole egress throughput +30.94 [+22.87, +39.00]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
✅ file_to_blackhole egress throughput +30.94 [+22.87, +39.00]
✅ syslog_regex_logs2metric_ddmetrics ingress throughput +6.81 [+6.59, +7.03]
➖ syslog_loki ingress throughput +4.83 [+4.72, +4.94]
➖ socket_to_socket_blackhole ingress throughput +2.97 [+2.88, +3.06]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput +2.84 [+2.74, +2.95]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +2.57 [+2.47, +2.68]
➖ otlp_http_to_blackhole ingress throughput +1.38 [+1.21, +1.55]
➖ http_to_http_acks ingress throughput +0.56 [-0.75, +1.87]
➖ otlp_grpc_to_blackhole ingress throughput +0.49 [+0.38, +0.61]
➖ fluent_elasticsearch ingress throughput +0.37 [-0.11, +0.85]
➖ http_to_http_noack ingress throughput +0.20 [+0.10, +0.29]
➖ syslog_splunk_hec_logs ingress throughput +0.02 [-0.07, +0.11]
➖ http_to_http_json ingress throughput +0.02 [-0.03, +0.06]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.09, +0.11]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.13, +0.13]
➖ splunk_hec_indexer_ack_blackhole ingress throughput -0.02 [-0.10, +0.06]
➖ datadog_agent_remap_blackhole_acks ingress throughput -0.13 [-0.24, -0.02]
➖ http_text_to_http_json ingress throughput -0.23 [-0.35, -0.11]
➖ syslog_log2metric_humio_metrics ingress throughput -0.43 [-0.62, -0.23]
➖ http_to_s3 ingress throughput -0.51 [-0.78, -0.24]
➖ http_elasticsearch ingress throughput -0.60 [-0.75, -0.45]
➖ syslog_humio_logs ingress throughput -0.77 [-0.91, -0.64]
➖ splunk_hec_route_s3 ingress throughput -1.39 [-1.71, -1.08]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput -2.27 [-2.45, -2.09]
➖ datadog_agent_remap_blackhole ingress throughput -2.28 [-2.38, -2.17]
➖ datadog_agent_remap_datadog_logs ingress throughput -4.07 [-4.24, -3.90]

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

github-actions[bot] avatar Aug 09 '24 17:08 github-actions[bot]

Regression Detector Results

Run ID: 9b956843-f15c-49c2-82b1-d2296a39485e Metrics dashboard

Baseline: b7cf0befe4a7bc917a8d6e25bc629385bcae72cb Comparison: d21798b75804246f609ad4d8840d68d5c4a8be3c

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.

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
➖ file_to_blackhole egress throughput -2.36 [-9.24, +4.51]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
➖ syslog_humio_logs ingress throughput +4.48 [+4.38, +4.58]
➖ syslog_log2metric_humio_metrics ingress throughput +3.60 [+3.45, +3.76]
➖ syslog_loki ingress throughput +2.92 [+2.82, +3.02]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +2.23 [+2.13, +2.34]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput +1.95 [+1.84, +2.07]
➖ socket_to_socket_blackhole ingress throughput +1.82 [+1.69, +1.94]
➖ syslog_splunk_hec_logs ingress throughput +0.68 [+0.58, +0.79]
➖ fluent_elasticsearch ingress throughput +0.43 [-0.06, +0.92]
➖ otlp_grpc_to_blackhole ingress throughput +0.41 [+0.29, +0.53]
➖ http_to_http_acks ingress throughput +0.27 [-1.06, +1.59]
➖ datadog_agent_remap_blackhole ingress throughput +0.22 [+0.13, +0.31]
➖ datadog_agent_remap_datadog_logs ingress throughput +0.20 [+0.01, +0.39]
➖ http_to_s3 ingress throughput +0.04 [-0.23, +0.31]
➖ http_to_http_json ingress throughput +0.03 [-0.01, +0.08]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.09, +0.10]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.11, +0.11]
➖ http_to_http_noack ingress throughput -0.00 [-0.02, +0.02]
➖ splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.09, +0.08]
➖ otlp_http_to_blackhole ingress throughput -0.10 [-0.25, +0.05]
➖ splunk_hec_route_s3 ingress throughput -0.13 [-0.47, +0.21]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput -0.38 [-0.56, -0.20]
➖ http_text_to_http_json ingress throughput -0.64 [-0.76, -0.51]
➖ http_elasticsearch ingress throughput -1.68 [-1.84, -1.52]
➖ datadog_agent_remap_blackhole_acks ingress throughput -2.03 [-2.16, -1.89]
➖ file_to_blackhole egress throughput -2.36 [-9.24, +4.51]
➖ syslog_regex_logs2metric_ddmetrics ingress throughput -3.18 [-3.39, -2.97]

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

github-actions[bot] avatar Aug 09 '24 17:08 github-actions[bot]

Regression Detector Results

Run ID: 7a4196ee-c5ba-4426-be90-c56b1cb8d870 Metrics dashboard

Baseline: 16d2300bd8def42248e49e42643c8c1a604835c8 Comparison: 3d31638351e591a0e428ada927cfa0ea2c5184f5

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

Significant changes in experiment optimization goals

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

perf experiment goal Δ mean % Δ mean % CI links
✅ syslog_log2metric_splunk_hec_metrics ingress throughput +5.22 [+5.07, +5.38]
❌ syslog_humio_logs ingress throughput -5.45 [-5.63, -5.27]

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
❌ file_to_blackhole egress throughput -11.78 [-18.17, -5.39]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
✅ syslog_log2metric_splunk_hec_metrics ingress throughput +5.22 [+5.07, +5.38]
➖ splunk_hec_route_s3 ingress throughput +2.73 [+2.42, +3.05]
➖ datadog_agent_remap_blackhole_acks ingress throughput +1.98 [+1.87, +2.08]
➖ syslog_regex_logs2metric_ddmetrics ingress throughput +1.94 [+1.75, +2.13]
➖ syslog_loki ingress throughput +1.08 [+0.98, +1.17]
➖ datadog_agent_remap_datadog_logs ingress throughput +0.80 [+0.62, +0.98]
➖ syslog_log2metric_humio_metrics ingress throughput +0.63 [+0.50, +0.76]
➖ http_elasticsearch ingress throughput +0.38 [+0.20, +0.56]
➖ http_to_s3 ingress throughput +0.27 [+0.01, +0.53]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput +0.20 [+0.03, +0.38]
➖ http_to_http_noack ingress throughput +0.16 [+0.08, +0.24]
➖ http_to_http_json ingress throughput +0.05 [-0.00, +0.10]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.09, +0.10]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.14, +0.14]
➖ splunk_hec_indexer_ack_blackhole ingress throughput -0.01 [-0.09, +0.07]
➖ socket_to_socket_blackhole ingress throughput -0.12 [-0.18, -0.05]
➖ http_to_http_acks ingress throughput -0.29 [-1.61, +1.02]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -0.58 [-0.67, -0.48]
➖ otlp_grpc_to_blackhole ingress throughput -0.75 [-0.86, -0.64]
➖ syslog_splunk_hec_logs ingress throughput -0.82 [-0.93, -0.71]
➖ http_text_to_http_json ingress throughput -1.03 [-1.17, -0.89]
➖ datadog_agent_remap_blackhole ingress throughput -1.52 [-1.63, -1.41]
➖ fluent_elasticsearch ingress throughput -1.65 [-2.14, -1.16]
➖ otlp_http_to_blackhole ingress throughput -3.09 [-3.23, -2.96]
❌ syslog_humio_logs ingress throughput -5.45 [-5.63, -5.27]
❌ file_to_blackhole egress throughput -11.78 [-18.17, -5.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:

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

github-actions[bot] avatar Aug 09 '24 18:08 github-actions[bot]

Regression Detector Results

Run ID: a5e5bf46-78be-4119-b623-ede2169ba7ae Metrics dashboard

Baseline: a358576f968e4b363f52a54aed0e43d6b0b744f4 Comparison: 1b32fc7f73902c2117bc1b1332705bde23b595c1

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.

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
❌ file_to_blackhole egress throughput -12.53 [-18.64, -6.42]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
➖ otlp_http_to_blackhole ingress throughput +2.61 [+2.44, +2.78]
➖ syslog_log2metric_humio_metrics ingress throughput +2.08 [+1.95, +2.22]
➖ datadog_agent_remap_blackhole ingress throughput +1.46 [+1.36, +1.56]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +1.37 [+1.28, +1.47]
➖ datadog_agent_remap_blackhole_acks ingress throughput +0.94 [+0.84, +1.05]
➖ http_text_to_http_json ingress throughput +0.33 [+0.22, +0.44]
➖ syslog_regex_logs2metric_ddmetrics ingress throughput +0.13 [-0.00, +0.27]
➖ http_to_s3 ingress throughput +0.12 [-0.15, +0.38]
➖ http_to_http_noack ingress throughput +0.10 [+0.03, +0.17]
➖ http_to_http_json ingress throughput +0.09 [+0.03, +0.15]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.09, +0.11]
➖ splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.08, +0.08]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.01 [-0.12, +0.11]
➖ fluent_elasticsearch ingress throughput -0.09 [-0.58, +0.39]
➖ otlp_grpc_to_blackhole ingress throughput -0.13 [-0.24, -0.01]
➖ syslog_loki ingress throughput -0.34 [-0.42, -0.26]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput -0.41 [-0.49, -0.32]
➖ splunk_hec_route_s3 ingress throughput -0.42 [-0.73, -0.11]
➖ datadog_agent_remap_datadog_logs ingress throughput -0.79 [-0.96, -0.62]
➖ socket_to_socket_blackhole ingress throughput -0.83 [-0.89, -0.76]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput -0.90 [-1.09, -0.72]
➖ syslog_humio_logs ingress throughput -1.14 [-1.25, -1.04]
➖ http_to_http_acks ingress throughput -1.19 [-2.49, +0.12]
➖ syslog_splunk_hec_logs ingress throughput -1.32 [-1.44, -1.21]
➖ http_elasticsearch ingress throughput -1.57 [-1.72, -1.42]
❌ file_to_blackhole egress throughput -12.53 [-18.64, -6.42]

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

github-actions[bot] avatar Aug 10 '24 06:08 github-actions[bot]

Regression Detector Results

Run ID: 774240aa-a50d-4af5-b014-a7cdad446586 Metrics dashboard

Baseline: 645804a72438197c8e8ccd02ad29e4024f9a59ce Comparison: d86780f5faea71d587e91c8bb1bc98d1f0bc0a8d

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.

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
✅ file_to_blackhole egress throughput +14.09 [+6.62, +21.56]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
✅ file_to_blackhole egress throughput +14.09 [+6.62, +21.56]
➖ otlp_http_to_blackhole ingress throughput +4.01 [+3.89, +4.14]
➖ splunk_hec_route_s3 ingress throughput +2.59 [+2.24, +2.95]
➖ socket_to_socket_blackhole ingress throughput +2.36 [+2.31, +2.42]
➖ syslog_loki ingress throughput +1.44 [+1.31, +1.57]
➖ otlp_grpc_to_blackhole ingress throughput +0.93 [+0.82, +1.05]
➖ http_to_http_noack ingress throughput +0.16 [+0.08, +0.25]
➖ http_to_http_acks ingress throughput +0.15 [-1.16, +1.46]
➖ splunk_hec_indexer_ack_blackhole ingress throughput +0.03 [-0.05, +0.11]
➖ http_to_http_json ingress throughput +0.02 [-0.02, +0.05]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.08, +0.10]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.11, +0.11]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput -0.01 [-0.13, +0.10]
➖ datadog_agent_remap_datadog_logs ingress throughput -0.09 [-0.29, +0.11]
➖ fluent_elasticsearch ingress throughput -0.28 [-0.77, +0.21]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput -0.31 [-0.50, -0.13]
➖ http_elasticsearch ingress throughput -0.44 [-0.62, -0.27]
➖ http_to_s3 ingress throughput -0.75 [-1.03, -0.47]
➖ syslog_splunk_hec_logs ingress throughput -0.86 [-0.97, -0.75]
➖ datadog_agent_remap_blackhole_acks ingress throughput -0.88 [-1.04, -0.71]
➖ syslog_humio_logs ingress throughput -0.95 [-1.13, -0.77]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -2.60 [-2.70, -2.49]
➖ datadog_agent_remap_blackhole ingress throughput -3.02 [-3.15, -2.88]
➖ http_text_to_http_json ingress throughput -3.02 [-3.14, -2.90]
➖ syslog_regex_logs2metric_ddmetrics ingress throughput -3.64 [-3.82, -3.45]
➖ syslog_log2metric_humio_metrics ingress throughput -4.25 [-4.42, -4.07]

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

github-actions[bot] avatar Aug 12 '24 23:08 github-actions[bot]

Regression Detector Results

Run ID: 02216b42-926b-4414-97ad-1a4eaebd0fb5 Metrics dashboard

Baseline: 84666a4a41302e665651db68c7d2ce866b96d78c Comparison: 12d690891b31e13f92b22a87700d822c89e21081

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.

Experiments ignored for regressions

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

perf experiment goal Δ mean % Δ mean % CI links
❌ file_to_blackhole egress throughput -8.41 [-14.85, -1.96]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI links
➖ syslog_regex_logs2metric_ddmetrics ingress throughput +1.87 [+1.69, +2.06]
➖ datadog_agent_remap_datadog_logs ingress throughput +1.58 [+1.37, +1.78]
➖ http_elasticsearch ingress throughput +1.14 [+1.00, +1.28]
➖ fluent_elasticsearch ingress throughput +1.11 [+0.62, +1.61]
➖ datadog_agent_remap_blackhole_acks ingress throughput +0.83 [+0.70, +0.96]
➖ syslog_splunk_hec_logs ingress throughput +0.51 [+0.43, +0.59]
➖ otlp_grpc_to_blackhole ingress throughput +0.50 [+0.38, +0.61]
➖ http_to_s3 ingress throughput +0.34 [+0.08, +0.61]
➖ http_to_http_noack ingress throughput +0.19 [+0.10, +0.28]
➖ http_to_http_acks ingress throughput +0.12 [-1.20, +1.44]
➖ http_to_http_json ingress throughput +0.02 [-0.01, +0.05]
➖ splunk_hec_to_splunk_hec_logs_noack ingress throughput +0.01 [-0.09, +0.12]
➖ splunk_hec_indexer_ack_blackhole ingress throughput +0.00 [-0.08, +0.09]
➖ splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.01 [-0.12, +0.11]
➖ syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -0.33 [-0.47, -0.20]
➖ datadog_agent_remap_datadog_logs_acks ingress throughput -0.37 [-0.54, -0.20]
➖ splunk_hec_route_s3 ingress throughput -0.40 [-0.73, -0.07]
➖ datadog_agent_remap_blackhole ingress throughput -0.56 [-0.65, -0.46]
➖ syslog_log2metric_humio_metrics ingress throughput -0.66 [-0.81, -0.52]
➖ syslog_loki ingress throughput -1.18 [-1.25, -1.11]
➖ syslog_humio_logs ingress throughput -2.04 [-2.17, -1.91]
➖ syslog_log2metric_splunk_hec_metrics ingress throughput -2.09 [-2.22, -1.97]
➖ otlp_http_to_blackhole ingress throughput -2.55 [-2.66, -2.43]
➖ socket_to_socket_blackhole ingress throughput -2.58 [-2.62, -2.54]
➖ http_text_to_http_json ingress throughput -3.25 [-3.38, -3.11]
❌ file_to_blackhole egress throughput -8.41 [-14.85, -1.96]

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

github-actions[bot] avatar Aug 17 '24 02:08 github-actions[bot]

Blocked by https://github.com/Geal/rust-syslog/pull/90

jszwedko avatar Aug 20 '24 00:08 jszwedko

syslog is abandoned. Closing this in favor of #22603

thomasqueirozb avatar Jul 11 '25 13:07 thomasqueirozb

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.

dependabot[bot] avatar Jul 11 '25 13:07 dependabot[bot]