chore(deps): Bump metrics from 0.21.1 to 0.22.0

[dependabot[bot]]

Bumps metrics from 0.21.1 to 0.22.0.

Commits

• da3edb3 (cargo-release) version 0.22.0
• 3b3a991 chore: clean up some clippy lints
• c04acc4 chore(metrics-observer,metrics-exporter-tcp): update to prost 0.12
• 4bc6c26 update RELEASES.md
• 0e5874d enhancement(metrics): add support for scoped (local) recorders (#414)
• 49d96b1 Update ordered-float requirement from 3.4 to 4.2 (#421)
• 545878b Update quanta requirement from 0.11 to 0.12 (#396)
• 851c930 update changelog
• e9b8230 Try other resolved addresses if the first one fails (#429)
• 52f5a50 Add a clippy CI check (#416) (#417)
• Additional commits viewable in compare view

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

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

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

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

[github-actions[bot]]

Your preview site for the VRL Playground will be ready in a few minutes, please allow time for it to build.

Heres your preview link: VRL Playground preview

[github-actions[bot]]

Your preview site for the Rust Doc will be ready in a few minutes, please allow time for it to build.

Heres your preview link: Rust Doc preview

[github-actions[bot]]

Your preview site for the vector.dev will be ready in a few minutes, please allow time for it to build.

Heres your preview link: vector.dev preview

[jszwedko]

@dependabot rebase

[neuronull]

@dependabot rebase

[dependabot[bot]]

A newer version of metrics exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[datadog-vectordotdev[bot]]

Datadog Report

Branch report: dependabot/cargo/metrics-0.22.0 Commit report: a5e1edf Test service: vector

:x: 4 Failed (0 Known Flaky), 9 Passed, 0 Skipped, 24m 0.61s Total Time

:x: Failed Tests (4)

• sinks::amqp::integration_tests::amqp_happy_path_plaintext - vector - Details

  Expand for error

  est failed, but output was not captured
  

• sinks::amqp::integration_tests::amqp_round_trip_plaintext - vector - Details

  Expand for error

  est failed, but output was not captured
  

• sources::amqp::integration_test::amqp_source_consume_event - vector - Details

  Expand for error

  est failed, but output was not captured
  

• sources::amqp::integration_test::amqp_tls_source_consume_event - vector - Details

  Expand for error

  est failed, but output was not captured
  

[datadog-vectordotdev[bot]]

Datadog Report

Branch report: dependabot/cargo/metrics-0.22.0 Commit report: 9799aca Test service: vector

:white_check_mark: 0 Failed, 426 Passed, 0 Skipped, 4m 11.11s Total Time

[github-actions[bot]]

Regression Detector Results

Run ID: 0fe1ee7e-367d-40f5-8075-eb890b9a17e6 Metrics dashboard

Baseline: 0c1d3b1ca1250e73237ba7b9e20218c2e53cdfad Comparison: 4eb84fb4aeabc5d2d8f3a5b4532bde6b93f80b54

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	-0.20	[-7.10, +6.69]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+2.26	[+2.04, +2.48]
➖	socket_to_socket_blackhole	ingress throughput	+1.29	[+1.24, +1.33]
➖	fluent_elasticsearch	ingress throughput	+0.73	[+0.24, +1.22]
➖	syslog_humio_logs	ingress throughput	+0.71	[+0.60, +0.82]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	+0.41	[+0.30, +0.53]
➖	datadog_agent_remap_datadog_logs	ingress throughput	+0.26	[+0.04, +0.48]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.01	[-0.10, +0.11]
➖	http_to_http_noack	ingress throughput	+0.00	[-0.12, +0.13]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.13, +0.12]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.09, +0.06]
➖	http_text_to_http_json	ingress throughput	-0.10	[-0.21, +0.01]
➖	http_to_http_json	ingress throughput	-0.11	[-0.19, -0.04]
➖	file_to_blackhole	egress throughput	-0.20	[-7.10, +6.69]
➖	otlp_grpc_to_blackhole	ingress throughput	-0.22	[-0.34, -0.11]
➖	splunk_hec_route_s3	ingress throughput	-0.27	[-0.59, +0.04]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	-0.40	[-0.51, -0.30]
➖	http_to_http_acks	ingress throughput	-0.45	[-1.75, +0.86]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-0.53	[-0.69, -0.37]
➖	http_to_s3	ingress throughput	-0.76	[-1.03, -0.49]
➖	datadog_agent_remap_blackhole	ingress throughput	-0.82	[-0.92, -0.71]
➖	syslog_splunk_hec_logs	ingress throughput	-0.90	[-1.00, -0.81]
➖	syslog_log2metric_humio_metrics	ingress throughput	-0.97	[-1.14, -0.80]
➖	syslog_loki	ingress throughput	-1.69	[-1.77, -1.61]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.77	[-1.90, -1.64]
➖	http_elasticsearch	ingress throughput	-2.06	[-2.26, -1.86]
➖	otlp_http_to_blackhole	ingress throughput	-4.38	[-4.59, -4.18]

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]]

Regression Detector Results

Run ID: d345d34b-5e1d-4889-b0ee-f45c15f94480 Metrics dashboard

Baseline: fd35e1c54c33e297cdfd48ecfeae344947f303fb Comparison: b2aea48a374259fd289f3ee3bc9a23eb0446b025

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	+40.37	[+32.36, +48.39]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	links
✅	file_to_blackhole	egress throughput	+40.37	[+32.36, +48.39]
➖	splunk_hec_route_s3	ingress throughput	+1.92	[+1.59, +2.25]
➖	http_elasticsearch	ingress throughput	+1.58	[+1.37, +1.80]
➖	syslog_log2metric_humio_metrics	ingress throughput	+1.46	[+1.33, +1.60]
➖	syslog_humio_logs	ingress throughput	+0.94	[+0.79, +1.10]
➖	syslog_splunk_hec_logs	ingress throughput	+0.43	[+0.33, +0.53]
➖	datadog_agent_remap_datadog_logs_acks	ingress throughput	+0.41	[+0.19, +0.62]
➖	datadog_agent_remap_blackhole_acks	ingress throughput	+0.40	[+0.28, +0.52]
➖	splunk_hec_indexer_ack_blackhole	ingress throughput	+0.01	[-0.07, +0.09]
➖	splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.00	[-0.11, +0.11]
➖	splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.00	[-0.11, +0.10]
➖	http_to_http_acks	ingress throughput	-0.02	[-1.34, +1.30]
➖	http_to_http_json	ingress throughput	-0.11	[-0.19, -0.03]
➖	http_to_http_noack	ingress throughput	-0.13	[-0.25, -0.01]
➖	syslog_log2metric_splunk_hec_metrics	ingress throughput	-0.18	[-0.29, -0.07]
➖	syslog_log2metric_tag_cardinality_limit_blackhole	ingress throughput	-0.65	[-0.74, -0.56]
➖	http_to_s3	ingress throughput	-0.69	[-0.96, -0.42]
➖	http_text_to_http_json	ingress throughput	-0.80	[-0.97, -0.63]
➖	fluent_elasticsearch	ingress throughput	-1.23	[-1.72, -0.75]
➖	datadog_agent_remap_blackhole	ingress throughput	-1.56	[-1.67, -1.45]
➖	syslog_regex_logs2metric_ddmetrics	ingress throughput	-1.70	[-1.87, -1.53]
➖	otlp_grpc_to_blackhole	ingress throughput	-1.74	[-1.87, -1.62]
➖	syslog_loki	ingress throughput	-1.99	[-2.10, -1.88]
➖	socket_to_socket_blackhole	ingress throughput	-2.57	[-2.63, -2.52]
➖	datadog_agent_remap_datadog_logs	ingress throughput	-4.04	[-4.30, -3.78]
➖	otlp_http_to_blackhole	ingress throughput	-4.20	[-4.35, -4.05]

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