Add Snowflake Task Monitoring docs (Preview) - #39206
Open
himakolavennu wants to merge 2 commits into
Open
Conversation
New Jobs Monitoring page documenting Snowflake task run history monitoring (Preview): setup via the Snowflake integration plus the Task History Traces toggle, what Datadog collects, and where task runs appear (catalog Task Runs tab, Lineage side panel, Trace Explorer). Adds the Snowflake card to the Jobs Monitoring index. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Preview links (active after the
|
jhgilbert
added
the
astro-reorg-no-conflicts
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
janine-c
approved these changes
Aug 14, 2026
janine-c
left a comment
janine-c
left a comment
Contributor
There was a problem hiding this comment.
Looks great! Just some minor writing suggestions for you 🙂
|
|
||
| ## Prerequisites | ||
|
|
||
| Connect the [Snowflake integration][2] to Data Observability. The standard setup script already grants everything this feature needs. The grant specific to task monitoring is **`MONITOR EXECUTION ON ACCOUNT`**, which lets Datadog read your Snowflake task run history. |
Contributor
There was a problem hiding this comment.
Suggested change
| Connect the [Snowflake integration][2] to Data Observability. The standard setup script already grants everything this feature needs. The grant specific to task monitoring is **`MONITOR EXECUTION ON ACCOUNT`**, which lets Datadog read your Snowflake task run history. | |
| Connect the [Snowflake integration][2] to Data Observability. The standard setup script already grants everything this feature needs. The permission it grants that is specific to task monitoring is **`MONITOR EXECUTION ON ACCOUNT`**, which lets Datadog read your Snowflake task run history. |
Does this make sense? I thought some more specific wording would make this a bit easier to parse
|
|
||
| ## Enable Task History Traces | ||
|
|
||
| 1. In Data Observability, go to your Snowflake account configuration. |
Contributor
There was a problem hiding this comment.
Maybe add a link to the relevant page in the app here?
| 2. Under **Data Jobs Monitoring**, turn on **Task History Traces**. | ||
| 3. Choose a **Traces collection period** (`5 Min`, `15 Min`, `30 Min`, `Hourly`, or `Daily`). | ||
|
|
||
| Task runs are read from Snowflake's `ACCOUNT_USAGE.TASK_HISTORY` view. When you first enable the feature, Datadog backfills task runs from roughly the last 18 hours. Because that view has a latency of up to 45 minutes, new runs may take that long to appear. |
Contributor
There was a problem hiding this comment.
Suggested change
| Task runs are read from Snowflake's `ACCOUNT_USAGE.TASK_HISTORY` view. When you first enable the feature, Datadog backfills task runs from roughly the last 18 hours. Because that view has a latency of up to 45 minutes, new runs may take that long to appear. | |
| Data Observability reads task runs from Snowflake's `ACCOUNT_USAGE.TASK_HISTORY` view. When you first enable the feature, Datadog backfills task runs from roughly the last 18 hours. Because that view has a latency of up to 45 minutes, new runs may take that long to appear. |
Comment on lines
+40
to
+42
| - **Timing** — scheduled time, completed time, and duration. | ||
| - **Status** — success or failure, with the error code and message on failed runs. | ||
| - **The SQL statement** the task ran. |
Contributor
There was a problem hiding this comment.
Suggested change
| - **Timing** — scheduled time, completed time, and duration. | |
| - **Status** — success or failure, with the error code and message on failed runs. | |
| - **The SQL statement** the task ran. | |
| - **Timing**: Scheduled time, completed time, and duration. | |
| - **Status**: Success or failure, with the error code and message on failed runs. | |
| - The **SQL statement** the task ran. |
| - **Status** — success or failure, with the error code and message on failed runs. | ||
| - **The SQL statement** the task ran. | ||
|
|
||
| Runs are grouped into a **task graph (DAG)** trace, so a root task and its dependent tasks appear together. |
Contributor
There was a problem hiding this comment.
Suggested change
| Runs are grouped into a **task graph (DAG)** trace, so a root task and its dependent tasks appear together. | |
| Data Observability groups runs into a **task graph (DAG)** trace, so a root task and its dependent tasks appear together. |
Comment on lines
+48
to
+55
| - In the Data Observability catalog, the same **Task Runs** view appears in two places: | ||
| - the **Task Runs** tab on the task's entity page, and | ||
| - the **side panel** that opens when you click a task in the Lineage map. | ||
| - In **Trace Explorer**. | ||
|
|
||
| {{< img src="data_jobs/snowflake_task_runs.png" alt="Task Runs on a Snowflake task's entity page in Data Observability" style="width:100%;" >}} | ||
|
|
||
| {{< img src="data_jobs/snowflake_task_runs_lineage.png" alt="Task runs in the side panel of a Snowflake task in the Data Observability Lineage map" style="width:100%;" >}} |
Contributor
There was a problem hiding this comment.
Suggested change
| - In the Data Observability catalog, the same **Task Runs** view appears in two places: | |
| - the **Task Runs** tab on the task's entity page, and | |
| - the **side panel** that opens when you click a task in the Lineage map. | |
| - In **Trace Explorer**. | |
| {{< img src="data_jobs/snowflake_task_runs.png" alt="Task Runs on a Snowflake task's entity page in Data Observability" style="width:100%;" >}} | |
| {{< img src="data_jobs/snowflake_task_runs_lineage.png" alt="Task runs in the side panel of a Snowflake task in the Data Observability Lineage map" style="width:100%;" >}} | |
| You can view task runs in the following places: | |
| - Trace Explorer | |
| - In the Data Observability catalog, in the Task Runs view: | |
| - In the Task Runs tab on the task's entity page | |
| {{< img src="data_jobs/snowflake_task_runs.png" alt="Task runs on a Snowflake task's entity page in Data Observability" style="width:100%;" >}} | |
| - In the side panel that opens when you click a task in the Lineage map | |
| {{< img src="data_jobs/snowflake_task_runs_lineage.png" alt="Task runs in the side panel of a Snowflake task in the Data Observability Lineage map" style="width:100%;" >}} |
Contributor
There was a problem hiding this comment.
I would also recommend adding some links to the relevant pages in the app here, in case users want to try it themselves!
Contributor
|
🔗 Commit SHA: 3d8d0c1 | Docs | Datadog PR Page | Give us feedback! |
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
3 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.
Adds a Jobs Monitoring docs page for Snowflake Task Monitoring (Preview) and links it from the Jobs Monitoring index. Covers setup (Snowflake integration + the Task History Traces toggle), what Datadog collects, where task runs appear (catalog Task Runs tab, Lineage side panel, Trace Explorer), and troubleshooting.
🤖 Generated with Claude Code