Skip to content

[DBMON-6454] Add Postgres OTel integration docs#36015

Open
eric-weaver wants to merge 2 commits intomasterfrom
eric.weaver/DBMON-6454
Open

[DBMON-6454] Add Postgres OTel integration docs#36015
eric-weaver wants to merge 2 commits intomasterfrom
eric.weaver/DBMON-6454

Conversation

@eric-weaver
Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

This adds documentation for how to configure Postgresql OTel collector pipeline to export metrics and logs to Datadog in order to correctly semantically map Postgresql OTel metrics with Datadog Agent Postgres integration metrics

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Claude Code was used to generate these docs based off of previous Mysql OTel docs. The OTel configs themselves were manually built and tested during the semantic mapping buildout of supported metrics

Additional notes

Currently there is a TODO for adding image assets. I can help generate data to populate the dashboard but currently the dashboard won't look the prettiest due to a feature flag that is disabling tag mapping.

@eric-weaver eric-weaver requested a review from a team as a code owner April 15, 2026 19:56
@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Apr 15, 2026
@github-actions
Copy link
Copy Markdown
Contributor

@brett0000FF brett0000FF self-assigned this Apr 15, 2026
@brett0000FF brett0000FF added the editorial review Waiting on a more in-depth review label Apr 15, 2026
Copy link
Copy Markdown
Contributor

@brett0000FF brett0000FF left a comment

Choose a reason for hiding this comment

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

Thank you!

Comment on lines +74 to +91
deltatorate:
metrics:
- postgresql.tup_returned
- postgresql.tup_fetched
- postgresql.tup_inserted
- postgresql.tup_updated
- postgresql.tup_deleted
- postgresql.operations
- postgresql.commits
- postgresql.rollbacks
- postgresql.blks_hit
- postgresql.blks_read
- postgresql.temp_files
- postgresql.temp.io
- postgresql.function.calls
- postgresql.index.scans
- postgresql.sequential_scans
- postgresql.blocks_read
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.

Several metrics listed here aren't explicitly enabled in the receivers.postgresql block above: postgresql.operations, postgresql.commits, postgresql.rollbacks, postgresql.index.scans, postgresql.blocks_read. Are they on by default?

- postgresql.commits
- postgresql.rollbacks
- postgresql.blks_hit
- postgresql.blks_read
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.

Are postgresql.blks_read and postgresql.blocks_read the same thing? Just want to make sure we aren't accidentally duplicating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants