Add IDM as co-owners for all instrumentations

[sarahchen6]

What Does This Do

Add IDM as co-owners for all instrumentations to ease reviewing PRs such as #12266 that update instrumentation versions -- with this change, we should only need one review from an IDM team member instead of reviews from each team with updated instrumentation versions.

Also split all gradle.lockfiles between IDM (instrumentation-related) and LP (other) for similar reasons.

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

Jira ticket: [PROJ-IDENT]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f835f793e3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-official]

The final build file rules remove the IDM owner from instrumentation build files. Instrumentation version changes can still require a review from the language platform team.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit f835f79 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 58.79% (-0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 95c19ca | Docs | View more details | 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	14.89 s	14.62 s	[+0.9%; +2.7%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.61 s	13.75 s	[-1.8%; -0.3%] (maybe better)
startup:petclinic:appsec:Agent	16.98 s	16.67 s	[+1.0%; +2.7%] (significantly worse)
startup:petclinic:iast:Agent	16.91 s	16.98 s	[-1.1%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.70 s	16.76 s	[-1.6%; +0.9%] (no difference)
startup:petclinic:sca:Agent	16.84 s	16.59 s	[+0.4%; +2.5%] (maybe worse)
startup:petclinic:tracing:Agent	16.21 s	16.05 s	[+0.1%; +1.9%] (maybe worse)

Commit: 95c19ca3 · 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-official]

The final generic build file rules override the earlier instrumentation rule. Instrumentation build files do not request IDM review, so the main ownership goal is incomplete.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 4f1d304 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[sarahchen6]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-25 19:39:05 UTC ℹ️ Start processing command /merge

---

2026-08-25 19:39:10 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-25 20:10:56 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for c91327b:

• test_inst: [semeru11, 7/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[sarahchen6]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-25 20:13:16 UTC ℹ️ Start processing command /merge

---

2026-08-25 20:13:20 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-25 21:06:36 UTC ℹ️ MergeQueue: This merge request was merged