model query and auto-exposures beta #5896
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
…getdbt.com into add-exposures-model-query
reubenmc
reviewed
Aug 9, 2024
website/docs/docs/cloud-integrations/configure-auto-exposures.md
Outdated
Show resolved
Hide resolved
reubenmc
reviewed
Aug 9, 2024
| 1. You have a dbt Cloud account on the [Enterprise plan](https://www.getdbt.com/pricing/). | ||
| 2. You have set up a [production](/docs/deploy/deploy-environments#set-as-production-environment) deployment environment for each project you want to explore, with at least one successful job run. | ||
| 3. You have [admin permissions](/docs/cloud/manage-access/enterprise-permissions) in dbt Cloud to edit project settings or production environment settings | ||
| 4. Use Tableau as your BI tool and can enable metadata permissions or work with an admin to do so. Compatible with Tableau Cloud or Tableau Server with the Metadata API enabled. |
There was a problem hiding this comment.
We may need an update for Tableau server based on what we find out from customers about Whitelisting the IP address (just an additional callout of the extra step for Server). I'll know more on Monday. Is it fine to make the update post it going live if needed?
There was a problem hiding this comment.
Yes, we can totally update after it goes live! I won't resolve this comment until we hear back though.
runleonarun
reviewed
Aug 10, 2024
website/docs/docs/cloud-integrations/configure-auto-exposures.md
Outdated
Show resolved
Hide resolved
mirnawong1
commented
Aug 12, 2024
website/docs/docs/cloud-integrations/configure-auto-exposures.md
Outdated
Show resolved
Hide resolved
mirnawong1
commented
Aug 12, 2024
mirnawong1
commented
Aug 12, 2024
mirnawong1
commented
Aug 12, 2024
| - View the query count for a model based on the data warehouse's query logs. | ||
| - Provides data teams insight, so they can focus their time and infrastructure spend on the worthwhile used data products. | ||
| - Enable analysts to find the most popular models used by other people. | ||
|
|
There was a problem hiding this comment.
Suggested change
| :::info Available in beta | |
| Model query history is currently available in beta to a limited group of users and is gradually being rolled out. If you're interested in gaining access or learning more, stay tuned for updates! | |
| ::: |
|
ok so it looks like we’re waiting on two things:
i do think there’s a benefit in having a callout to all the docs saying this is available in beta for limited users and then rolling out. that way we make it clear for users that it’ll get rolled out soon and will hopefully address users questions without them needing to reach out to support. i’ve added it as a sugg and if eeryone is ok, can someone from the docs team commit them? :ty: |
Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
|
Approved |
|
Check your created Crawler Check your created index on your Algolia Application |
7 tasks
matthewshaver
pushed a commit
that referenced
this pull request
Aug 13, 2024
## What are you changing in this pull request and why? Adding one more beta we missed in [Mirna's PR](#5896) ## Checklist <!-- Uncomment when publishing docs for a prerelease version of dbt: - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages) - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade) --> - [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content). - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." Adding or removing pages (delete if not applicable): - [ ] Add/remove page in `website/sidebars.js` - [ ] Provide a unique filename for new pages - [ ] Add an entry for deleted pages in `website/vercel.json` - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages
JKarlavige
pushed a commit
that referenced
this pull request
Aug 13, 2024
this pr adds model query history and auto exposures (beta) to the doca site for the broader beta cycle. [docs project](https://www.notion.so/dbtlabs/BI-auto-exposures-model-query-history-embeddable-tile-00b9411c36e748f09d16ede9136fc7ec) outstanding questions: - is data health tile enterprise only? or team + enterprise? - is the beta call out (for feedback to to take part bit) correct? [ ] PM review required [x ] Docs review optional since beta --------- Co-authored-by: nataliefiann <120089939+nataliefiann@users.noreply.github.com> Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
JKarlavige
pushed a commit
that referenced
this pull request
Aug 13, 2024
## What are you changing in this pull request and why? Adding one more beta we missed in [Mirna's PR](#5896) ## Checklist <!-- Uncomment when publishing docs for a prerelease version of dbt: - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages) - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade) --> - [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [ ] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content). - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch." Adding or removing pages (delete if not applicable): - [ ] Add/remove page in `website/sidebars.js` - [ ] Provide a unique filename for new pages - [ ] Add an entry for deleted pages in `website/vercel.json` - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages
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.
this pr adds model query history and auto exposures (beta) to the doca site for the broader beta cycle.
docs project
outstanding questions:
[ ] PM review required
[x ] Docs review optional since beta