tutorial

Monitoring Datafold with Vigilmon: Data Reliability Platform Health, API Availability & Webhook Delivery

How to monitor Datafold data reliability and data diff infrastructure with Vigilmon — API availability, dashboard uptime, webhook delivery health, and SSL certificate validity.

Datafold is the data reliability platform that brings column-level lineage and automated data diff to your SQL transformations, catching regressions in dbt models and data warehouse changes before they reach downstream dashboards and reports. When Datafold's API goes down, CI/CD integrations stop running data diff checks on pull requests silently. When the dashboard becomes unavailable, data engineers lose access to the column-level lineage and impact analysis they need to safely ship warehouse schema changes. When webhook delivery fails, integrations with GitHub, Slack, and PagerDuty stop receiving data diff summaries and regression alerts, leaving breaking changes invisible until they surface in production. Vigilmon gives you external visibility into Datafold's availability: the API, dashboard, and outbound webhook endpoints, so you know the moment the reliability platform itself becomes unreliable.

What You'll Build

  • An HTTP monitor on the Datafold dashboard to detect frontend failures
  • A health-check monitor on the Datafold REST API to catch backend degradation
  • A monitor on your webhook receiver to verify Datafold alert delivery is flowing
  • A monitor on the Datafold CI integration endpoint to catch pull request check failures
  • An SSL certificate monitor for your Datafold domain
  • Alerting that distinguishes API outages from CI integration failures

