Skip to main content
As a data engineer, you build and maintain the pipelines that keep data flowing. AnomalyArmor helps you catch breaking changes before they impact downstream systems.
Data Engineer Journey: Connect (~5 min) → Discover (~3 min) → Monitor (~5 min) → Alert (~5 min)

Your Key Workflows

Detect Breaking Schema Changes

Schema drift is your biggest enemy. A column rename or type change can silently break pipelines that ran fine yesterday.
1

Connect Your Database

Start with your most critical production database. Connect now
2

Run Discovery

AnomalyArmor catalogs all tables, views, and columns. Run discovery
3

Configure Schema Alerts

Get notified of column additions, removals, type changes, and renames. Set up alerts

Integrate with Your CI/CD

Gate deployments on data quality using the CLI:
Full CLI reference

Automate with Webhooks

Trigger actions when schema changes are detected:
Python SDK guide

Common Tasks

Set Up dbt Integration

Run AnomalyArmor checks as part of dbt runs

Airflow Pre-flight Checks

Gate DAG tasks on data freshness

GitHub Actions Integration

Add data quality checks to your CI pipeline

CLI Reference

Full command documentation

Common Questions

How do I gate a dbt run or Airflow DAG on data freshness?

Use the armor freshness check <asset> CLI command in your pipeline. It exits non-zero when data is stale, which blocks the next step in most orchestrators. See CLI overview and Airflow integration.

Can AnomalyArmor catch a breaking schema change before my pipeline runs?

Yes, if you schedule discovery to run before your pipelines. Point discovery at production every hour and schedule it 30-60 minutes before your main ETL windows. Breaking changes (column removed, type changed) fire alerts on the next discovery.

How do I send schema change alerts to a webhook for automation?

Create a webhook destination, then build an alert rule scoped to the change types you care about (e.g. column_removed, type_changed). Incoming payloads include asset name, change type, and diff for your automation to act on. See Webhook destinations.

Can I pull schema change history programmatically?

Yes, via the Python SDK: client.schema.changes(since="24h", change_types=[...]). See Python SDK guide.

How does AnomalyArmor handle column renames?

Today a rename surfaces as a column removed plus a column added. You can correlate the pair in your webhook handler or alert rule. Automatic rename detection is on the roadmap.