[CONTP-1760] Document configuring Autodiscovery with the DatadogInstrumentation CRD - #37532
Merged
Mathew-Estafanous merged 20 commits intoAug 7, 2026
Conversation
Contributor
Mathew-Estafanous
changed the title
Mathew-Estafanous
marked this pull request as ready for review
June 17, 2026 15:43
Contributor
|
Thanks for the PR! I've created DOCS-14878 for documentation team review |
cswatt
requested changes
Jun 24, 2026
cswatt
approved these changes
Jun 25, 2026
This comment has been minimized.
This comment has been minimized.
Mathew-Estafanous
force-pushed
the
mathew.estafanous/docs-datadoginstrumentation-crd-autodiscovery
branch
2 times, most recently
from
August 3, 2026 19:24
4820848 to
07cd13f
Compare
Mathew-Estafanous
force-pushed
the
mathew.estafanous/docs-datadoginstrumentation-crd-autodiscovery
branch
from
August 5, 2026 17:51
3c7d488 to
85b7b33
Compare
Contributor
gabedos
approved these changes
Aug 5, 2026
gabedos
left a comment
gabedos
left a comment
Contributor
There was a problem hiding this comment.
approved with small comments
Mathew-Estafanous
force-pushed
the
mathew.estafanous/docs-datadoginstrumentation-crd-autodiscovery
branch
from
August 6, 2026 13:05
38899ab to
40bbbd2
Compare
jhgilbert
added
the
astro-reorg-no-conflicts
Mathew-Estafanous
force-pushed
the
mathew.estafanous/docs-datadoginstrumentation-crd-autodiscovery
branch
from
August 6, 2026 19:05
40bbbd2 to
0315ee5
Compare
Add a new guide describing how to configure Autodiscovery checks for Kubernetes workloads through the DatadogInstrumentation custom resource (beta) instead of pod annotations, and cross-reference it from the existing Autodiscovery pages. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Use present tense for precedence and validation behavior - Add "Verify scheduled checks" section with an agent configcheck example - Remove the redundant status section - Point Prometheus Operator users to the DDI CRD as the PodMonitor/ServiceMonitor equivalent - Fix a trailing space in the Prometheus DDI example Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Show the OpenMetrics check as a DatadogInstrumentation resource alongside the annotation examples, note the 7.81+ requirement, and call out removing the annotation from the example manifest so the resource takes effect. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Mathew-Estafanous
force-pushed
the
mathew.estafanous/docs-datadoginstrumentation-crd-autodiscovery
branch
from
August 7, 2026 00:08
0315ee5 to
4eb4555
Compare
Mathew-Estafanous
deleted the
mathew.estafanous/docs-datadoginstrumentation-crd-autodiscovery
branch
August 7, 2026 00:52
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
5 participants
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.
What does this PR do? What is the motivation?
Datadog now lets users configure Autodiscovery for Kubernetes workloads through the
DatadogInstrumentationcustom resource, instead of pod annotations. This PR documents that capability.Pod annotations require editing workload specs, are error-prone (raw JSON), and can't be centrally managed or rolled back without touching the workload. The custom resource gives users a structured, validated, version-controllable way to configure checks per workload — and it's a familiar model for teams coming from the Prometheus Operator's
PodMonitor/ServiceMonitor.Annotations remain the default path for most users. These docs surface the CRD as an alternative wherever annotation-based configuration already appears, so users discover it when it's relevant without disrupting the existing flow.
What's included:
Epic context: CONTP-1453
Platform RFC: https://datadoghq.atlassian.net/wiki/x/J8FIhwE
Autodiscovery RFC: https://datadoghq.atlassian.net/wiki/x/mgAsiAE
Merge instructions
Merge readiness: