[DOCS-12615] Data Observability reorg #33006
Merged
Conversation
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
rtrieu
changed the title
Contributor
rtrieu
added
editorial review
Contributor
Author
|
Created DOCS-12912 for docs review. |
3 tasks
…g/documentation into rtrieu/docs-12615-update-data-obs
warrierr
requested changes
Dec 18, 2025
content/en/data_observability/quality_monitoring/openlineage.md
Outdated
Show resolved
Hide resolved
|
@warrierr and I caught up just on on organization, specifically on whether to have a separate Integrations section. Originally I imagined a separate Integrations section would reduce redundancy across SKUs (especially as we introduce more) and encourage the cross-product suite message. But I'm convinced now that it's secondary to having a simple and clear onboarding experience for specific products. We will probably have to change things in the future, but for now (and we're sorry for the late structure change @Rosa Trieu 😬) how about we go with this change? I'll also leave this as a comment in the PR and change the doc 
|
warrierr
requested changes
Dec 24, 2025
content/en/data_observability/jobs_monitoring/openlineage/_index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Ryan Warrier <ryan.warrier@datadoghq.com>
…g/documentation into rtrieu/docs-12615-update-data-obs
gusvargas
reviewed
Jan 6, 2026
content/en/data_observability/quality_monitoring/data_warehouses/bigquery.md
Outdated
Show resolved
Hide resolved
warrierr
approved these changes
Jan 7, 2026
jhgilbert
approved these changes
Jan 8, 2026
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.
What does this PR do? What is the motivation?
Reorg of existing Data Jobs docs:
See also: #33006 (comment)
Merge instructions
Merge readiness:
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.
Additional notes