MetricSign
Start free
transformation

Power BI Monitoring for dbt Core

Teams that ask about dbt core vs dbt cloud usually need to monitor both sides of the comparison together. 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
45-day free trial, no credit card required

Common dbt Core error codes

View all 139
Connection Error
dbt could not establish a connection to the target warehouse. The run was aborted before any models
ContractBreakingChangeError
dbt detected a breaking change to a versioned model's enforced contract — such as a column removal o
ContractBreakingChangeError
dbt rejected a model change because it violates an enforced data contract — a column was removed, it
Compilation Error: Incorrect YAML spec
A dbt schema YAML file has valid YAML syntax but does not conform to the dbt schema specification. K
Compilation Error: Invalid Jinja
dbt encountered a Jinja templating error during compilation. An unclosed block, undefined variable,
Compilation Error: Invalid ref function
A ref() call in a dbt model references a model that does not exist in the project. The model name is

Other integrations