[WIP] Add Azure Data Factory Jobs Monitoring documentation#37962
Draft
kevinzenghu wants to merge 2 commits into
Draft
[WIP] Add Azure Data Factory Jobs Monitoring documentation#37962kevinzenghu wants to merge 2 commits into
kevinzenghu wants to merge 2 commits into
Conversation
Corrects an earlier finding: a prior code-only pass found an internal knowledge-base comment stating "not GA, do not promise to customers" and concluded this shouldn't be publicly documented. Kevin confirmed directly that ADF is in private preview with access available on request, backed by a setup guide — the internal knowledge-base file was stale relative to the feature's actual current phase (a real instance of the "most recent live signal wins" precedence rule; the stale knowledge-base file should be updated separately). Content is adapted from that setup guide into house style (tabs for the two role-assignment options, standard Datadog UI/CLI conventions), following the existing AWS Glue Jobs Monitoring page's structure. No internal-only URLs or infrastructure in this one — Azure Portal, az CLI, and Datadog's own already-public UI paths only. AI assistance: adapted by Claude Code from a human-authored internal setup doc (linked in the PR), restructured into Datadog documentation style; Azure permission/role details are not independently verified against code, only against the source doc.
Contributor
Preview links (active after the
|
Same class of bug just found and fixed for Airbyte: this PR's new page and card-grid link were correctly added, but the separate sidebar-nav config (config/_default/menus/main.en.yaml) was not — this branch predates discovering that file exists. Added the missing entry right after AWS Glue, matching the card-grid ordering already in this PR.
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.
Summary
Source
Adapted from an internal setup guide: https://docs.google.com/document/d/1LQdwYkuyfid-Xhs59fuh8lylXHpswAGSMHgpE46wvDo/edit — no internal-only infrastructure in this one (standard Azure Portal / az CLI / Datadog UI paths only), unlike the parallel Postgres doc.
Open items
domains/data_observability/apps/apis/do_product_agent/internal/knowledge/engineering/integrations.md) still says "not GA" and should be corrected so it doesn't mislead the next person/agent who checks it.Status
Work in progress — not ready for review yet. Draft, no reviewers requested.
AI assistance
Content adapted by Claude Code from a human-authored internal setup doc (linked above) into Datadog documentation style — flagging per the AI-assistance disclosure in CONTRIBUTING.md.