fix(azure_blob sink): Base Content-Type on encoder and not compression

[stemjacobs]

Description

Update setting of the content type associated with a blob to be the uncompressed underlying encoded type.

Issues

The following open issues are concerned with this PR:
Closes: #18183

[bits-bot]

All committers have signed the CLA.

[netlify]

✅ Deploy Preview for vrl-playground canceled.

Name	Link
🔨 Latest commit	ead6162
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/64d2842b7039110008d9b8ea

[netlify]

✅ Deploy Preview for vector-project canceled.

Name	Link
🔨 Latest commit	ead6162
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/64d2842b03244c0008217913

[dsmith3197]

Looks good, will approve once comment is addressed.

[dsmith3197]

@stemjacobs, could you format the code by running cargo vdev fmt? Thanks 🙂

That's the reason checks are failing

cargo vdev check fmt
File "src/sinks/azure_blob/integration_tests.rs" contains trailing spaces in some of the lines
File "src/sinks/azure_blob/request_builder.rs" doesn't end with a newline
Error: command: cd "/home/runner/work/vector/vector" && "/home/runner/work/vector/vector/scripts/check-style.sh"
  failed with exit code: 1
make: *** [Makefile:453: check-fmt] Error 1

[stemjacobs]

@stemjacobs, could you format the code by running cargo vdev fmt? Thanks 🙂

That's the reason checks are failing

cargo vdev check fmt
File "src/sinks/azure_blob/integration_tests.rs" contains trailing spaces in some of the lines
File "src/sinks/azure_blob/request_builder.rs" doesn't end with a newline
Error: command: cd "/home/runner/work/vector/vector" && "/home/runner/work/vector/vector/scripts/check-style.sh"
  failed with exit code: 1
make: *** [Makefile:453: check-fmt] Error 1

Done and done, sorry about that.

[github-actions]

Regression Detector Results

Run ID: 7a9dc169-e56b-459c-9b26-b9db32c23a0c
Baseline: e0590da
Comparison: 985c328
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
file_to_blackhole	egress throughput	+3.92	[+0.14, +7.71]	81.63%
syslog_regex_logs2metric_ddmetrics	ingress throughput	+2.07	[+1.76, +2.38]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	+1.67	[+1.58, +1.77]	100.00%
syslog_splunk_hec_logs	ingress throughput	+1.62	[+1.53, +1.72]	100.00%
datadog_agent_remap_datadog_logs_acks	ingress throughput	+1.61	[+1.47, +1.75]	100.00%
datadog_agent_remap_blackhole	ingress throughput	+1.32	[+1.20, +1.43]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	+0.86	[+0.75, +0.97]	100.00%
splunk_hec_route_s3	ingress throughput	+0.86	[+0.73, +1.00]	100.00%
http_to_http_acks	ingress throughput	+0.61	[-0.64, +1.86]	46.86%
datadog_agent_remap_blackhole_acks	ingress throughput	+0.40	[+0.30, +0.51]	100.00%
http_to_s3	ingress throughput	+0.06	[-0.13, +0.26]	32.18%
enterprise_http_to_http	ingress throughput	+0.06	[+0.02, +0.10]	92.49%
otlp_grpc_to_blackhole	ingress throughput	+0.02	[-0.09, +0.12]	14.50%
fluent_elasticsearch	ingress throughput	+0.00	[-0.00, +0.00]	42.20%
http_to_http_json	ingress throughput	-0.00	[-0.04, +0.04]	2.28%
splunk_hec_indexer_ack_blackhole	ingress throughput	-0.01	[-0.05, +0.03]	17.31%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.01	[-0.05, +0.04]	17.86%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.01	[-0.08, +0.06]	15.15%
http_to_http_noack	ingress throughput	-0.01	[-0.07, +0.05]	22.61%
syslog_humio_logs	ingress throughput	-0.82	[-0.89, -0.75]	100.00%
otlp_http_to_blackhole	ingress throughput	-1.28	[-1.44, -1.13]	100.00%
socket_to_socket_blackhole	ingress throughput	-1.34	[-1.39, -1.28]	100.00%
http_text_to_http_json	ingress throughput	-1.55	[-1.62, -1.48]	100.00%
syslog_loki	ingress throughput	-1.75	[-1.81, -1.69]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	-2.32	[-2.45, -2.19]	100.00%

[github-actions]

Regression Detector Results

Run ID: 48869e2e-e4a8-4db6-be87-3f111ded3bde
Baseline: e476e12
Comparison: 4a049d4
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
syslog_regex_logs2metric_ddmetrics	ingress throughput	+3.50	[+3.19, +3.80]	100.00%
file_to_blackhole	egress throughput	+2.64	[-1.13, +6.41]	63.00%
splunk_hec_route_s3	ingress throughput	+1.32	[+1.15, +1.48]	100.00%
datadog_agent_remap_blackhole	ingress throughput	+1.04	[+0.91, +1.16]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	+0.97	[+0.89, +1.06]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+0.55	[+0.45, +0.65]	100.00%
http_to_s3	ingress throughput	+0.53	[+0.34, +0.72]	99.96%
socket_to_socket_blackhole	ingress throughput	+0.08	[+0.02, +0.14]	90.41%
enterprise_http_to_http	ingress throughput	+0.04	[+0.00, +0.08]	82.26%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.02	[-0.04, +0.09]	36.54%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.02	[-0.02, +0.06]	42.48%
fluent_elasticsearch	ingress throughput	+0.00	[-0.00, +0.00]	66.61%
http_to_http_json	ingress throughput	-0.00	[-0.04, +0.04]	3.13%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.01	[-0.05, +0.04]	18.03%
http_to_http_noack	ingress throughput	-0.02	[-0.08, +0.04]	27.35%
datadog_agent_remap_datadog_logs	ingress throughput	-0.23	[-0.32, -0.13]	99.80%
datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.35	[-0.46, -0.25]	100.00%
syslog_humio_logs	ingress throughput	-0.45	[-0.53, -0.37]	100.00%
http_to_http_acks	ingress throughput	-0.71	[-1.94, +0.51]	54.51%
http_text_to_http_json	ingress throughput	-0.79	[-0.86, -0.73]	100.00%
otlp_http_to_blackhole	ingress throughput	-0.90	[-1.04, -0.75]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	-1.32	[-1.41, -1.23]	100.00%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.35	[-1.48, -1.22]	100.00%
syslog_splunk_hec_logs	ingress throughput	-1.83	[-1.91, -1.75]	100.00%
syslog_loki	ingress throughput	-2.74	[-2.82, -2.66]	100.00%