[ASCII-2601] Create SSI component

[louis-cqrl]

What does this PR do?

This PR adds the SSI comp inside tracer bundle to display SSI status and possibly add debug information inside flares

Motivation

Unlike the agent, there is no troubleshooting tool for the Single Step APM setup on a host which makes it very difficult for customers, implementation services’ team and TSEs/TEEs to understand what really happened if users do not see traces for their services when setting APM through Single Step Instrumentation. This has been one of the biggest feedback.

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

[cit-pr-commenter]

Go Package Import Differences

Baseline: 623bea0
Comparison: 0fe4138

binary	os	arch	change
trace-agent	linux	amd64	+3, -0 +github.com/DataDog/datadog-agent/comp/trace/ssi/def +github.com/DataDog/datadog-agent/comp/trace/ssi/fx +github.com/DataDog/datadog-agent/comp/trace/ssi/impl
trace-agent	linux	arm64	+3, -0 +github.com/DataDog/datadog-agent/comp/trace/ssi/def +github.com/DataDog/datadog-agent/comp/trace/ssi/fx +github.com/DataDog/datadog-agent/comp/trace/ssi/impl
trace-agent	windows	amd64	+3, -0 +github.com/DataDog/datadog-agent/comp/trace/ssi/def +github.com/DataDog/datadog-agent/comp/trace/ssi/fx +github.com/DataDog/datadog-agent/comp/trace/ssi/impl
trace-agent	darwin	amd64	+3, -0 +github.com/DataDog/datadog-agent/comp/trace/ssi/def +github.com/DataDog/datadog-agent/comp/trace/ssi/fx +github.com/DataDog/datadog-agent/comp/trace/ssi/impl
trace-agent	darwin	arm64	+3, -0 +github.com/DataDog/datadog-agent/comp/trace/ssi/def +github.com/DataDog/datadog-agent/comp/trace/ssi/fx +github.com/DataDog/datadog-agent/comp/trace/ssi/impl
heroku-trace-agent	linux	amd64	+3, -0 +github.com/DataDog/datadog-agent/comp/trace/ssi/def +github.com/DataDog/datadog-agent/comp/trace/ssi/fx +github.com/DataDog/datadog-agent/comp/trace/ssi/impl

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 935f0b6e-ea52-460c-bd87-3cd4573bf099

Baseline: 623bea0
Comparison: 0fe4138
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	tcp_syslog_to_blackhole	ingress throughput	+1.72	[+1.67, +1.77]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.22	[-0.24, +0.68]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.08	[-0.03, +0.20]	1	Logs bounds checks dashboard
➖	file_to_blackhole_300ms_latency	egress throughput	+0.07	[-0.57, +0.70]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.01	[-0.09, +0.11]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.01	[-0.81, +0.82]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.00	[-0.84, +0.84]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	-0.00	[-0.82, +0.82]	1	Logs
➖	file_tree	memory utilization	-0.00	[-0.12, +0.12]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.04	[-0.77, +0.69]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.08	[-0.84, +0.69]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.11	[-0.90, +0.69]	1	Logs
➖	quality_gate_idle	memory utilization	-0.32	[-0.36, -0.27]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.96	[-1.69, -0.22]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-1.02	[-1.71, -0.32]	1	Logs
➖	quality_gate_logs	% cpu utilization	-1.49	[-4.41, +1.43]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	file_to_blackhole_500ms_latency	lost_bytes	8/10
❌	file_to_blackhole_300ms_latency	lost_bytes	9/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	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_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[agent-platform-auto-pr]

Package size comparison

Comparison with ancestor 623bea046b6c811266d986ae1329b584f107e13a

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.06MB	⚠️	1271.35MB	1271.29MB	140.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.21MB	113.21MB	10.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.32MB	78.32MB	10.00MB
datadog-heroku-agent-amd64-deb	0.06MB	⚠️	526.50MB	526.44MB	70.00MB
datadog-agent-x86_64-rpm	0.06MB	⚠️	1280.58MB	1280.52MB	140.00MB
datadog-agent-x86_64-suse	0.06MB	⚠️	1280.58MB	1280.52MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.28MB	113.28MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.27MB	113.27MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.40MB	78.40MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.40MB	78.40MB	10.00MB
datadog-agent-arm64-deb	0.06MB	⚠️	1005.50MB	1005.44MB	140.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.70MB	108.70MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.59MB	55.59MB	10.00MB
datadog-agent-aarch64-rpm	0.06MB	⚠️	1014.71MB	1014.66MB	140.00MB
datadog-iot-agent-aarch64-rpm	0.00MB	✅	108.77MB	108.77MB	10.00MB

Decision

⚠️ Warning

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=51066767 --os-family=ubuntu

Note: This applies to commit 0fe4138