Skip to content

Conversation

@lspanodd
Copy link

We made two changes to the documentation page:
1 - in the Annotations v1 example, we were not using the container name for check, which is incorrect and it will not work. Replaced the postgresql.check_names for postgres.check_names to match the container name.
2. We added a note to guide customers to match their container name in the integration check_names. We are open to suggestion regarding the added note in the documentation.

What does this PR do?

We made two changes to the documentation page:
1 - in the Annotations v1 example, we were not using the container name for check, which is incorrect and it will not work. Replaced the postgresql.check_names for postgres.check_names to match the container name.
2. We added a note to guide customers to match their container name in the integration check_names. We are open to suggestion regarding the added note in the documentation.
Based on customer confusion in case https://datadog.zendesk.com/agent/tickets/2237581

Motivation

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged
We made two changes to the documentation page: 1 - in the Annotations v1 example, we were not using the container name for check, which is incorrect and it will not work. Replaced the postgresql.check_names for postgres.check_names to match the container name. 2. We added a note to guide customers to match their container name in the integration check_names. We are open to suggestion regarding the added note in the documentation.
@github-actions
Copy link

⚠️ Recommendation: Add qa/skip-qa Label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

@traegerdog
Copy link

/merge

@dd-devflow-routing-codex
Copy link

dd-devflow-routing-codex bot commented Oct 10, 2025

View all feedbacks in Devflow UI.

2025-10-10 15:30:06 UTC ℹ️ Start processing command /merge


2025-10-10 15:30:07 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2025-10-10 19:31:15 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

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