tutorial

Monitoring Metaplane with Vigilmon: Data Reliability Platform Health, API Availability & Alert Delivery

How to monitor Metaplane data reliability and data quality monitoring infrastructure with Vigilmon — platform uptime, API availability, incident webhook delivery, and SSL certificate validity.

Metaplane is the data reliability platform that connects to your data warehouse and automatically monitors tables, columns, and metrics for unexpected changes — tracking row count anomalies, freshness delays, null rate spikes, and distribution shifts across Snowflake, BigQuery, Redshift, and dbt models. When the Metaplane platform becomes unavailable, data teams lose real-time visibility into warehouse health and the automated incident alerts they depend on to catch data issues before stakeholders notice them in BI dashboards. When the Metaplane API is degraded, integrations with dbt Cloud and Airflow that pull data quality signals cannot retrieve freshness and anomaly status. When incident webhook delivery fails, Slack and PagerDuty notifications for detected data issues stop flowing, leaving data quality problems undiscovered until a business user reports a wrong number. Vigilmon gives you external visibility into Metaplane's infrastructure: the platform dashboard, the monitoring API, and your incident delivery endpoints, so you know the moment the data reliability platform itself needs attention.

What You'll Build

  • An HTTP monitor on the Metaplane platform dashboard to detect availability failures
  • A health-check monitor on the Metaplane API to catch backend degradation
  • A monitor on your webhook receiver to verify Metaplane incident delivery is flowing
  • A monitor on the Metaplane incident notification endpoint to catch dispatch failures
  • An SSL certificate monitor for your Metaplane domain
  • Alerting that distinguishes platform outages from API and notification delivery failures

Prerequisites

  • A Metaplane account (cloud-hosted SaaS)
  • The Metaplane platform dashboard accessible via HTTPS
  • A webhook receiver endpoint configured to accept Metaplane incident notifications
  • A free account at vigilmon.online

Step 1: Understand Metaplane's Service Architecture

Metaplane operates as a cloud-native data reliability platform with several monitorable components:

| Component | Default port | Role | |---|---|---| | Platform dashboard | 443 (HTTPS) | Web UI for reviewing data incidents, configuring monitors, and managing warehouse connections | | Metaplane REST API | 443 (HTTPS) | Delivers freshness, anomaly, and schema change data to external integrations and CI/CD pipelines | | Incident dispatcher | Outbound | Delivers incident notifications to Slack, PagerDuty, email, and custom webhooks | | Monitor scheduler | Internal | Runs automated quality checks against connected data warehouse tables on a defined cadence |

External monitoring focuses on the platform dashboard and REST API — these are the interfaces your data teams and pipeline integrations use to retrieve reliability signals and investigate incidents.

Step 2: Monitor the Metaplane Platform Dashboard

The Metaplane platform dashboard is the primary interface for reviewing active incidents, understanding anomaly context across related tables, configuring data source monitors, and tracking data quality trends over time:

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

This monitor catches:

  • Metaplane frontend deployment failures or infrastructure outages
  • Application container restarts that leave the dashboard returning 5xx errors
  • Failed Metaplane platform upgrades that break the UI
  • DNS resolution failures for the Metaplane application domain

Alert sensitivity: Set to trigger after 1 consecutive failure. When the Metaplane dashboard is unavailable, data engineers cannot investigate active incidents, review anomaly context, or acknowledge data quality issues — leaving the team without visibility into the reliability of their most critical warehouse tables.

Step 3: Monitor the Metaplane REST API

The Metaplane REST API enables pipeline integrations to programmatically query data quality signals — checking table freshness before a downstream transformation runs, confirming no anomalies are active before a dashboard refreshes, or pulling incident status for custom quality gate logic in CI/CD:

curl https://api.metaplane.dev/health
# Returns: {"status": "ok"} when the API backend is operational
  1. Add Monitor → HTTP.
  2. URL: https://api.metaplane.dev/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: Metaplane API health.
  8. Click Save.

Why monitor the API separately from the dashboard? The Metaplane dashboard may display incident history from a cached or read-only state even when the API is returning errors for write operations. A failing API means your dbt pipeline quality gates cannot retrieve freshness checks, Airflow DAGs that depend on Metaplane signals cannot verify table readiness, and programmatic incident management integrations fail silently.

Step 4: Monitor Your Webhook Receiver

Metaplane delivers incident notifications and anomaly alerts to your on-call tools (Slack, PagerDuty, custom webhooks) via outbound HTTP POST requests. If your webhook receiver becomes unavailable or returns errors, incident notification delivery fails silently — engineers stop receiving alerts about row count drops, freshness delays, and null rate spikes until a downstream dashboard shows incorrect data:

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: Metaplane webhook receiver.
  8. Click Save.

For Slack incoming webhooks, verify https://slack.com/api/api.test to confirm the Slack API is reachable for incident alert delivery. For PagerDuty, monitor https://status.pagerduty.com/api/v2/status.json to catch PagerDuty degradation that would block incident creation from Metaplane anomalies.

Step 5: Monitor the Metaplane Incident Notification Endpoint

