data observability: document attribute queries in monitor docs#37357
Open
kevinzenghu wants to merge 6 commits into
Open
data observability: document attribute queries in monitor docs#37357kevinzenghu wants to merge 6 commits into
kevinzenghu wants to merge 6 commits into
Conversation
Contributor
Preview links (active after the
|
drichards-87
approved these changes
Jun 8, 2026
drichards-87
left a comment
Contributor
There was a problem hiding this comment.
Left a couple of suggestions and approved the PR.
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
Contributor
|
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
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
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.
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:
owner,platform,environment), with the same wildcard and quoting support as name filters.lineage_scorecomputed attribute — bucketed into the discrete tiers0.00,0.10,0.30,0.50,0.70,0.90, and1.00(the only computed attribute available today). You can match one tier or combine tiers withOR(for example,lineage_score:(0.90 OR 1.00)for the top two tiers).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:
Additional notes
Scope is limited to the existing Choose data to monitor section; no other pages change.
lineage_scoreis 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.