Filter datasets to generate alerts - Precisely Data Integrity Suite

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Create alerts based on filter conditions applied to table fields. You can add single or multiple conditions to observe specific data subsets. Use filtered datasets to generate volume, data drift, and freshness alerts for the exact data you need to monitor.

A filter condition like Firstname equal Joe generates alerts and profiling results only for rows where Firstname equals Joe.
Note: The filter dataset link is accessible only when you have at least one Data Integrity Suite asset. You cannot use the filter dataset link when the selected assets belong to datasets that are not part of the Data Integrity Suite.

Profiling statistics are calculated from the filtered dataset only, not the entire table. For example, if a table has 100 total records but your filter returns 10 records, all statistics are based on those 10 filtered records.

To filter selected datasets:
  1. Go to Observability > Observers and select + Create Observer.
  2. Select the datasets and fields you want to observe, then click Next.
  3. Select the Filter Selected Datasets link.
  4. Select the dataset to filter.
  5. Select the field, operator, and value. Add multiple conditions as needed. Choose Match All for logical AND or Match Any for logical OR.
  6. Complete the remaining Observer creation steps.

The Observer saves with your filter conditions, and you're redirected to the Observers page.

Note:
  • Datetime values are assumed to be in UTC timezone.
  • Float values are rounded to two decimal places for filtering. For example, 100.2367 becomes 100.24.
  • The where clause can reference columns not in the observed column list.
  • Columns in the where clause must be cataloged.
  • Changing filter conditions is treated as a data change, which may increase or decrease volume and trigger alerts.

Limitation with quoted database objects: Tables or columns with single or double quotes in their names (for example, 'TableName' or "ColumnName") can cause Observer runs to fail. Rename affected objects without quotes.