From 8609fecef55fa4fbd9af03c0f153839413fea449 Mon Sep 17 00:00:00 2001 From: Kevin Hu Date: Sun, 5 Jul 2026 00:12:55 -0400 Subject: [PATCH] Fix stale/incorrect content across existing DO docs (hygiene sweep) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Found via a proactive quality audit of already-published pages (not a gap-finding pass — these are corrections to live content). All are mechanical/verifiable, not judgment calls: - databricks.md: GRANT USE_CATALOG/USE_SCHEMA is invalid Unity Catalog syntax (underscored) — would fail if copy-pasted. Correct two-word form (GRANT USE CATALOG/SCHEMA) is already used correctly earlier in the same file and consistently in the sibling jobs_monitoring/databricks/_index.md page. Fixed all 5 occurrences. - 5 pages (snowflake/redshift/bigquery/aws_glue x2/glue) still linked to the old app.datadoghq.com/datasets/... URL scheme; updated to the current /data-obs/... scheme already used consistently elsewhere (e.g. dbt.md, data_catalog.md, monitors/types/data_observability.md). - 3 pages (emr.md, airflow.md, databricks/_index.md) used the old "DJM" acronym in body text instead of "Jobs Monitoring", used everywhere else. - data_catalog.md called the monitor feature "Data Quality Monitors"; every other page (monitors/types/data_observability.md and all warehouse/data-lake pages) calls it "Data Observability monitors". - jobs_monitoring/_index.md's two card-grid blocks mixed legacy /data_jobs/* alias paths with the canonical /data_observability/ jobs_monitoring/* form used elsewhere on the same page; standardized to canonical. (Left the AWS Glue card's neighboring position alone — a separate open PR, #37962, adds an Azure Data Factory card to this same file; whichever merges second will need a quick rebase.) - Removed 3 dangling reference-link definitions (dataproc.md, emr.md, looker.md) never cited in body text — harmless but leftover cruft. Not touched (need product input, not a mechanical fix): - A split between app.datadoghq.com/data-jobs/ (used almost everywhere) and .../data-obs/jobs (used in the newest jobs_monitoring page) — lower confidence on which is canonical; flagging for the product team rather than guessing. - An oddly-named image asset (entity_type_selection_and_aastra.png) — cosmetic only, the file exists and renders fine. AI assistance: found and fixed by Claude Code via a systematic audit against sibling-page conventions within the same doc tree — each fix is independently verifiable by diffing against the correct pattern cited above, not a judgment call. --- content/en/data_observability/data_catalog.md | 2 +- .../en/data_observability/jobs_monitoring/_index.md | 10 +++++----- .../en/data_observability/jobs_monitoring/airflow.md | 2 +- .../jobs_monitoring/databricks/_index.md | 2 +- .../data_observability/jobs_monitoring/dataproc.md | 1 - content/en/data_observability/jobs_monitoring/emr.md | 3 +-- .../en/data_observability/jobs_monitoring/glue.md | 2 +- .../business_intelligence/looker.md | 1 - .../quality_monitoring/data_lakes/aws_glue.md | 4 ++-- .../quality_monitoring/data_warehouses/bigquery.md | 2 +- .../quality_monitoring/data_warehouses/databricks.md | 12 ++++++------ .../quality_monitoring/data_warehouses/redshift.md | 2 +- .../quality_monitoring/data_warehouses/snowflake.md | 2 +- 13 files changed, 21 insertions(+), 24 deletions(-) diff --git a/content/en/data_observability/data_catalog.md b/content/en/data_observability/data_catalog.md index 7fb395e8657..32a2771b24b 100644 --- a/content/en/data_observability/data_catalog.md +++ b/content/en/data_observability/data_catalog.md @@ -32,7 +32,7 @@ When you open the catalog at [/data-obs/catalog](https://app.datadoghq.com/data- - **Description**: pulled from the source system if available - **Links to the source system**: direct references back to the origin platform so you can navigate from the catalog to the source in one click - **Tags**: `key:value` metadata pairs pulled from the source system if available -- **Monitor Status**: displays the state of any active [Data Quality Monitors](/data_observability/quality_monitoring/) on the asset +- **Monitor Status**: displays the state of any active [Data Observability monitors](/data_observability/quality_monitoring/) on the asset - **Lineage**: upstream and downstream dependencies, where supported by the integration. To explore lineage across assets, see [Lineage][1]. Use the left sidebar to filter assets by type: {{< ui >}}All assets{{< /ui >}}, {{< ui >}}Databases{{< /ui >}}, {{< ui >}}Schemas{{< /ui >}}, or {{< ui >}}Tables{{< /ui >}}. Connected integrations (such as Snowflake, dbt, and BigQuery) are also listed individually in the sidebar. diff --git a/content/en/data_observability/jobs_monitoring/_index.md b/content/en/data_observability/jobs_monitoring/_index.md index 08c0454054c..89bcdabc973 100644 --- a/content/en/data_observability/jobs_monitoring/_index.md +++ b/content/en/data_observability/jobs_monitoring/_index.md @@ -34,8 +34,8 @@ Data Observability: Jobs Monitoring provides visibility into the performance, re Data Observability: Jobs Monitoring supports multiple job technologies. To get started, select your technology and follow the installation instructions: {{< card-grid >}} - {{< image-card href="/data_jobs/databricks/" src="integrations_logos/databricks.png" alt="Databricks" >}} - {{< image-card href="/data_jobs/airflow/" src="integrations_logos/airflow.png" alt="Airflow" >}} + {{< image-card href="/data_observability/jobs_monitoring/databricks/" src="integrations_logos/databricks.png" alt="Databricks" >}} + {{< image-card href="/data_observability/jobs_monitoring/airflow/" src="integrations_logos/airflow.png" alt="Airflow" >}} {{< image-card href="/data_observability/jobs_monitoring/dbt" src="integrations_logos/dbt-cloud_large.svg" alt="dbt cloud" >}} {{< image-card href="/data_observability/jobs_monitoring/glue/" src="integrations_logos/amazon_glue.png" alt="AWS Glue" >}} {{< /card-grid >}} @@ -45,9 +45,9 @@ Data Observability: Jobs Monitoring supports multiple job technologies. To get s Data Observability: Jobs Monitoring also supports Apache Spark jobs on the following platforms: {{< card-grid >}} - {{< image-card href="/data_jobs/kubernetes/" src="integrations_logos/kubernetes.png" alt="Kubernetes" >}} - {{< image-card href="/data_jobs/emr" src="integrations_logos/amazon_emr.png" alt="Amazon EMR" >}} - {{< image-card href="/data_jobs/dataproc/" src="integrations_logos/google_cloud_dataproc.png" alt="GCP Dataproc" >}} + {{< image-card href="/data_observability/jobs_monitoring/kubernetes/" src="integrations_logos/kubernetes.png" alt="Kubernetes" >}} + {{< image-card href="/data_observability/jobs_monitoring/emr" src="integrations_logos/amazon_emr.png" alt="Amazon EMR" >}} + {{< image-card href="/data_observability/jobs_monitoring/dataproc/" src="integrations_logos/google_cloud_dataproc.png" alt="GCP Dataproc" >}} {{< /card-grid >}}
diff --git a/content/en/data_observability/jobs_monitoring/airflow.md b/content/en/data_observability/jobs_monitoring/airflow.md index cda1520d3e2..30c1545adff 100644 --- a/content/en/data_observability/jobs_monitoring/airflow.md +++ b/content/en/data_observability/jobs_monitoring/airflow.md @@ -205,7 +205,7 @@ To get started, follow the instructions below. 1. Deploy your updated `requirements.txt` and [Amazon MWAA startup script][3] to your Amazon S3 folder configured for your Amazon MWAA Environment. -1. Optionally, set up Log Collection for correlating task logs to DAG run executions in DJM: +1. Optionally, set up Log Collection for correlating task logs to DAG run executions in Jobs Monitoring: 1. Configure Amazon MWAA to [send logs to CloudWatch][9]. 2. [Send the logs to Datadog][10]. diff --git a/content/en/data_observability/jobs_monitoring/databricks/_index.md b/content/en/data_observability/jobs_monitoring/databricks/_index.md index 63c3e7745ae..2f84c2b6918 100644 --- a/content/en/data_observability/jobs_monitoring/databricks/_index.md +++ b/content/en/data_observability/jobs_monitoring/databricks/_index.md @@ -417,7 +417,7 @@ If some jobs are not visible, navigate to the [Configuration][9] page to underst ## Troubleshooting -If you don't see any data in DJM after installing the product, follow these steps. +If you don't see any data in Jobs Monitoring after installing the product, follow these steps. ### Init script not running or failing diff --git a/content/en/data_observability/jobs_monitoring/dataproc.md b/content/en/data_observability/jobs_monitoring/dataproc.md index d74d3255640..d4f3b9b8a42 100644 --- a/content/en/data_observability/jobs_monitoring/dataproc.md +++ b/content/en/data_observability/jobs_monitoring/dataproc.md @@ -115,7 +115,6 @@ In Datadog, view the [Data Observability: Jobs Monitoring][8] page to see a list [3]: https://cloud.google.com/secret-manager/docs/secret-rotation?_gl=1*144zyx0*_ga*MTk0ODY1OTU1OS4xNzI0NzA5NDM4*_ga_WH2QY8WWF5*MTcyNTk1MDU4Mi4yMy4xLjE3MjU5Nzk3NzUuNDEuMC4w [4]: https://console.cloud.google.com/dataproc/ [5]: https://console.cloud.google.com/iam-admin/iam -[7]: /getting_started/site/ [8]: https://app.datadoghq.com/data-jobs/ [9]: /data_jobs [10]: https://cloud.google.com/dataproc/docs/concepts/versioning/overview diff --git a/content/en/data_observability/jobs_monitoring/emr.md b/content/en/data_observability/jobs_monitoring/emr.md index 4f16a594703..f7ac6780c8e 100644 --- a/content/en/data_observability/jobs_monitoring/emr.md +++ b/content/en/data_observability/jobs_monitoring/emr.md @@ -11,7 +11,7 @@ further_reading: [Data Observability: Jobs Monitoring][9] gives visibility into the performance and reliability of Apache Spark applications on Amazon EMR. -If you are using [EMR on EKS][13], follow these [instructions for setting up DJM on Kubernetes][14]. +If you are using [EMR on EKS][13], follow these [instructions for setting up Jobs Monitoring on Kubernetes][14]. ## Requirements @@ -179,7 +179,6 @@ In Datadog, view the [Data Observability: Jobs Monitoring][8] page to see a list [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotating-secrets.html [4]: https://console.aws.amazon.com/emr [5]: https://console.aws.amazon.com/iam/ -[7]: /getting_started/site/ [8]: https://app.datadoghq.com/data-jobs/ [9]: /data_jobs [10]: https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-601-release.html diff --git a/content/en/data_observability/jobs_monitoring/glue.md b/content/en/data_observability/jobs_monitoring/glue.md index f3e21e138ae..e694ffaaddf 100644 --- a/content/en/data_observability/jobs_monitoring/glue.md +++ b/content/en/data_observability/jobs_monitoring/glue.md @@ -148,7 +148,7 @@ In Datadog, view the [Data Observability: Jobs Monitoring][6] page to see a list {{< partial name="whats-next/whats-next.html" >}} [1]: /integrations/amazon-web-services/ -[2]: https://app.datadoghq.com/datasets/settings/integrations +[2]: https://app.datadoghq.com/data-obs/settings/integrations [4]: /integrations/amazon-glue/ [5]: /logs/guide/send-aws-services-logs-with-the-datadog-lambda-function/?tab=awsconsole [6]: https://app.datadoghq.com/data-jobs/ diff --git a/content/en/data_observability/quality_monitoring/business_intelligence/looker.md b/content/en/data_observability/quality_monitoring/business_intelligence/looker.md index 7e6ff0d94b8..c8b539d42e9 100644 --- a/content/en/data_observability/quality_monitoring/business_intelligence/looker.md +++ b/content/en/data_observability/quality_monitoring/business_intelligence/looker.md @@ -55,7 +55,6 @@ After syncing, you can explore your Looker assets and their upstream dependencie {{< partial name="whats-next/whats-next.html" >}} -[1]: https://cloud.google.com/looker/docs/api-auth [2]: https://app.datadoghq.com/integrations/looker [3]: https://app.datadoghq.com/data-obs/catalog [4]: https://app.datadoghq.com/integrations/github diff --git a/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md b/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md index c0a5dfa37fe..956fabb494f 100644 --- a/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md +++ b/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md @@ -218,8 +218,8 @@ After the sync completes, your tables appear in the [Data Catalog][3]. You can a {{< partial name="whats-next/whats-next.html" >}} [1]: /integrations/amazon-web-services/ -[2]: https://app.datadoghq.com/datasets/settings/integrations -[3]: https://app.datadoghq.com/datasets/catalog?integration=awsglue%2Fdatabase_account +[2]: https://app.datadoghq.com/data-obs/settings/integrations +[3]: https://app.datadoghq.com/data-obs/catalog?integration=awsglue%2Fdatabase_account [4]: https://docs.aws.amazon.com/glue/latest/dg/security_iam_id-based-policy-examples.html [5]: https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-format-iceberg.html [6]: /integrations/amazon-glue/ diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/bigquery.md b/content/en/data_observability/quality_monitoring/data_warehouses/bigquery.md index fbaad972bc9..beceba60dd6 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/bigquery.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/bigquery.md @@ -120,7 +120,7 @@ After the initial sync completes, create a [Data Observability monitor][14] to s [5]: https://cloud.google.com/iam/docs/roles-permissions/monitoring#monitoring.viewer [6]: https://cloud.google.com/iam/docs/roles-permissions/cloudasset#cloudasset.viewer [7]: https://cloud.google.com/iam/docs/roles-permissions/browser#browser -[8]: https://app.datadoghq.com/datasets/settings/integrations +[8]: https://app.datadoghq.com/data-obs/settings/integrations [9]: https://cloud.google.com/monitoring/api/enable-api [10]: https://cloud.google.com/asset-inventory/docs/reference/rest [11]: https://cloud.google.com/compute/docs/reference/rest/v1 diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/databricks.md b/content/en/data_observability/quality_monitoring/data_warehouses/databricks.md index 78123db1f62..e92086f17d9 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/databricks.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/databricks.md @@ -53,8 +53,8 @@ Use the full catalog access option for simpler setup. It automatically includes ```sql -GRANT USE_CATALOG ON CATALOG TO ``; -GRANT USE_SCHEMA ON CATALOG TO ``; +GRANT USE CATALOG ON CATALOG TO ``; +GRANT USE SCHEMA ON CATALOG TO ``; GRANT SELECT ON CATALOG TO ``; ``` @@ -64,8 +64,8 @@ GRANT SELECT ON CATALOG TO ``; Use the specific tables option for least-privilege access or if you only need to monitor a subset of your data. You must update permissions when adding new tables. ```sql -GRANT USE_CATALOG ON CATALOG TO ``; -GRANT USE_SCHEMA ON SCHEMA . TO ``; +GRANT USE CATALOG ON CATALOG TO ``; +GRANT USE SCHEMA ON SCHEMA . TO ``; GRANT SELECT ON TABLE .. TO ``; ``` @@ -74,8 +74,8 @@ GRANT SELECT ON TABLE .. TO `}} -[1]: https://app.datadoghq.com/datasets/settings/integrations +[1]: https://app.datadoghq.com/data-obs/settings/integrations [2]: /monitors/types/data_observability/ [3]: /integrations/amazon-web-services/ \ No newline at end of file diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md index facbf4c467a..0fd3e879f1e 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/snowflake.md @@ -249,7 +249,7 @@ If Datadog is unable to see expected databases, schemas, or tables in your Snowf [1]: https://docs.snowflake.com/en/user-guide/key-pair-auth#generate-the-private-key [2]: https://docs.snowflake.com/en/developer-guide/logging-tracing/event-table-setting-up -[3]: https://app.datadoghq.com/datasets/settings/integrations +[3]: https://app.datadoghq.com/data-obs/settings/integrations [4]: https://app.datadoghq.com/apm/traces [5]: /monitors/types/data_observability/ [6]: https://docs.snowflake.com/en/user-guide/object-tagging