Prerequisites

  • A Datafold account with API access (cloud-hosted deployment)
  • The Datafold dashboard accessible via HTTPS (e.g., https://app.datafold.com or your organization's domain)
  • A webhook receiver endpoint configured to accept Datafold diff summary and alert notifications
  • A free account at vigilmon.online

Step 1: Understand Datafold's Service Architecture

Datafold's cloud deployment centers on a set of cooperating services:

| Component | Default port | Role | |---|---|---| | Datafold Dashboard | 443 (HTTPS) | Web UI for data diffs, column-level lineage, and catalog browsing | | Datafold REST API | 443 (HTTPS) | CI/CD integration triggers, diff computation, lineage queries | | CI runner service | Internal + outbound | Connects to warehouse (Snowflake, BigQuery, Redshift) to compute diffs on PR | | Webhook dispatcher | Outbound | Delivers diff summaries and alerts to GitHub, Slack, PagerDuty, custom endpoints |

External monitoring focuses on the API and dashboard HTTPS endpoints — these surface the availability of the entire Datafold deployment and are the interfaces your engineers and CI/CD pipelines interact with directly.

Step 2: Monitor the Datafold Dashboard with HTTP Check

The Datafold dashboard is the primary interface for reviewing data diff results, browsing column-level lineage, and understanding the downstream impact of schema changes before merging:

curl -I https://app.datafold.com
# Returns HTTP 200 with HTML when the frontend is healthy
  1. Log in to Vigilmon → Add Monitor → HTTP.
  2. URL: https://app.datafold.com (or your organization's Datafold domain).
  3. Check interval: 60 seconds.
  4. Response timeout: 15 seconds.
  5. Expected status: 200.
  6. Keyword: Datafold (appears in the page title and HTML content).
  7. Click Save.

This monitor catches:

  • Datafold frontend process crashes or failed deployments
  • CDN or load balancer misconfigurations blocking dashboard access
  • Failed Datafold platform upgrades that leave the UI returning 5xx errors
  • DNS resolution failures for the Datafold domain

Alert sensitivity: Set to trigger after 1 consecutive failure. When the Datafold dashboard is unavailable, data engineers cannot review open diff results or understand the column-level blast radius of a warehouse schema change currently in review.

Step 3: Monitor the Datafold REST API

Datafold's REST API is used by both the dashboard frontend and by CI/CD pipelines that trigger data diff computations automatically on every dbt pull request. When the API is degraded, automated diff checks stop running on PRs even if the dashboard HTML appears to load from cache:

curl https://app.datafold.com/api/v1/health
# Returns: {"status": "ok"} when the API is healthy
  1. Add Monitor → HTTP.
  2. URL: https://app.datafold.com/api/v1/health.
  3. Check interval: 60 seconds.
  4. Response timeout: 10 seconds.
  5. Expected status: 200.
  6. Keyword: ok (present in healthy API responses).
  7. Label: Datafold API health.
  8. Click Save.

Why monitor the API separately from the dashboard? The dashboard may serve cached HTML from a CDN even when the API backend is down. A failing API means Datafold cannot compute data diffs on open pull requests, cannot deliver diff summaries to GitHub PR comments, and cannot answer lineage queries from engineers trying to understand the downstream impact of a pending schema change.

Step 4: Monitor Your Webhook Receiver

Datafold delivers diff summaries and regression alerts to your CI/CD and on-call tools (GitHub, Slack, PagerDuty, custom webhooks) via outbound HTTP calls. If your webhook receiver becomes unavailable or returns errors, Datafold notification delivery fails silently — pull requests no longer receive diff summaries as comments, and data regression alerts stop reaching the on-call team:

curl https://your-webhook-receiver.example.com/health
# Returns: {"status": "ok"} when the receiver is up
  1. Add Monitor → HTTP.
  2. URL: https://your-webhook-receiver.example.com/health.
  3. Check interval: 2 minutes.
  4. Response timeout: 10 seconds.
  5. Expected status: 200.
  6. Keyword: ok.
  7. Label: Datafold webhook receiver.
  8. Click Save.

If your receiver is a hosted service (GitHub, Slack), monitor your own middleware or integration relay instead. For GitHub status, you can monitor https://www.githubstatus.com/api/v2/status.json for API-level availability confirmation.

Step 5: Monitor the Datafold CI Integration Endpoint

For teams using Datafold's automated CI integration to run data diff checks on every dbt pull request, a dedicated CI status endpoint confirms the integration runner is available and connected to your warehouse:

curl https://app.datafold.com/api/v1/ci/status
# Returns CI runner status and last successful diff computation timestamp
  1. Add Monitor → HTTP.
  2. URL: https://app.datafold.com/api/v1/ci/status.
  3. Check interval: 5 minutes.
  4. Response timeout: 15 seconds.
  5. Expected status: 200.
  6. Keyword: status (present in the response JSON).
  7. Label: Datafold CI integration.
  8. Click Save.

CI integration failures mean pull requests no longer receive automated data diff comments, and data engineers must manually run comparisons to assess the impact of pending warehouse changes — slowing down the review process and increasing the risk that a regression ships to production undetected.

Step 6: Monitor SSL Certificates

Datafold's dashboard and REST API are accessed over HTTPS by both data engineers and the CI/CD pipelines that call Datafold's API to trigger diff computations and post results back to pull requests. An expired certificate breaks both browser access and programmatic API calls:

openssl s_client -connect app.datafold.com:443 2>/dev/null | openssl x509 -noout -dates
  1. Add Monitor → SSL Certificate.
  2. Domain: app.datafold.com (or your organization's Datafold domain).
  3. Alert when expiry is within: 30 days.
  4. Alert again: 14 days, 7 days, 3 days, 1 day.
  5. Click Save.

CI/CD pipeline impact: Data pipelines that call Datafold's API as a quality gate in CI will fail with TLS errors when the certificate expires. Because CI pipelines often treat Datafold as an optional advisory step rather than a hard gate, these failures may be silent — diffs stop running without blocking the merge, and the regression check is simply absent from the PR.

Step 7: Configure Alerting

In Vigilmon under Settings → Notifications, configure your alert channels:

| Monitor | Trigger | Action | |---|---|---| | Dashboard | Non-200 or Datafold missing | Check Datafold frontend deployment; inspect CDN and load balancer | | API health | Non-200 or ok missing | Backend down; check Datafold service logs; verify warehouse connectivity | | Webhook receiver | Non-200 or ok missing | CI/PR diff comments not posting; verify receiver deployment | | CI integration | Non-200 or status missing | Automated diffs not running on PRs; check warehouse connector credentials | | SSL certificate | < 30 days to expiry | Renew certificate; verify CI pipeline API clients reconnect after renewal |

Alert after: 1 consecutive failure for the dashboard and API health monitors. 2 consecutive failures for the CI integration and webhook receiver monitors to reduce noise from transient warehouse connection timeouts during peak query periods.

Common Datafold Failure Modes and What Vigilmon Catches

| Scenario | Vigilmon monitor | |---|---| | Datafold API process crash | API health monitor fires; CI diff computations stop on open PRs | | Dashboard frontend deployment failure | Dashboard monitor fires; engineers cannot review lineage or diff history | | Webhook receiver crash | Webhook receiver monitor fires; PR diff comments stop posting; on-call alerts silent | | CI integration runner failure | CI integration monitor fires; pull requests ship without diff validation | | TLS certificate expired | SSL monitor alerts at 30-day threshold; API clients and browsers fail | | DNS misconfiguration | All monitors fire simultaneously | | Warehouse credential rotation breaks CI runner | CI integration monitor fires; diff computations fail at warehouse query stage | | Datafold upgrade leaves API in broken state | API health monitor fires; dashboard monitor may also fire |

Monitoring Data Diff Results Themselves (Beyond Infrastructure)

Vigilmon monitors Datafold's infrastructure endpoints — the API, dashboard, CI integration runner, and webhook receiver. The health of individual data diff results and regression findings is a separate concern that requires review within Datafold itself:

  • Datafold's built-in alerting: Configure alert policies within Datafold to route regression detections to Slack, PagerDuty, or email — this is distinct from monitoring Datafold's own availability.
  • CI pipeline coverage: Audit which dbt projects and repositories have Datafold CI integration configured to ensure new models are covered automatically.
  • Lineage freshness: Datafold's catalog sync tracks column-level lineage from your warehouse. A stale catalog may indicate warehouse connectivity issues separate from Datafold's API availability.

Vigilmon catches infrastructure-level failures — when Datafold itself is down. Data quality regressions detected by a healthy Datafold deployment require Datafold's own notification rules and PR review workflows.

Datafold is the layer that makes your data warehouse changes auditable — when it goes down, column-level regressions in dbt model outputs and warehouse schema changes ship to production without automated diff validation, and data engineers lose the lineage context needed to quickly diagnose a downstream impact. Vigilmon gives you external visibility into Datafold's availability that doesn't depend on Datafold self-reporting: API uptime, dashboard health, CI integration status, and SSL certificate validity, so you know the moment the reliability platform itself needs attention and can restore automated data diff coverage before the next breaking change slips through code review.

Start monitoring Datafold in under 5 minutes — register free at vigilmon.online.

Monitor your app with Vigilmon

Free plan — 5 monitors, no credit card required. Up and running in 60 seconds.

Start free →
← Back to all articles