Monitoring and alerting¶
Monitoring and alerting are core concepts in the MatrixOne Intelligence product model. This page explains the problems they solve, their relationships with other objects, and their usage boundaries.
Definition¶
Monitoring and alerting cover workflow jobs, SQL history, operation logs, and alert records.
Jobs and SQL history focus on individual executions, while operation logs focus on workspace write operations and service responses.
Alerts notify recipients when metrics or states continuously meet specified conditions.
Object relationships¶
AI Studio monitoring covers workspace tasks, Genesis usage covers model requests, and MatrixOne monitoring covers database instances.
Cross-service troubleshooting requires execution IDs, request IDs, and server timestamps to correlate records.
Whether the alerting entry point is available depends on the deployment version and which features are enabled.
Design principles¶
Use least privilege and keep credentials in managed configuration.
Start by validating with minimal data or test objects, then expand the scope.
Version executable configuration and retain each run as an execution record.
Do not equate a visible entry with backend availability or resource authorization.
Note
These pages follow the current MOI 5.0 product model. If an entry is missing, check the workspace, permissions, and feature flags.