Create configuration settings rule

Configuration settings affect how Operational Metrics MID Servers process metric data. Configuration settings rules override the default values of these configuration settings, letting you build efficient statistical models for different CI classes.

Before you begin

Role required: evt_mgmt_admin

About this task

A number of configuration settings determine the behavior of Operational Metrics MID Servers. In the base system, these configuration settings are configured with default values, data types, and range of valid values. You cannot directly modify these configuration settings or add new ones. However, you can create a metric configuration rule with new configuration settings that override the default values on the MID Servers.

Then, manually apply these rules to all Operational Metrics MID Servers in a single synchronization operation, or rely on an hourly system job to perform the synchronization.

To take effect, Operational Metrics MID Servers must be synchronized with the updates to the configuration settings rules.

It is valid to have multiple rules for a setting that affect the same CIs, in which case:
  • Rules in which a filter is defined take precedence over a global rule in which no filter has been defined.
  • If multiple rules that affect the same set of CIs have the same priority, then only the latest rule to be defined is applied.
  • If multiple rules with different priorities affect the same set of CIs, then rules with the highest priority are applied.

Procedure

  1. Navigate to Event Management > Operational Metrics > Metric Config Rules.
  2. On the Metric Configuration Rules pane, click New, and fill out the form.
    Table 1. Metric Configuration Rules form
    Field Description
    Name Rule name.
    Order Rule priority within all other rules. Higher numbers represent higher priorities.
    Filter by

    Check box for displaying the Rule field, where you can specify conditions that CIs must meet for the rule to apply. For example, in the choose field list, select Add Related Fields and then add the filter [class][is][Linux Server].

    If clear, the rule applies globally to all CIs in the Metric To CI Mapping [sa_metric_map] table.

  3. Right-click the form title, and click Save.
  4. In the Metric overridden configurations form section click New, fill out the form, and then click Submit.
    Table 2. Metric overridden configurations form
    Field Description
    Name Configuration setting for which to override its value.

    Click the icon to display the list of all configuration settings.

    Click the icon to display the Metric Settings dialog with details such as range of possible values.

    See the following tables (Configuration Settings and Internal Configuration Settings) for details about configuration settings.

    Rule Rule to which the created configuration setting applies.
    Value New value that overrides the default value for the specified configuration setting.
    You can modify the following configuration settings in the Name field.
    Note: The filter specified in the metric configuration rule does not apply to settings with a global scope.
    Table 3. Configuration Settings
    Name and Description Min Max Default Data Type Scope

    anomaly_detection_enabled

    Enable/disable anomaly detection.

    true Boolean CI/Metric

    buffer_anomaly_eviction_size

    Maximum number of anomalies at individual metric level that can be stored in internal buffer before sending them to instance for every CI/Metric pair.

    60 1440 60 Integer Global

    buffer_ci_score_eviction_size

    Maximum number of anomalies at CI level that can be stored in internal buffer before sending them to instance (Currently not being used)

    60 1440 60 Integer Global

    buffer_metric_eviction_size

    Maximum number of metrics that can be stored in internal buffer before sending them to instance for every CI/Metric pair.

    60 1440 60 integer Global

    connection_login_timeout_secs

    Maximum time in seconds to log in to the local database on MID Server.

    30 60 30 integer Global

    corrupt_data_count_threshold

    Minimum number of training points (15-minute averages) required to do any statistical analysis.

    10 100 30 Integer Global

    deprioritize_early_batching_of_anomalous_ci

    Send anomalous CI information immediately or at regular interval.

    false boolean Global

    max_pool_connections_size

    Maximum number of connections for local database pool.

    10 50 25 integer Global

    observation_time_min

    Expected minimum metric observation interval.

    1 1440 1 Integer CI/Metric

    robust_central_percentage

    Percentage of the residual data to compute the residual standard deviation, used for outlier detection. When set to 100 - uses the regular sample standard deviation.

    50 100 90 Double Global

    sparse_gap_fraction_threshold

    If more than this percentage of data is missing and no other class has been identified, classify as SPARSE. Do not attempt to fit a WEEKLY model.

    0 100 50 Double Global

    weekly_model_min_weeks

    Number of weeks for which data must be available in order to consider only a WEEKLY seasonality decomposition.

    2 4 2 Integer Global

    The following configuration settings are for internal usage.

    Table 4. Internal Configuration Settings
    Name and Description Min Max Default Data Type Scope

    anomaly_memory_time_min

    Anomaly score calculator parameter: Memory time for abnormal situation.

    1 600 45 Double CI/Metric

    excess_z_score

    Anomaly score calculator parameter: Minimal anomalousness accumulated for outlier.

    0 3 0.8 Double CI/Metric

    linear_accumulator_threshold

    Decision Tree Threshold: ACCUMULATOR analysis

    0.5 5 1 Double Global

    low_freq_power_threshold

    Decision Tree Threshold: WEEKLY analysis

    0 100 50 Double Global

    low_variability_threshold

    Decision Tree Threshold: TRENDY analysis

    0.0000000001 0.001 0.0001 Double Global

    mid_freq_power_threshold

    Decision Tree Threshold: WEEKLY analysis

    0 100 33 Double Global

    multinomial_count_threshold

    Decision Tree Threshold: MULTINOMIAL analysis

    1 1000 40 Integer Global

    non_zero_diff_threshold

    Decision Tree Threshold: NEAR_CONSTANT analysis

    0 100 5 Double Global

    normal_memory_time_min

    Anomaly score calculator parameter: Memory time for normal situation.

    1 600 1 Double CI/Metric

    normal_probability_ewma_timescale_min

    Anomaly score calculator parameter: Normal assessment time-scale.

    1 600 15 Double CI/Metric

    normal_probability_weight

    Anomaly score calculator parameter: Normal assessment adjustment factor.

    0 1 1 Double CI/Metric

    sigmoid_offset

    Anomaly score calculator parameter: Anomalousness to score conversion.

    0 5 2.1 Double CI/Metric

    sigmoid_weight

    Anomaly score calculator parameter: Anomalousness to score conversion.

    0 5 1.2 Double CI/Metric

    tiny_variability_threshold

    Decision Tree Threshold: NEAR_CONSTANT analysis

    0 0.001 0.0000000001 Double Global

    weekly_peak_hi_limit

    Decision Tree Threshold: WEEKLY analysis.

    7 14 10 Double Global

    weekly_peak_lo_limit

    Decision Tree Threshold: Weekly analysis.

    0.5 7 0.7 Double Global

What to do next

  • Manually apply updates to all Operational Metrics MID Servers by synchronizing configuration settings rules.