Skip to content

[monitors/do] update docs to include hierarchy query #38247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
benbriggs wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[monitors/do] update docs to include hierarchy query #38247

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion content/en/monitors/types/data_observability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,11 @@ Combine any of these filters with `AND` or `OR`, use parentheses to group condit

**Filter by lineage relationship:**

To scope your selection to assets that are connected to another asset in your lineage graph, click {{< ui >}}Add Lineage Filter{{< /ui >}}. Choose {{< ui >}}Upstream of{{< /ui >}} or {{< ui >}}Downstream of{{< /ui >}}, then select a specific asset or use the same `key:value` filters to match a set of assets. For example, monitor every table that is upstream of a critical dashboard, or every column downstream of a specific source table.
To scope your selection to assets that are connected to another asset in your lineage graph, click {{< ui >}}Add Relation Filter{{< /ui >}}. Choose {{< ui >}}Upstream of{{< /ui >}} or {{< ui >}}Downstream of{{< /ui >}}, then select a specific asset or use the same `key:value` filters to match a set of assets. For example, monitor every table that is upstream of a critical dashboard, or every column downstream of a specific source table.

**Filter by hierarchy relationship:**

To scope your selection to assets that are a parent or child of another asset in your lineage graph, click {{< ui >}}Add Relation Filter{{< /ui >}}. Choose {{< ui >}}Parent of{{< /ui >}} or {{< ui >}}Child of{{< /ui >}}, then select a specific asset or use the same `key:value` filters to match a set of assets. For example, monitor every table that has a `revenue` column, or every table that is within a critical schema.

@evazorro evazorro Jul 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For example, monitor every table that has a revenue column, or every table that is within a critical schema.

Is this example related to parent/child assets? Or just general examples of what you might filter on?

@benbriggs benbriggs Jul 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup, it's related! in the first case, you'd be filtering tables based on their column children, and in the second you'd be filtering tables based on their parent schemas


A single monitor can track up to 5,000 tables, views, or columns. This limit cannot be increased. If your query matches more, split them across multiple monitors.

Expand Down
Loading