feat(crashtracking): include JVM distribution details in crash report

[gyuheon0h]

What Does This Do

Read JVM distribution details in Hotspot and J9 parser and include the details in crash report

Motivation

Additional Notes

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 (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[gyuheon0h]

• feat(crashtracking): include JVM distribution details in crash report #11715 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[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	14.00 s	13.96 s	[-0.4%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	13.07 s	[-2.0%; -0.6%] (maybe better)
startup:petclinic:appsec:Agent	16.92 s	16.85 s	[-0.6%; +1.5%] (no difference)
startup:petclinic:iast:Agent	16.89 s	17.01 s	[-1.5%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.67 s	16.78 s	[-1.5%; +0.2%] (no difference)
startup:petclinic:sca:Agent	16.90 s	16.79 s	[-0.2%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	15.54 s	16.02 s	[-7.1%; +1.1%] (no difference)

Commit: 33ebcc5d · 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.

[zhengyu123]

LGTM, Thanks!

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-23 20:43:13 UTC ℹ️ Start processing command /merge

---

2026-06-23 20:43:19 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-23 20:45:39 UTC ⚠️ MergeQueue: This merge request build was cancelled

gyuheon.oh@datadoghq.com cancelled this merge request build

[gyuheon0h]

/merge -c

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-23 20:45:21 UTC ℹ️ Start processing command /merge -c