Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Seeking Best Practices for End-to-End Data Pipeline Observability

Hi Fabric community,

I've been exploring ways to enhance observability across our data pipelines in Fabric (especially Dataflows Gen2 and Lakehouses). With complex transformations and multiple data sources, tracking data quality issues upstream feels like finding needles in haystacks!

One approach I'm testing involves implementing data contracts between ingestion and transformation layers. This helps catch schema drifts early, but I still struggle with:

  • Column-level lineage visibility

  • Automated anomaly detection

  • Proactive alert thresholds

Has anyone built a comprehensive monitoring solution within Fabric? I'd love to hear how you:

  1. Track pipeline health beyond just activity logs

  2. Monitor sensitive data columns (PII/PHI)

  3. Maintain data quality SLAs

For inspiration, I've been researching solutions like Sifflet's data observability platform. Their approach to metadata-driven monitoring seems promising for Fabric environments. Curious if others have tried similar tools or built custom solutions using:

  • Fabric REST APIs

  • Purview integration

  • Power BI anomaly detection

Would appreciate any war stories or architecture diagrams!

5 Replies