Agent based support to generate observation alerts

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
2025

The Data Integrity Suite supports generating freshness, volume, data drift and schema drift alerts for those data assets that are fetched by the agent. This helps to identify any anomalies in the assets and generate the corresponding alerts. This functionality is currently supported for Oracle and Microsoft SQL connections.

Note:
  • Schema drift alerts for assets fetched from the agent are generated based on the schedule associated with the alert type. The table deleted alert is generated depending on the Discovery schedule and column deleted, column added, column datatype change alerts are generated based on the Observer schedule.
  • An Observer is necessary for generating alerts, but the schedule is determined depending on the type of alert.
Follow the steps below to observe and generate alerts for those assets that are fetched by the agent.
Steps to observe and generate volume, data drift and schema drift alerts for those assets that are fetched by the agent Steps to observe and generate freshness alerts for those assets that are fetched by the agent
  1. Install the Agent.
  2. Ensure the Agent is healthy.
  3. Proceed to establish a new connection.
  4. Trigger the onboarding flow, enable the profile datasets option and schedule the discovery. This will initiate Cataloging and Profiling for the selected data assets at the scheduled time.
  5. Create an Observer with the required assets and schedule the Observer to run accordingly.
    Tip: It is recommended to schedule the Observer after a short duration following the completion of the onboarding flow. This would ensure that the datasets are profiled, cataloged and available to be selected during the process.

  6. Monitor the alerts generated from the Observer run and take corrective actions to fix the anomalies.

  1. Install the Agent.
  2. Ensure the Agent is healthy.
  3. Proceed to establish a new connection.
  4. Ensure that the metadata is available within the Catalog section.
  5. Create a new Observer by selecting the required assets and ensure the scheduler is disabled.
  6. Enable the profile datasets toggle in the insights page of the established connection and initiate the onboarding flow.
  7. Enable the scheduler for the observer.
  8. The observer upon successful run will generate alerts accordingly.
Note:
  • The datasets fetched from the agents are differentiated with a configuration icon for easy identification.
  • Agent based data assets can be used to create an observer or profiler if the pipeline engine associated with the connection is available in the workspace.
  • The filter datasets option is available to be selected only for the assets discovered through the onboarding flow.