Skip to content

Include JVM distribution details in crash report#11715

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
masterfrom
gyuheon0h/PROF-15200-include-jvm-dist-crash
Jun 24, 2026
Merged

Include JVM distribution details in crash report#11715
gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
masterfrom
gyuheon0h/PROF-15200-include-jvm-dist-crash

Conversation

@gyuheon0h

@gyuheon0h gyuheon0h commented Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

What Does This Do

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

Motivation

Screenshot 2026-06-23 at 2 12 21 PM

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 Graphite App

gyuheon0h commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

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

@gyuheon0h gyuheon0h changed the title Include JVM distribution details in crash report feat(crashtracking): include JVM distribution details in crash report Jun 23, 2026
@gyuheon0h gyuheon0h added the comp: crash tracking Crash Tracking label Jun 23, 2026
@gyuheon0h
gyuheon0h marked this pull request as ready for review June 23, 2026 18:12
@gyuheon0h
gyuheon0h requested a review from a team as a code owner June 23, 2026 18:12
@gyuheon0h
gyuheon0h requested a review from zhengyu123 June 23, 2026 18:12
@dd-octo-sts

dd-octo-sts Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

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

dd-octo-sts Bot commented Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🟢 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.88 s 13.98 s [-1.5%; +0.2%] (no difference)
startup:insecure-bank:tracing:Agent 12.87 s 12.99 s [-1.7%; -0.2%] (maybe better)
startup:petclinic:appsec:Agent 16.87 s 16.78 s [-0.4%; +1.5%] (no difference)
startup:petclinic:iast:Agent 16.29 s 16.91 s [-8.0%; +0.8%] (no difference)
startup:petclinic:profiling:Agent 16.80 s 16.92 s [-1.7%; +0.4%] (no difference)
startup:petclinic:sca:Agent 16.96 s 16.78 s [+0.1%; +2.0%] (maybe worse)
startup:petclinic:tracing:Agent 16.06 s 16.07 s [-1.1%; +0.9%] (no difference)

Commit: 1f201d7b · 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
zhengyu123 approved these changes Jun 23, 2026
View reviewed changes

@zhengyu123 zhengyu123 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Thanks!

@gyuheon0h
gyuheon0h added this pull request to the merge queue Jun 23, 2026
@dd-octo-sts

dd-octo-sts Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown

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

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 23, 2026
@gyuheon0h

gyuheon0h commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

/merge -c

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

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

@gyuheon0h
gyuheon0h added this pull request to the merge queue Jun 24, 2026
@dd-octo-sts

dd-octo-sts Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jun 24, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-06-24 14:16:09 UTC ℹ️ Start processing command /merge

2026-06-24 14:16:16 UTC ℹ️ MergeQueue: pull request added to the queue

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

2026-06-24 16:16:51 UTC ❌ MergeQueue: The build pipeline has timeout

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

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 24, 2026
@gyuheon0h
gyuheon0h added this pull request to the merge queue Jun 24, 2026
@dd-octo-sts

dd-octo-sts Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jun 24, 2026 •
edited
Loading

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-06-24 16:37:14 UTC ℹ️ Start processing command /merge

2026-06-24 16:37:19 UTC ℹ️ MergeQueue: pull request added to the queue

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

2026-06-24 17:49:35 UTC ℹ️ MergeQueue: This merge request was merged

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 24, 2026
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 42ae556 into master Jun 24, 2026
779 of 781 checks passed
@github-actions github-actions Bot added this to the 1.64.0 milestone Jun 24, 2026
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the gyuheon0h/PROF-15200-include-jvm-dist-crash branch June 24, 2026 17:49
TophrC-dd pushed a commit that referenced this pull request Jun 29, 2026
@gyuheon0h @TophrC-dd
feat(crashtracking): include JVM distribution details in crash report (…
b505e14 
…#11715)

Include JVM distribution details in crash report

Add runtime info to experimental instead

Co-authored-by: devflow.devflow-routing-intake <devflow.devflow-routing-intake@kubernetes.us1.ddbuild.io>
@PerfectSlayer PerfectSlayer changed the title feat(crashtracking): include JVM distribution details in crash report Include JVM distribution details in crash report Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zhengyu123 zhengyu123 zhengyu123 approved these changes

Assignees

No one assigned

Labels

comp: crash tracking Crash Tracking type: feature request

Projects

None yet

Milestone

1.64.0

Development

Successfully merging this pull request may close these issues.

2 participants

@gyuheon0h @zhengyu123