Monitoring checks - Domino

Monitoring checks connect governance to Domino Model Monitoring (DMM) and respond to alerts without reprocessing raw data. Governance listens for drift and data quality alerts. When an alert triggers, governance creates findings with severity levels and assigns owners for follow-up. All alerts, actions, and results are logged in the governance notebook and dashboard for audit compliance.

Prerequisites

You need the GovernanceAdmin role to define checks in policies. Roles and security has details on role assignment. For monitoring checks, you also need:

Domino Model Monitoring (DMM) configured and running
Model endpoints registered with DMM

Monitoring checks

Monitoring checks listen for drift and data quality alerts from DMM without reprocessing raw data. Governance registers model endpoints with DMM and subscribes to alert notifications. When DMM detects an issue, governance evaluates the alert against policy rules and takes action:

Drift or data quality alert received: Finding created with high severity
Alert threshold exceeded: Owner assigned for investigation

All monitoring activity is recorded in the governance notebook with timestamps, alert details, and action history. Define monitoring checks in Policy components has YAML configuration details for monitoring checks.

Known issues and limitations

Monitoring checks require DMM to be configured before policies can reference endpoints.
Endpoints must be attached to the bundle before the checks are set up: Endpoint overview > Versions > Endpoint version > Add to bundle

Next steps

Manual evidence: add text responses, files, and artifacts to bundles
Automated checks: run metrics and scripted validations
Add findings to a bundle: document review decisions and track issues

Automated checks Approvals

⌘I