Skip to content

data observability: document attribute queries in monitor docs#37357

Open
kevinzenghu wants to merge 6 commits into
masterfrom
kevinzenghu/document-aastra-attribute-queries
Open

data observability: document attribute queries in monitor docs#37357
kevinzenghu wants to merge 6 commits into
masterfrom
kevinzenghu/document-aastra-attribute-queries

Conversation

@kevinzenghu

@kevinzenghu kevinzenghu commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Expands the Data Observability monitor Choose data to monitor docs to cover search capabilities that were already supported in the product but undocumented, and tidies up that section. This PR:

  • Documents tag filters — filter on any tag applied to your assets, using the tag key as the filter key (for example, owner, platform, environment), with the same wildcard and quoting support as name filters.
  • Documents the lineage_score computed attribute — bucketed into the discrete tiers 0.00, 0.10, 0.30, 0.50, 0.70, 0.90, and 1.00 (the only computed attribute available today). You can match one tier or combine tiers with OR (for example, lineage_score:(0.90 OR 1.00) for the top two tiers).
  • Documents the lineage relationship filter — explains Add Lineage Filter, which scopes a selection to assets that are Upstream of or Downstream of another asset (for example, every table upstream of a critical dashboard).
  • Updates the "Choose data to monitor" screenshot to show the lineage relationship filter row, and updates its alt text accordingly.
  • Removes the "Source tab" query-format section, which exposed internal query syntax (search for [ENTITY_TYPE] where ...) that users don't need.

Motivation: this came up in #data-observability-feedback — the syntax for attribute queries and the lineage filter had never been documented.

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

Scope is limited to the existing Choose data to monitor section; no other pages change. lineage_score is the only computed attribute today. It is not continuous — the entity-scorer rounds each asset up to one of seven percentile tiers (0.00, 0.10, 0.30, 0.50, 0.70, 0.90, 1.00), where higher means more downstream dependents.

@kevinzenghu kevinzenghu requested a review from a team as a code owner June 8, 2026 21:29
@github-actions github-actions Bot added the Images Images are added/removed with this PR label Jun 8, 2026
@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@drichards-87 drichards-87 left a comment

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.

Left a couple of suggestions and approved the PR.

Comment thread content/en/monitors/types/data_observability.md Outdated
Comment thread content/en/monitors/types/data_observability.md Outdated
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

Code-Freeze | check-code-freeze-status   View in Datadog   GitHub Actions

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 3189c3a | Docs | Datadog PR Page | Give us feedback!

Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Images Images are added/removed with this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants