Skip to main content

Running an Analysis

Select Run Analysis on the Monitoring tab or the drift dashboard. The analysis compares the active version's production predictions from the last 7 days with its active baseline.

While it runs, the page shows Analyzing with what it is doing. If it cannot produce a result, it says why; for example, the version has no production predictions in the window, or its inputs are not recorded. The drift list shows these models as Could not run with the reason.

An analysis window needs enough predictions to mean anything: with a handful of values, every feature reads as drifted. A window with fewer predictions (with recorded inputs) than the model's Minimum predictions per analysis (30 by default) is not scored, and the analysis says so.

Scheduled analysis​

On the drift dashboard's Algorithms tab, under Automated schedule:

  • Enable scheduled analysis;
  • choose the Frequency: hourly, daily or weekly;
  • set the Analysis window (days) each run looks back over;
  • select Save Configuration.

The first scheduled run happens shortly after you enable it. Building a baseline with Analyze drift daily turns on a daily schedule the same way; the baseline's own first analysis counts as that day's run. If the schedule cannot start an analysis (for example, the version has no baseline), the Algorithms tab says why.

Notifications​

When an analysis finds drift (status Warning or Alert), the model's owner is notified in Strongly (the notification bell and push). On the drift dashboard's Algorithms tab, under Notifications, you can also:

  • turn on Email to email the Email recipients (separated by commas; leave empty to email the model's owner);
  • set a Slack incoming webhook to post a message to a Slack channel.

Select Save Configuration. An address that is not an email address, or a webhook pointing at localhost, an internal host or a private network address, is refused. Each result is announced once, and an analysis that could not run sends no notification (the dashboard says why it could not run). Email needs the platform's mail server to be configured; when it is not, the result records that the email could not be sent.