[sethsamuel]

What does this PR do?

Add opt-in Database Monitoring (dbm: true) for IBM Db2 LUW:

• Collect per-query execution counts, elapsed and CPU time, rows read/returned, and lock waits from the package cache. Send obfuscated full query text with table, command, and SQL-comment metadata.
• Add instance metadata and configurable database identifiers shared by DBM payloads and integration metrics. Attribute monitoring queries to the Agent, and use the shared DBM framework for background collection, custom queries, and collector health.
• Document fixed-server deployment and HADR behavior. Add unit, integration, packaged-Agent E2E, and HADR takeover coverage, with amd64 GitLab CI environments for Db2 11.1, 11.5, and 12.1.

Validation: 49 unit tests passed, along with ddev lint and configuration/model validation. Live Db2 integration and E2E tests were not run locally.

Motivation

This is the first merge of the Db2 DBM development branch into master, bringing query metrics and full query text into the existing IBM Db2 integration. Schema collection remains a separate follow-up in #25330.

Earlier component reviews:

• Query metrics and identity: #25486, #25487, #25516, #25748, #25749.
• Query text and metadata: #25531, #25532.
• Controls and health: #25642, #25643, #25645, #25646, #25726.
• Waits, versions, and HADR: #25648, #25649, #25661, #25741.

Checklist before requesting review

• I self-reviewed the full diff, and this description matches the final change
• Tests cover the change, or this description explains why none are needed
• Automated review comments, including Codex review, were addressed or answered
• I, the human author, understand this change, can explain it to reviewers, and believe it meets the repository standards

[datadog-prod-us1-4]

   

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 94.65%
• Overall Coverage: 94.99% (+5.42%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1092181 | Docs | View more details | Give us feedback!}

[cit-pr-commenter-54b7da]

evalya-impact-summary

Evalya CI impact

Impact analysis: RUN-ALL — every test task will run
Trigger:         empty diff (default branch, scheduled run, or shallow-clone fallback)
Test tasks:      0 (all selected)
Publish tasks:   4 (always emitted)
Changed files:   0

Full impact report
Learn more about CI impact filtering

[dd-octo-sts]

Disk usage change

Commit 1092181 compared against 1e3691a.

Uncompressed

linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
🔺 +26.85 KiB	🔺 +26.85 KiB	🔺 +26.85 KiB	🔺 +26.85 KiB	🔺 +26.85 KiB

Details

Name	Version	Type	linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
ibm_db2	4.4.0	Integration	🔺 +26.85 KiB	🔺 +26.85 KiB	🔺 +26.85 KiB	🔺 +26.85 KiB	🔺 +26.85 KiB

Compressed

linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
🔺 +9.17 KiB	🔺 +9.17 KiB	🔺 +9.17 KiB	🔺 +9.17 KiB	🔺 +9.17 KiB

Details

Name	Version	Type	linux-aarch64	linux-x86_64	macos-aarch64	macos-x86_64	windows-x86_64
ibm_db2	4.4.0	Integration	🔺 +9.17 KiB	🔺 +9.17 KiB	🔺 +9.17 KiB	🔺 +9.17 KiB	🔺 +9.17 KiB

[AAraKKe]

Hi team! Some comments below, I understand why you are trying to run tests in GitLab but that is a hard blocker to merge this PR, take a look at the comment about that as the strongest one that I have. I would propose to drop 11.1 al together since it is fully EOL with not even extended support and supporting it in GitLab means not knowing anything about the tests on the integration at all in the standard quality validation checks we currently have.

[dd-octo-sts]

✅ Dispatcher tests: passed

Dispatcher beta: informational only
Existing CI remains the merge signal.

  10/10 jobs

✅ 10 passed · nothing failed

Batches · ✅ batch-01 10/10

_{Dispatcher finished on cd6ae55 — GitHub Run · Dispatcher Logs.}

[jasonmp85]

I'm checking out the ACR question both otherwise have addressed the feedback

[jasonmp85]

@AAraKKe I think I've addressed your feedback. There might be a CI flake right now, but if my last commit fixes that it's good to merge.

Any chance of a ✅ 😄 ?

[AAraKKe]

Lets go! 🚀🚀🚀

Thanks for taking a look, the failed job right now does seem more an issue with the testing harness than anything else because I saw it passing before. I will take a look tomorrow since I am in rotation this week.

[dd-octo-sts]

Validation Report

All 22 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata, naming, and wheel contents	✅
pr-description	Validate the pull request checklist and visible description length	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run