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 our service customers
Frequently asked questions
How does data observability improve incident response and SLA compliance?
With data observability, teams get real-time metrics and deep context around data issues. This means faster incident response and better SLA compliance. Sifflet’s observability platform helps you pinpoint root causes quickly, reducing downtime and giving stakeholders confidence in the reliability of your data.
How does Sifflet ensure a user-friendly experience for data teams?
We prioritize user research and apply UX principles like Jacob’s Law to design familiar and intuitive workflows. This helps reduce friction for users working with tools like our Sifflet Insights plugin, which brings real-time metrics and data quality monitoring directly into BI dashboards like Looker and Tableau.
What does 'observability culture' mean at Adaptavist?
For Adaptavist, observability culture means going beyond tools. It's about clear ownership of alerts, integrating data quality monitoring into sprints, and giving stakeholders ways to provide feedback directly in dashboards. They even track observability metrics to continuously improve their own observability practices.
Why is data lineage a pillar of Full Data Stack Observability?
At Sifflet, we consider data lineage a core part of Full Data Stack Observability because it connects data quality monitoring with data discovery. By mapping data dependencies, teams can detect anomalies faster, perform accurate root cause analysis, and maintain trust in their data pipelines.
Can non-technical users benefit from Sifflet’s Data Catalog?
Yes, definitely! Sifflet is designed to be user-friendly for both technical and business users. With features like AI-driven description recommendations and easy-to-navigate asset pages, even non-technical users can confidently explore and understand the data they need.
What is data distribution deviation and why should I care about it?
Data distribution deviation happens when the distribution of your data changes over time, either gradually or suddenly. This can lead to serious issues like data drift, broken queries, and misleading business metrics. With Sifflet's data observability platform, you can automatically monitor for these deviations and catch problems before they impact your decisions.
What makes Carrefour’s approach to observability scalable and effective?
Carrefour’s approach combines no-code self-service tools with as-code automation, making it easy for both technical and non-technical users to adopt. This balance, along with incremental implementation and cultural emphasis on data quality, supports scalable observability across the organization.
How does schema evolution impact batch and streaming data observability?
Schema evolution can introduce unexpected fields or data type changes that disrupt both batch and streaming data workflows. With proper data pipeline monitoring and observability tools, you can track these changes in real time and ensure your systems adapt without losing data quality or breaking downstream processes.