Revert "[SVLS-8160] Add serverless-identifying tag to Azure App Service Windows profiles"

[chouetz]

Reverts #44488, as it's breaking the CI on the main branch of the repo

[kathiehuang]

Sorry about this!! I see these jobs failed: 1 and 2, I will look into them

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: c848b18b-bd0b-420e-85bc-596681f23aaa

Baseline: b4417c0
Comparison: 0080576
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

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

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	-1.64	[-4.49, +1.22]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	tcp_syslog_to_blackhole	ingress throughput	+0.77	[+0.69, +0.85]	1	Logs
➖	otlp_ingest_logs	memory utilization	+0.48	[+0.38, +0.58]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.32	[+0.16, +0.48]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.32	[-1.16, +1.79]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_cumulative	memory utilization	+0.29	[+0.13, +0.45]	1	Logs
➖	file_tree	memory utilization	+0.25	[+0.20, +0.31]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	+0.19	[-0.03, +0.41]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency	egress throughput	+0.08	[-0.42, +0.58]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.06	[-0.32, +0.45]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.01	[-0.11, +0.13]	1	Logs
➖	quality_gate_idle	memory utilization	+0.01	[-0.04, +0.05]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.12, +0.13]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.09, +0.09]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.00	[-0.05, +0.04]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.01	[-0.06, +0.05]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.01	[-0.42, +0.40]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.04	[-0.08, -0.00]	1	Logs bounds checks dashboard
➖	docker_containers_memory	memory utilization	-0.19	[-0.26, -0.12]	1	Logs
➖	ddot_logs	memory utilization	-0.19	[-0.25, -0.13]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.22	[-0.41, -0.02]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.38	[-0.62, -0.15]	1	Logs
➖	ddot_metrics	memory utilization	-0.79	[-1.00, -0.57]	1	Logs
➖	docker_containers_cpu	% cpu utilization	-1.64	[-4.49, +1.22]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	lost_bytes	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
❌	quality_gate_idle_all_features	memory_usage	9/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	bounds checks dashboard

Explanation

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

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

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

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Profiling Replicate Execution Failures (target internal profiling)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle_all_features	baseline	11 (x3)	Oom killed	Debug Dashboard
quality_gate_idle_all_features	comparison	11 (x3)	Oom killed	Debug Dashboard

CI Pass/Fail Decision

❌ Failed. Some Quality Gates were violated.

• quality_gate_idle_all_features, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[agent-platform-auto-pr]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor b4417c0
📊 Static Quality Gates Dashboard

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_msi	-3.36 KiB (0.00% reduction)	571.824 → 571.821 → 982.080
✅	agent_rpm_arm64	-4.84 KiB (0.00% reduction)	687.053 → 687.049 → 693.520
✅	agent_suse_arm64	-4.84 KiB (0.00% reduction)	687.053 → 687.049 → 693.520
✅	docker_agent_arm64	-4.84 KiB (0.00% reduction)	773.824 → 773.819 → 780.200
✅	docker_agent_jmx_arm64	-4.84 KiB (0.00% reduction)	953.422 → 953.417 → 959.800

26 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	705.548 MiB
✅	agent_deb_amd64_fips	700.837 MiB
✅	agent_heroku_amd64	327.030 MiB
✅	agent_rpm_amd64	705.534 MiB
✅	agent_rpm_amd64_fips	700.823 MiB
✅	agent_rpm_arm64_fips	683.189 MiB
✅	agent_suse_amd64	705.534 MiB
✅	agent_suse_amd64_fips	700.823 MiB
✅	agent_suse_arm64_fips	683.189 MiB
✅	docker_agent_amd64	767.691 MiB
✅	docker_agent_jmx_amd64	958.569 MiB
✅	docker_cluster_agent_amd64	180.749 MiB
✅	docker_cluster_agent_arm64	196.602 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.843 MiB
✅	docker_dogstatsd_arm64	37.128 MiB
✅	dogstatsd_deb_amd64	30.066 MiB
✅	dogstatsd_deb_arm64	28.211 MiB
✅	dogstatsd_rpm_amd64	30.066 MiB
✅	dogstatsd_suse_amd64	30.066 MiB
✅	iot_agent_deb_amd64	43.097 MiB
✅	iot_agent_deb_arm64	40.206 MiB
✅	iot_agent_deb_armhf	40.795 MiB
✅	iot_agent_rpm_amd64	43.097 MiB
✅	iot_agent_suse_amd64	43.097 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+16.79 KiB (0.01% increase)	173.268 → 173.285 → 174.490
✅	agent_deb_amd64_fips	-12.05 KiB (0.01% reduction)	172.247 → 172.235 → 173.750
✅	agent_heroku_amd64	+10.73 KiB (0.01% increase)	87.127 → 87.137 → 88.450
✅	agent_msi	+44.0 KiB (0.03% increase)	142.965 → 143.008 → 143.020
✅	agent_rpm_amd64	-30.62 KiB (0.02% reduction)	175.998 → 175.968 → 177.660
✅	agent_rpm_amd64_fips	-39.27 KiB (0.02% reduction)	175.063 → 175.024 → 176.600
✅	agent_rpm_arm64	+23.22 KiB (0.01% increase)	159.423 → 159.445 → 161.260
✅	agent_rpm_arm64_fips	-13.86 KiB (0.01% reduction)	158.726 → 158.712 → 160.550
✅	agent_suse_amd64	-30.62 KiB (0.02% reduction)	175.998 → 175.968 → 177.660
✅	agent_suse_amd64_fips	-39.27 KiB (0.02% reduction)	175.063 → 175.024 → 176.600
✅	agent_suse_arm64	+23.22 KiB (0.01% increase)	159.423 → 159.445 → 161.260
✅	agent_suse_arm64_fips	-13.86 KiB (0.01% reduction)	158.726 → 158.712 → 160.550
✅	docker_agent_amd64	neutral	261.128 MiB
✅	docker_agent_arm64	+5.36 KiB (0.00% increase)	250.122 → 250.128 → 252.630
✅	docker_agent_jmx_amd64	-10.08 KiB (0.00% reduction)	329.772 → 329.762 → 331.080
✅	docker_agent_jmx_arm64	+3.13 KiB (0.00% increase)	314.747 → 314.750 → 317.270
✅	docker_cluster_agent_amd64	neutral	63.863 MiB
✅	docker_cluster_agent_arm64	-9.33 KiB (0.02% reduction)	60.142 → 60.133 → 61.170
✅	docker_cws_instrumentation_amd64	neutral	2.994 MiB
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB
✅	docker_dogstatsd_amd64	neutral	15.037 MiB
✅	docker_dogstatsd_arm64	neutral	14.363 MiB
✅	dogstatsd_deb_amd64	neutral	7.952 MiB
✅	dogstatsd_deb_arm64	neutral	6.827 MiB
✅	dogstatsd_rpm_amd64	neutral	7.962 MiB
✅	dogstatsd_suse_amd64	neutral	7.962 MiB
✅	iot_agent_deb_amd64	neutral	11.291 MiB
✅	iot_agent_deb_arm64	neutral	9.651 MiB
✅	iot_agent_deb_armhf	neutral	9.852 MiB
✅	iot_agent_rpm_amd64	neutral	11.309 MiB
✅	iot_agent_suse_amd64	neutral	11.309 MiB