Add Data Observability network requirements (intake domains and IP ranges)#38073
Draft
kevinzenghu wants to merge 1 commit into
Draft
Add Data Observability network requirements (intake domains and IP ranges)#38073kevinzenghu wants to merge 1 commit into
kevinzenghu wants to merge 1 commit into
Conversation
Documents the connectivity model for Data Observability: the data-obs-intake push endpoint for OpenLineage lineage and Jobs Monitoring, and the webhooks/API IP ranges used by agentless Quality Monitoring and the Databricks API path. Adds a Data Observability entry to the Agent network destinations page and a further reading link from the Data Observability overview. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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?
Data Observability intake endpoints and IP ranges are not documented on the Agent Network Traffic page or elsewhere, which comes up repeatedly in customer security reviews and RFIs. This PR documents the connectivity model.
Changes:
content/en/data_observability/network.mddescribing the three connectivity paths:webhooksIP ranges on the warehouse.data-obs-intake.<site>/api/v1/lineage.webhooksIP ranges; serverless Spark is API-only.Merge instructions
Merge readiness:
Draft pending SME review. Please confirm the open items below before merging.
Additional notes
Open questions for the Data Observability / intake owners to confirm:
data-obs-intake.<site>has a published static IP set (anip-rangesentry), or whether domain-based allowlisting is the only supported option for the push path.webhooksvsapiIP-range requirement for the Databricks API path:webhooksis required; theapiranges appear needed only when adding workspaces through the Datadog UI. This PR reflects that, but it should be confirmed.data-obs-intakeendpoint.No Jira ticket attached yet; add the
[DOCS-XXXXX]key to the title before merge.