


Discover more integrations
No items found.
Get in touch CTA Section
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Frequently asked questions
Does Sifflet store any of my company’s data?
No, Sifflet does not store your data. We designed our platform to discard any data previews immediately after display, and we only retain metadata like table and column names. This approach supports GDPR compliance and strengthens your overall data governance strategy.
What is the Model Context Protocol (MCP), and why is it important for data observability?
The Model Context Protocol (MCP) is a new interface standard developed by Anthropic that allows large language models (LLMs) to interact with tools, retain memory, and access external context. At Sifflet, we're excited about MCP because it enables more intelligent agents that can help with data observability by diagnosing issues, triggering remediation tools, and maintaining context across long-running investigations.
What kind of monitoring should I set up after migrating to the cloud?
After migration, continuous data quality monitoring is a must. Set up real-time alerts for data freshness checks, schema changes, and ingestion latency. These observability tools help you catch issues early and keep your data pipelines running smoothly.
What are some best practices for ensuring SLA compliance in data pipelines?
To stay on top of SLA compliance, it's important to define clear service level objectives (SLOs), monitor data freshness checks, and set up real-time alerts for anomalies. Tools that support automated incident response and pipeline health dashboards can help you detect and resolve issues quickly. At Sifflet, we recommend integrating observability tools that align both technical and business metrics to maintain trust in your data.
How does Sifflet help reduce alert fatigue in data teams?
Sifflet's observability tools are built with smart alerting in mind. By combining dynamic thresholding, impact-aware triage, and anomaly scoring, we help teams focus on what really matters. This reduces noise and ensures that alerts are actionable, leading to faster resolution and better SLA compliance.
Why is declarative lineage important for data observability?
Declarative lineage is a game changer because it provides a clear, structured view of how data flows through your systems. This visibility is key for effective data pipeline monitoring, root cause analysis, and data governance. With Sifflet’s approach, you can track upstream and downstream dependencies and ensure your data is reliable and well-managed.
How does Sifflet help identify performance bottlenecks in dbt models?
Sifflet's dbt runs tab offers deep insights into model execution, cost, and runtime, making it easy to spot inefficiencies. You can also use historical performance data to set up custom dashboards and proactive monitors. This helps with capacity planning and ensures your data pipelines stay optimized and cost-effective.
What new dbt metadata can I now see in Sifflet?
You’ll now find key dbt metadata like the last execution timestamp and status directly within the dataset catalog and asset pages. This makes real-time metrics and pipeline health monitoring more accessible and actionable across your observability platform.






-p-500.png)
