DQLabs Data Observability

DQLabs data testing

DQLabs checks SQL tables, compares tables, and shows the rows that fail. It generates checks across quality dimensions from profiling or plain-language prompts.

Compare: data testing tools

• SQL Table Tests: Conditional metrics define row-level rules every record must satisfy, alongside auto-generated pattern, frequency and statistics checks across quality dimensions (docs).

• Table Comparison Tests: Comparison metrics compute a metric from two datasets and evaluate the difference, ratio or percentage deviation, for migration and reconciliation (docs).

• Inspect Failed Rows: The Exception Records page lists every failing record captured across metrics, with filters and remediation (docs).

• DataFrame Tests: Checks run against connected sources (pushed down where possible); no in-memory DataFrame validation library is offered (docs).

• Unstructured Data Tests: Unstructured data validation is described only as an extension of the agentic roadmap; no checks on free-text columns or documents are documented (docs).

• Data Diff: Comparison metrics compare aggregate values between datasets; no row-by-row diff of two tables is documented (docs).

• Data Contracts: Business and reconciliation metrics can enforce contract rules, and the website mentions contract-level scores, but no machine-readable contract spec is documented (docs).

DQLabs data observability

DQLabs profiles every attribute and uses statistical and ML models to learn expected ranges on every metric. Monitors are configured in the UI, and DQLabs also monitors Airflow, Azure Data Factory and dbt jobs.

Compare: data observability tools · data profiling tools

• Data Profiling: Automated profiling computes structure, patterns and statistics for every attribute (docs).

• Anomaly Detection: Statistical and ML models learn expected ranges and flag outliers and drift on every metric (docs).

• Freshness Monitors: Freshness metrics are generated automatically for connected assets (docs).

• Volume Monitors: Volume metrics track row counts automatically (docs).

• Schema Monitors: Schema metrics detect structural changes automatically (docs).

• Field Monitors: Structural metrics (statistics, frequency, pattern) are auto-generated per column and tracked over time (docs).

• Distribution Monitors: Distribution metrics track how column values are spread and flag drift (docs).

• Segment Monitors: Metrics can be segmented by column values, with scores and exceptions tracked per segment (docs).

• Custom SQL Monitors: Query metrics run custom SQL as a monitored metric (docs).

• UI-Based Monitors: Metrics are created in the UI via Metric > Add, with no code required (docs).

• Pipeline Monitoring: Monitors Airflow DAGs and tasks, ADF pipelines and dbt jobs for failures and execution status (docs).

• Monitors-as-Code: Metrics are created in the UI or via the REST API; no YAML or version-controlled metric definitions are documented (docs).

• Partition-Based Monitors: Not documented (docs).

• Window-Based Monitors: Dashboards use comparison windows, but tumbling or sliding windows for metric evaluation are not documented (docs).

DQLabs incident management

DQLabs triages issues, takes feedback on alerts and opens tickets.

• Alert Notifications: Alerts go to Slack, Microsoft Teams, Google Chat and email (docs).

• Incident Triage: Issues give a structured workflow to assign, prioritize and track problems, and related alerts are clustered into one incident (docs).

• Alert Feedback: Users can Mark as Normal an alert that needs no remediation, with a required note (docs).

• Incident Resolution: Alerts and issues have a resolution lifecycle with notes, issue linkage and automatic resolution when metrics recover (docs).

• Ticketing Integrations: Bidirectional Jira and ServiceNow integrations (docs).

• On-Call Integrations: Integrations list Slack, Teams, Google Chat, email, Jira and ServiceNow; no PagerDuty or Opsgenie integration is documented (docs).

DQLabs data quality analytics

DQLabs' dashboards, health scores and resolution metrics track data quality over time.

• Data Quality Dashboards: The Quality Dashboard shows DQ score trends, alerts, issues and an AI summary (docs).

• Data Health Scores: Quality scores roll up at asset, domain, product, application and tag level (docs).

• Incident Resolution Metrics: The Quality Dashboard tracks issue counts and average age of DQ issues over time (docs).

DQLabs data lineage

DQLabs extracts lineage at table and column level from query logs, access history, view definitions and dbt or Airflow, with impact analysis.

Compare: data lineage tools

• Table-Level Lineage: Automated lineage across tables, transformations and models (docs).

• Column-Level Lineage: Column-level lineage shows which source column feeds which target column, with transformation logic (docs).

• End-to-End Lineage: Lineage runs from raw sources through transformations to dashboards and reports, including Airflow and dbt (docs).

• Impact Analysis: Maps every downstream consumer affected by a change to a dataset or column (docs).

DQLabs data governance

DQLabs's catalog, classification and data products overlap with data governance tools.

• Data Catalog: Built-in catalog of assets with glossary, domains, tags, ownership and a catalog dashboard (docs).

• Data Catalog Integration: Integrates with Alation, Collibra, Atlan and Microsoft Purview (docs).

• Data Classification: Automated discovery and classification of assets, with classification tags such as PII, PHI and PCI (docs).

• Data Products: Data Products group assets around a business concept with defined quality expectations (docs).

DQLabs FinOps

DQLabs tracks query performance and compute credit usage by database and schema, with budget alerts.

• Query Performance: Queries metrics measure query volume, efficiency and reliability, enabled automatically (docs).

• Cost Monitoring: Credits metrics track compute credit consumption by database and schema for budget alerting (docs).

DQLabs workflows

DQLabs has a REST API, scheduling and a dbt integration. A GitHub Action posts lineage impact analysis on pull requests that change dbt models. It has no Python SDK.

• Scheduling: The Command Center schedules metric and profiling jobs (docs).

• CI/CD Integrations: A GitHub Action posts lineage impact analysis on pull requests that change dbt models (docs).

• REST / GraphQL API: REST API covering assets, metrics, alerts, issues, lineage and governance (docs).

• MCP Server: MCP access tokens connect clients such as Claude Desktop and Cursor to Prizm (docs).

• dbt Integration: Connects to dbt Cloud or dbt Core to ingest lineage, job health and dbt test results (docs).

• Python SDK: Offers a REST API but no Python SDK (docs).

• Webhooks: Inbound webhooks are used for dbt Cloud and Jira sync; outbound webhooks for alerts are not documented (docs).

DQLabs AI agents

DQLabs has Converse, a chat interface for managing assets and exploring the catalog. It writes checks from prompts, suggests checks automatically, triages issues and recommends fixes such as re-running a job. An MCP server is also available.

• AI Chat Assistant: Converse is a chat interface for managing assets, triggering workflows and exploring the catalog in natural language (docs).

• Natural Language Test Generation: Converse recommends DQ rules and generates measures from natural language requests (docs).

• Automated Test Generation: Structural and operational metrics are auto-generated on profiling, and a rule recommendation engine suggests DQ rules (docs).

• AI Issue Triaging: Alert clustering groups related signals into one incident and ranks them by lineage, usage and business criticality (docs).

• AI Issue Resolution: Autonomous Issue Resolution recommends fixes such as re-running a job, setting a default value or quarantining bad records, governed by AI Stewardship approval levels (docs).