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

chore(releasing): Regenerate k8s manifests for chart 0.32.1 #20280

Merged
merged 1 commit into from
May 3, 2024

Conversation

jszwedko
Copy link
Member

No description provided.

@jszwedko jszwedko added the no-changelog Changes in this PR do not need user-facing explanations in the release changelog label Apr 10, 2024
@github-actions github-actions bot added the domain: releasing Anything related to releasing Vector label Apr 10, 2024
@jszwedko jszwedko added this pull request to the merge queue Apr 17, 2024
Copy link

Regression Detector Results

Run ID: 2c7c200c-7b5d-483d-8523-3fcb06f02e9a
Baseline: ead0755
Comparison: 9d92e64
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 ingress throughput +2.82 [+2.67, +2.98]
http_to_http_acks ingress throughput +0.90 [-0.46, +2.26]
syslog_loki ingress throughput +0.86 [+0.80, +0.91]
syslog_log2metric_humio_metrics ingress throughput +0.78 [+0.69, +0.88]
http_elasticsearch ingress throughput +0.46 [+0.39, +0.53]
otlp_http_to_blackhole ingress throughput +0.39 [+0.25, +0.54]
http_text_to_http_json ingress throughput +0.32 [+0.19, +0.44]
syslog_humio_logs ingress throughput +0.26 [+0.09, +0.43]
splunk_hec_route_s3 ingress throughput +0.15 [-0.31, +0.61]
http_to_http_noack ingress throughput +0.08 [-0.02, +0.17]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +0.06 [-0.11, +0.23]
http_to_http_json ingress throughput +0.06 [-0.02, +0.14]
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.14, +0.14]
datadog_agent_remap_datadog_logs ingress throughput -0.01 [-0.13, +0.10]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.05 [-0.17, +0.06]
enterprise_http_to_http ingress throughput -0.07 [-0.15, +0.00]
http_to_s3 ingress throughput -0.16 [-0.44, +0.12]
otlp_grpc_to_blackhole ingress throughput -0.32 [-0.42, -0.23]
fluent_elasticsearch ingress throughput -0.39 [-0.87, +0.09]
syslog_log2metric_splunk_hec_metrics ingress throughput -0.68 [-0.85, -0.52]
datadog_agent_remap_datadog_logs_acks ingress throughput -0.83 [-0.92, -0.74]
socket_to_socket_blackhole ingress throughput -0.84 [-0.92, -0.76]
syslog_splunk_hec_logs ingress throughput -0.86 [-0.94, -0.78]
datadog_agent_remap_blackhole_acks ingress throughput -1.61 [-1.69, -1.52]
syslog_regex_logs2metric_ddmetrics ingress throughput -1.67 [-1.77, -1.56]
file_to_blackhole egress throughput -3.14 [-5.64, -0.64]

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

Copy link

Regression Detector Results

Run ID: 71fad647-7e86-4ec9-a84b-d1b3e9c14d11
Baseline: 7869a78
Comparison: 841bff0
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

Significant changes in experiment optimization goals

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

perf experiment goal Δ mean % Δ mean % CI
syslog_log2metric_splunk_hec_metrics ingress throughput -5.47 [-5.63, -5.31]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI
syslog_humio_logs ingress throughput +3.65 [+3.50, +3.81]
syslog_regex_logs2metric_ddmetrics ingress throughput +2.48 [+2.35, +2.62]
http_elasticsearch ingress throughput +0.66 [+0.58, +0.74]
http_text_to_http_json ingress throughput +0.61 [+0.48, +0.74]
otlp_http_to_blackhole ingress throughput +0.55 [+0.44, +0.67]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.53 [+0.45, +0.60]
fluent_elasticsearch ingress throughput +0.36 [-0.12, +0.84]
datadog_agent_remap_blackhole_acks ingress throughput +0.36 [+0.26, +0.46]
syslog_splunk_hec_logs ingress throughput +0.19 [+0.11, +0.27]
http_to_s3 ingress throughput +0.16 [-0.12, +0.44]
http_to_http_noack ingress throughput +0.10 [+0.03, +0.18]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +0.06 [-0.08, +0.20]
http_to_http_json ingress throughput +0.02 [-0.05, +0.09]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.14, +0.14]
splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.15, +0.14]
datadog_agent_remap_blackhole ingress throughput -0.02 [-0.13, +0.09]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.04 [-0.15, +0.07]
enterprise_http_to_http ingress throughput -0.07 [-0.12, -0.01]
socket_to_socket_blackhole ingress throughput -0.16 [-0.24, -0.08]
splunk_hec_route_s3 ingress throughput -0.27 [-0.74, +0.21]
otlp_grpc_to_blackhole ingress throughput -0.32 [-0.41, -0.22]
datadog_agent_remap_datadog_logs ingress throughput -0.52 [-0.63, -0.40]
syslog_loki ingress throughput -0.84 [-0.89, -0.79]
file_to_blackhole egress throughput -1.45 [-3.88, +0.99]
http_to_http_acks ingress throughput -1.96 [-3.30, -0.63]
syslog_log2metric_humio_metrics ingress throughput -2.59 [-2.76, -2.42]
syslog_log2metric_splunk_hec_metrics ingress throughput -5.47 [-5.63, -5.31]

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-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 17, 2024
@jszwedko jszwedko added this pull request to the merge queue May 3, 2024
Merged via the queue into master with commit 4850a9a May 3, 2024
54 checks passed
@jszwedko jszwedko deleted the jszwedko/manifests-0.32.1 branch May 3, 2024 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: releasing Anything related to releasing Vector no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants