Add datadog.common.filesystem to list of bootstrap package prefixes

[mcculls]

Motivation

Hopefully fixes the following log-spam when running instrumentation tests on CI:

14:42:03.913 [Test worker] DEBUG datadog.trace.bootstrap.config.provider.StableConfigSource - Stable configuration file found at path: /etc/datadog-agent/application_monitoring.yaml
14:42:03.920 [Test worker] ERROR datadog.trace.bootstrap.config.provider.StableConfigSource - Unexpected error while reading stable configuration file: /etc/datadog-agent/application_monitoring.yaml
java.lang.NoClassDefFoundError: datadog/common/filesystem/Files
	at datadog.trace.bootstrap.config.provider.StableConfigSource.<init>(StableConfigSource.java:37)
	at datadog.trace.bootstrap.config.provider.StableConfigSource.<clinit>(StableConfigSource.java:22)
	at datadog.trace.bootstrap.config.provider.ConfigProvider.createDefault(ConfigProvider.java:523)
	at datadog.trace.bootstrap.config.provider.ConfigProvider$Singleton.<clinit>(ConfigProvider.java:34)
	at datadog.trace.bootstrap.config.provider.ConfigProvider.getInstance(ConfigProvider.java:504)
	at datadog.trace.api.InstrumenterConfig.<clinit>(InstrumenterConfig.java:749)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:264)
	at datadog.trace.test.util.DDSpecification.makeConfigInstanceModifiable(DDSpecification.groovy:70)
	at datadog.trace.test.util.DDSpecification.<clinit>(DDSpecification.groovy:29)

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
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[datadog-prod-us1-3]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 60.97% (+3.93%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4ad233a | Docs | Datadog PR Page | Give us feedback!}

[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

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.94 s	14.00 s	[-1.1%; +0.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	13.00 s	[-1.1%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.84 s	16.67 s	[+0.0%; +2.1%] (maybe worse)
startup:petclinic:iast:Agent	16.87 s	16.95 s	[-1.3%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.10 s	16.87 s	[-8.9%; -0.3%] (maybe better)
startup:petclinic:sca:Agent	16.92 s	16.73 s	[+0.1%; +2.2%] (maybe worse)
startup:petclinic:tracing:Agent	15.94 s	15.63 s	[-2.4%; +6.2%] (no difference)

Commit: 4ad233ae · 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.

[datadog-prod-us1-3]

More details

This PR adds datadog.common.filesystem to the bootstrap package prefixes, fixing NoClassDefFoundError when StableConfigSource (which uses Files.exists()) initializes during test setup. The change is minimal, non-breaking, and correctly synchronized across both the main constant list and its test copy. No behavioral regressions detected.

Was this helpful? React 👍 or 👎

_{📊 Validated against 3 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 4ad233a · What is Autotest? · Any feedback? Reach out in #autotest}

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-10 23:19:24 UTC ℹ️ Start processing command /merge

---

2026-07-10 23:19:29 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-07-11 01:19:47 UTC ❌ MergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build 4949855003353360450 took longer than expected. The current limit for the base branch 'master' is 120 minutes.

[AlexeyKuznetsov-DD]

Any chance to cover with test? If that possible at all?

[mcculls]

I'd prefer if we had a general rule about unexpected exceptions in test logs - but that wouldn't be part of this PR, more a new test utility. You'd have to filter out expected exceptions but having that general check enabled across CI would have caught this as well as some previous cases which I only spotted manually.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-11 11:11:38 UTC ℹ️ Start processing command /merge

---

2026-07-11 11:11:42 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-07-11 13:12:03 UTC ❌ MergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build 14005003475570071 took longer than expected. The current limit for the base branch 'master' is 120 minutes.