Metaplane's incident notification system manages the delivery of data quality alerts to configured channels. When this internal endpoint is degraded, Metaplane continues detecting anomalies and freshness violations but fails to dispatch the notifications — creating a silent gap between detected issues and the engineers who need to investigate them:

curl https://api.metaplane.dev/v1/notifications/health
# Returns notification system health when the endpoint is available
  1. Add Monitor → HTTP.
  2. URL: https://api.metaplane.dev/v1/notifications/health.
  3. Check interval: 5 minutes.
  4. Response timeout: 15 seconds.
  5. Expected status: 200.
  6. Keyword: health (present in the response JSON).
  7. Label: Metaplane notification health.
  8. Click Save.

Notification endpoint degradation is one of the most operationally dangerous failure modes in data reliability platforms: tables go stale, row counts drop, null rates spike, and none of the configured alert recipients receive a signal. The incident is only discovered when a business user questions a number in a report — often hours or days after the data quality violation occurred.

Step 6: Monitor SSL Certificates

Metaplane's platform dashboard and REST API are accessed over HTTPS by both data engineers using the web interface and automated pipeline integrations making API calls. An expired certificate blocks browser access to incident investigation and causes API clients embedded in dbt Cloud and Airflow to fail with TLS verification errors:

openssl s_client -connect app.metaplane.dev:443 2>/dev/null | openssl x509 -noout -dates
openssl s_client -connect api.metaplane.dev:443 2>/dev/null | openssl x509 -noout -dates
  1. Add Monitor → SSL Certificate.
  2. Domain: app.metaplane.dev (and a second monitor for api.metaplane.dev).
  3. Alert when expiry is within: 30 days.
  4. Alert again: 14 days, 7 days, 3 days, 1 day.
  5. Click Save.

dbt Cloud integration impact: Metaplane integrates with dbt Cloud to surface freshness and anomaly status alongside dbt model run results. When the Metaplane API certificate expires, the dbt Cloud integration fails to retrieve quality signals, and data engineers lose the side-by-side view of model health and data reliability that makes root cause analysis faster during a pipeline incident.

Step 7: Configure Alerting

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

| Monitor | Trigger | Action | |---|---|---| | Platform dashboard | Non-200 or Metaplane missing | Check Metaplane platform status; review infrastructure health | | API health | Non-200 or ok missing | API down; pipeline quality gates and integrations failing | | Webhook receiver | Non-200 or ok missing | Incident alerts not delivering; verify receiver deployment | | Notification health | Non-200 or health missing | Anomalies detected but not alerted; check Metaplane notification config | | SSL certificate | < 30 days to expiry | Renew certificate; verify API clients reconnect cleanly |

Alert after: 1 consecutive failure for the dashboard and API health monitors. 2 consecutive failures for notification and webhook receiver monitors to absorb transient timeouts during peak anomaly detection windows.

Common Metaplane Failure Modes and What Vigilmon Catches

| Scenario | Vigilmon monitor | |---|---| | Metaplane platform outage | Dashboard monitor fires; incident investigation blocked | | REST API degradation | API monitor fires; pipeline quality gates and dbt integrations fail | | Webhook receiver crash | Webhook monitor fires; Slack and PagerDuty alerts stop posting | | Notification dispatch failure | Notification monitor fires; incidents detected but not alerted | | TLS certificate expired | SSL monitor alerts at 30-day threshold; browser and API clients fail | | DNS misconfiguration | All monitors fire simultaneously | | Metaplane API key rotation | API monitor may fire with 401 errors; integrations need key updates | | Monitor scheduler backlog | Dashboard may show stale anomaly data during high-volume periods |

Monitoring Data Quality Itself (Beyond Infrastructure)

Vigilmon monitors Metaplane's infrastructure endpoints — the platform dashboard, REST API, notification system, and your webhook receiver. The health of individual data monitors and detected anomalies is a separate concern managed within Metaplane itself:

  • Metaplane's built-in alerting: Configure notification channels within Metaplane (Slack, PagerDuty, email, custom webhooks) to route incident alerts to on-call teams — this is distinct from monitoring Metaplane's own availability.
  • Monitor coverage: Regularly audit which tables and metrics have Metaplane monitors enabled to ensure new data assets added to your warehouse are automatically included in quality monitoring.
  • Incident review process: Establish a weekly review of Metaplane's incident history to identify patterns — tables with recurring freshness violations or columns with persistent null rate drift may require upstream pipeline changes rather than just alert acknowledgment.

Vigilmon catches infrastructure-level failures — when Metaplane itself is down. Individual data anomaly coverage and reliability improvements within a healthy Metaplane deployment require Metaplane's own monitor configuration and incident response workflows.

Metaplane is the layer that makes your data warehouse reliability visible — when it goes down, anomaly detection stops, freshness checks break, and data engineers lose the real-time incident feed they rely on to catch data quality violations before they surface in stakeholder dashboards. Vigilmon gives you external visibility into Metaplane's availability that doesn't depend on Metaplane self-reporting: dashboard uptime, API health, notification system status, and SSL certificate validity, so you know the moment the data reliability platform itself needs attention and can restore monitoring coverage before the next pipeline run pushes unvalidated data to your business metrics.

Start monitoring Metaplane 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