Area: Observability
Sub-Area: Assertions
Issue
Data quality assertions fail to create, execute, or display properly in the UI. This includes freshness assertions, schema assertions, and SQL assertions that either cannot be configured or do not run as expected.
Common Error Messages:
Monitor limit exceeded (current monitors exceed maximum allowed)
Solution
Note: For DataHub Cloud customers, infrastructure-level changes (Kubernetes, AWS resources, operating system configurations) are managed by DataHub Support. The solutions below focus on configuration changes that customers can implement.
Verify assertion prerequisites:
- Ensure assertions are enabled in your DataHub instance
- Check that the target dataset exists and is properly ingested
- Confirm you have Editor or Admin role to create assertions
Create assertions through UI:
- Navigate to dataset → Validation tab
- Click "Create Assertion"
- Configure assertion type (Freshness, Schema, SQL, Volume)
- Set appropriate schedule and failure thresholds
Troubleshoot assertion execution:
- Check assertion run history in the UI
- Review executor logs for specific error messages
- Verify database credentials have SELECT permissions for SQL assertions
- Ensure the assertion query syntax is compatible with your database dialect
For SQL assertions not visible after upgrade:
- This may be a known issue in specific versions
- Check if SQL assertion feature flag is enabled
- Contact DataHub Support if assertions disappeared after upgrade
- Consider recreating assertions if they are not recoverable
Debug failed assertions:
- Review the assertion configuration for typos or incorrect field references
- Test SQL queries directly against the database before using in assertions
- Check if freshness assertion schedule aligns with data ingestion schedule
Additional Notes
Always backup your DataHub configuration before making changes. Test solutions in a non-production environment when possible.
Related Documentation
Related Tickets
- 5847, 5899, 5772, 5732, 5606, 5771, 5584, 5952, 5750, 5901
Tags:
assertions, data-quality, monitoring, troubleshooting