I wish spectacles had a change validator

[jschintz]

Random idea, End users want to know their impact from upstream analytics engineering changes.

As a user they should be able to:

• Describe all fields(dims and measures) that were changed in a PR.
• For all tiles with no field change, find changes to #s in dashboards. Identify where the PR has potential to impact numbers for business users.
• Option to iterate over parameters and filters.
• Make a change log output that details the above

Feature is specifically meant to capture downstream changes from a pdt or a dbt deployment

Use a package like datafold to improve query times.

[joshtemple]

Hey @jschintz, our SaaS product has a dbt integration [2min video] that does some of what you suggest. It works with dbt Cloud and open source dbt setups, as well as other data modeling tools like Dataform.

It won't tell you about changes in numbers in dashboards, that would be really cool. But it will warn you about potential SQL errors caused by analytics engineering changes.

I think the idea of dashboard diffing continues to be very interesting to us. It would be useful to define some key reports in your org and get a sense of how changes (whether to Looker or to the warehouse, like dbt) impact those reports.