Google BigQuery
Integrate Sifflet with BigQuery to monitor all table types, access field-level lineage, enrich metadata, and gain actionable insights for an optimized data observability strategy.




Metadata-based monitors and optimized queries
Sifflet leverages BigQuery's metadata APIs and relies on optimized queries, ensuring minimal costs and efficient monitor runs.


Usage and BigQuery metadata
Get detailed statistics about the usage of your BigQuery assets, in addition to various metadata (like tags, descriptions, and table sizes) retrieved directly from BigQuery.
Field-level lineage
Have a complete understanding of how data flows through your platform via field-level end-to-end lineage for BigQuery.


External table support
Sifflet can monitor external BigQuery tables to ensure the quality of data in other systems like Google Cloud BigTable and Google Cloud Storage

Still have a question in mind ?
Contact Us
Frequently asked questions
How does passive metadata support data lineage tracking in Sifflet?
In Sifflet, passive metadata captures the relationships between datasets, allowing users to trace how data flows from source to dashboard. This lineage tracking helps teams understand dependencies, assess the impact of changes, and maintain data reliability across the stack.
How can data teams prioritize what to monitor in complex environments?
Not all data is created equal, so it's important to focus data quality monitoring efforts on the assets that drive business outcomes. That means identifying key dashboards, critical metrics, and high-impact models, then using tools like pipeline health dashboards and SLA monitoring to keep them reliable and fresh.
How does integrating data observability improve SLA compliance?
Integrating data observability helps you stay on top of data issues before they impact your users. With real-time metrics, pipeline error alerting, and dynamic thresholding, you can catch problems early and ensure your data meets SLA requirements. This proactive monitoring helps teams maintain trust and deliver consistent, high-quality data services.
Can a metadata catalog help with SLA compliance?
Absolutely! By continuously tracking data freshness, lineage, and quality scores, a metadata catalog helps ensure that critical datasets meet SLA compliance standards. It also provides visibility into who owns the data and when it was last updated, which is essential for meeting service level objectives and supporting audit logging.
What’s next for Sifflet’s metrics observability capabilities?
We’re expanding support to more BI and transformation tools beyond Looker, and enhancing our ML-based monitoring to group business metrics by domain. This will improve consistency and make it even easier for users to explore metrics across the semantic layer.
Is it hard to set up the Sifflet and ServiceNow integration?
Not at all! It only takes a few minutes to get started. Just follow our step-by-step integration guide, and you’ll be ready to connect your data observability alerts directly to ServiceNow in no time.
How do declared assets improve data quality monitoring?
Declared assets appear in your Data Catalog just like built-in assets, with full metadata and business context. This improves data quality monitoring by making it easier to track data lineage, perform data freshness checks, and ensure SLA compliance across your entire pipeline.
How does the improved test connection process for Snowflake observability help teams?
The revamped 'Test Connection' process for Snowflake observability now provides detailed feedback on missing permissions or policy issues. This makes setup and troubleshooting much easier, especially during onboarding. It helps ensure smooth data pipeline monitoring and reduces the risk of refresh failures down the line.




















-p-500.png)
