Page Comparison

...

1. Schedule. Monitors can be scheduled to run using your preferred enterprise scheduling capability (Control-M, Airflow, Autosys, etc.)

   1. While the details will depend on the specific scheduling software, at the highest level, the user simply needs to create a REST call to the ModelOp Center API. Here are the steps:

      1. Obtain the Model snapshot’s unique ID, which can be obtained from the Model snapshot screen. Simply copy the ID from the URL bar:

         1. Example:

            

      2. Within the scheduler, configure the REST call to ModelOp Center’s automation engine to trigger the monitor for your model:

         1. Obtain a valid auth token

         2. Make a call to the ModelOp Center API to initiate the monitor

         3. Example:

            Code Block
            { "name": "com.modelop.mlc.definitions.Signals_MODEL_DATA_DRIFT_TEST", "variables": { "MODEL_ID": { "value": "FILL-IN-SNAPSHOT-GUID" } } }

      3. For more details on triggering monitors, visit the article Triggering Metrics Tests.

2. Monitoring Execution: once the scheduler triggers the monitoring job, the relevant model life cycle will initiated the specific monitor, which likely includes:

   1. Preparing the monitoring job with all artifacts necessary to run the job

   2. Creating the monitoring job

   3. Parsing the results into viewable test results

   4. Comparing the results against the thresholds in the decision table

   5. Taking action, which could include creating a notification and/or opening up an incident in JIRA/ServiceNow/etc.

   6. 

...