[DBM Doc] Document new agent diagnose support for Postgres DBM setup#37568
Draft
pierreln-dd wants to merge 1 commit into
Draft
[DBM Doc] Document new agent diagnose support for Postgres DBM setup#37568pierreln-dd wants to merge 1 commit into
agent diagnose support for Postgres DBM setup#37568pierreln-dd wants to merge 1 commit into
Conversation
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Confidence: DISCUSSION
Source PR: DataDog/integrations-core#23433
What changed:
The Postgres integration now surfaces common DBM setup issues via
datadog-agent diagnose. The new diagnostic framework validates:shared_preload_libraries,track_activity_query_size,track_io_timing,pg_stat_statements.maxpg_monitorrole membershippg_stat_activity,pg_stat_database,pg_stat_statementsdatadogschema,pg_stat_statementsextension, anddatadog.explain_statementfunctionDiagnostics are gated on the DBM subfeatures that require each dependency (e.g., query_metrics checks
shared_preload_libraries, query_samples validates the explain function) and cascade-suppress so a single root cause yields one actionable diagnostic.Why document this:
Users can now run
datadog-agent diagnoseto validate their Postgres DBM setup and get actionable remediation hints for common configuration issues. The self-hosted setup guide should mention this diagnostic capability so users know they can validate their configuration after completing the setup steps.Uncertainty:
The PR does not explicitly state a minimum Agent version for the new diagnostics, though the code changes are in integrations-core only. The placement and wording of the diagnostic callout in the setup flow is open to discussion — should it go near "Verify database permissions" or as a separate troubleshooting step?