usm: classification: tls: Classify more protocols if TLS monitoring is enabled

[guyarb]

trafficstars

What does this PR do?

USM will try to classify http, http2, amqp, redis, mongo, postgres, and mysql. In the future we should add kafka and grpc.

The PR creates a different entrypoint for TLS (classify_protocol_for_tls_dispatcher) as in the plaintext version, we share classification entrypoint with NPM, and we can rely only for classification of protocols we support of parsing. But, in TLS mode, only USM has the ability of classifying the protocols, thus we should try all protocols.

Currently I left out gRPC and Kafka classifications, as those require a more advanced parsing, and we need to create dedicated method to make that happen.

TODO list:

• [ ] Add TLS classification kitchen tests
• [ ] load test
• [ ] dogfooding

Motivation

Matching our TLS classification with plaintext classification.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

• [ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• [ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• [ ] A release note has been added or the changelog/no-changelog label has been applied.
• [ ] Changed code has automated tests for its functionality.
• [ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
• [ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• [ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• [ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
• [ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• [ ] If applicable, the config template has been updated.

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: 51fc68ef-83b3-43e7-985f-8631e3bfbca1 Baseline: a4b1d2a0444c33b25fac624bd886ab1257b68f14 Comparison: be4427129da32f251056fb49cf9fa3a44828949a 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.

Experiments ignored for regressions

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

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_tree	memory utilization	+0.53	[+0.47, +0.59]
➖	idle	memory utilization	-0.34	[-0.36, -0.31]
➖	file_to_blackhole	% cpu utilization	-0.55	[-7.09, +6.00]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.97	[-0.46, +2.40]
➖	process_agent_real_time_mode	memory utilization	+0.62	[+0.59, +0.66]
➖	file_tree	memory utilization	+0.53	[+0.47, +0.59]
➖	process_agent_standard_check	memory utilization	+0.25	[+0.21, +0.29]
➖	process_agent_standard_check_with_stats	memory utilization	+0.19	[+0.15, +0.23]
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.04, +0.04]
➖	trace_agent_msgpack	ingress throughput	+0.00	[-0.02, +0.02]
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.05, +0.05]
➖	trace_agent_json	ingress throughput	-0.00	[-0.03, +0.03]
➖	tcp_syslog_to_blackhole	ingress throughput	-0.28	[-0.34, -0.22]
➖	idle	memory utilization	-0.34	[-0.36, -0.31]
➖	file_to_blackhole	% cpu utilization	-0.55	[-7.09, +6.00]
➖	otel_to_otel_logs	ingress throughput	-2.61	[-3.32, -1.90]

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