transformation
Power BI Monitoring for dbt Core
dbt Core users run transformations in their own CI/CD pipelines (GitHub Actions, GitLab CI, Azure DevOps). There is no hosted dashboard for job runs — results live in logs and artifacts. MetricSign integrates via webhook: your CI/CD pipeline calls MetricSign after each dbt run, uploading the manifest and run results, which are then correlated with Power BI refresh events.
What you can monitor
- Receive alerts when a self-hosted dbt Core run fails, including which models failed
- Automatically map dbt model outputs to Power BI datasets using manifest lineage
- Detect when a dbt schema change breaks a Power BI measure or column
- See dbt run results next to Power BI refresh history without needing dbt Cloud
How MetricSign helps
01Webhook receiver for CI/CD-triggered dbt Core runs
02Manifest lineage parsing to connect dbt models to Power BI data sources
03Run history tracking with model-level pass/fail status
04Incident creation for failed dbt runs with model-level detail
MetricSign vs alternatives
Existing tools like dbt Cloud, Custom Slack/email notifications, Airflow task monitoring are built for their own domain — not for connecting dbt Core failures to downstream Power BI report health. MetricSign bridges that gap: you get one incident feed that covers both layers without switching between dashboards.
Alternatives
—dbt Cloud
—Custom Slack/email notifications
—Airflow task monitoring
MetricSign
✓Covers dbt Core and Power BI in one view
✓Chain visualization from source to report
✓One incident feed, not multiple alert tools
✓Free to start, no credit card required