Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Scheduled jobs installed with Operational Intelligence

Log in to subscribe to topics and get notified when content changes.

Scheduled jobs installed with Operational Intelligence

Operational Intelligence adds the following scheduled jobs.

Name Description
Operational Intelligence – Metric Learner job Runs daily and builds the statistical models used for anomaly detection.
Operational Intelligence – Purge old metric schemas and anomaly scores Cleans up the sa_metric_anomaly_score and the sa_metric_schema_definition tables.
Operational Intelligence – Sync metric schema to mid Synchronizing the metric schema table sa_metric_schema_definition.
Operational Intelligence – Sync tables with mid Synchronizing tables.
Operational Intelligence – Table cleanup Cleaning up tables related to various deletion operations.
Operational Intelligence – Observation Interval Learner job Calculates the observation interval using collected data points for all CI/metric pairs.
Operational Intelligence – Process Stale Anomaly Score – Daily Daily job that cleans stale CI/metric anomaly scores, for a specified window of time, in the Metric Anomaly Score [sa_metric_anomaly_score] table.

Uses the properties sa_metric.anomaly_score_stale_interval_in_days and sa_metric.anomaly_score_next_stale_interval_in_days to calculate the window of time for cleaning.

Operational Intelligence – Sync CI Anomaly Scores Keeps anomaly scores up to date with any deletion of metrics.
Operational Intelligence – Metric configuration job Synchronizes metric configurations from the instance to all Operational Intelligence MID Servers.
Operational Intelligence — Validate MID Distributed cluster
  1. Checks the status of the cluster node.

    If status is Started and the status of the Operational Intelligence extension is not any of Started/Starting/Warning [warning with specific errors], then the job changes the status of the cluster node to Stopped.

    This happens when MID Server stops unexpectedly without notifying the instance that it is stopping.

  2. Checks the status of all cluster nodes on all MID Servers in the cluster.
    • If the status of all nodes is Stopped and the status of the cluster itself is Running, then the job changes the status of the cluster to Stopped.
    • If the status of the cluster is Stopped but there are MID Servers with a cluster node that is running, then the job changes the status of the cluster to Started.
  3. Checks the number of Cluster Leaders: If two are detected, then the job stops the entire cluster.

    This happens when MID Servers are not able to connect with other members of the cluster and form multiple sub-clusters.