Surface active headless test session and module

[daniel-mohedano]

What Does This Do

• Surfaces the active headless test sessions and modules through CIVisibility.activeTestSessions() and CIVisibility.activeTestModules() for users to add custom tags to them. The events are registered per component (framework) because when running in headless mode each framework instrumentation creates its own session and module.
• Implements top-to-bottom tag propagation configured through an allow-list with DD_CIVISIBILITY_PROPAGATED_TAGS (e.g. DD_CIVISIBILITY_PROPAGATED_TAGS=custom.shard_index,custom.total_shards,build.id)
  • The configured tags will always be propagated from the test event (e.g. session, module or suite) to its children if they are created after the tag is set.

Motivation

These changes allow users to programmatically set custom tags at session and module level.

Alternative approach to #11366

Additional Notes

test-environment-trigger: skip

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level
  • Get more information in this doc

Jira ticket: [SDTEST-3804]

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Startup Time

Scenario	This PR	master	Change
insecure-bank / iast	14,713 ms	14,664 ms	+0.3%
insecure-bank / tracing	13,588 ms	13,725 ms	-1.0%
petclinic / appsec	16,521 ms	16,227 ms	+1.8%
petclinic / iast	16,526 ms	16,514 ms	+0.1%
petclinic / profiling	15,394 ms	16,574 ms	-7.1%
petclinic / tracing	14,946 ms	15,654 ms	-4.5%

Commit: a007d25b · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.