Skip to content

Thresholds

Thresholds is a standard configuration interface for adding, editing, and removing thresholds in Assure1.

Refer to the Standard Configuration Interface guide for details on interacting with the grid and form.

This user interface calls REST methods from api/metric/thresholds.

The UI path for this interface is Configuration -> Metrics -> Thresholds -> Thresholds.

Form Fields

  • Name - The name of the threshold.

  • Type - The threshold type.

  • Abnormal Profile - If Type is set to "Abnormal", the abnormal profile that will be used for the confidence band calculation and threshold.

  • Measurement - The metric type the threshold will check.

  • Metric Field - The data type the threshold will check. Must be set to one of the following:

    • availability

    • utilization

    • value

  • Time Range - Unless Type is set to "Abnormal", the period of time where data points will be retrieved and evaluated. This must be a combination of a numerical value and a duration, which must be set to one of the following:

    • s for seconds

    • m for minutes

    • h for hours

    • d for days

  • Forecast - If Type is set to "Trend Prediction", how far out to predict when the metric value will breach the threshold, e.g. "Notify when Disk will be 90% in 6 months or less". This must be a combination of a numerical value and a duration, which must be set to one of the following:

    • s for seconds

    • m for minutes

    • h for hours

    • d for days

  • Frequency - If Type is set to "Standard" and CheckLocation is set to "Threshold Engine", how often the threshold is being checked. This should not be less than the PollTime. This must be a combination of a numerical value and a duration, which must be set to one of the following:

    • s for seconds

    • m for minutes

    • h for hours

    • d for days

  • Offset - If Type is set to "Standard" and CheckLocation is set to "Threshold Engine", what offset to apply to the time range, e.g "Go back 5 minutes when checking the threshold to ensure most recent poll data is considered". 0 minutes means no offset. This must be a combination of a numerical value and a duration, which must be set to one of the following:

    • s for seconds

    • m for minutes

    • h for hours

    • d for days

  • Function - If Type is set to "Standard", what function to apply when calculating if a threshold is breached. Expands from previous Mean. The following options are available:

    • Mean is used when the average of the values should be considered.

    • Minimum can be used to ensure the data never falls below a certain value.

    • Maximum is a good way to ensure all data is below a certain value.

    • 95th Percentile makes sense for scenarios where high outliers / odd values are expected to occur infrequent but are not to be counted. It basically says "most data points shall be under a certain value".

    • Count is a way to ensure there is no missing data, so if a data point is expected every minute checking a TimeRange of x minutes every y minutes shows after the latest y minutes if data is missing.

  • Warning Operator - Unless Type is set to "Abnormal", threshold comparison operator.

  • Warning Value - Unless Type is set to "Abnormal", value to compare against.

  • Warning Severity - Severity for the event when shown on the event list.

  • Critical Operator - Unless Type is set to "Abnormal", threshold comparison operator.

  • Critical Value - Unless Type is set to "Abnormal", value to compare against.

  • Critical Severity - Unless Type is set to "Abnormal", severity for the event when shown on the event list.

  • Message - Message for the event when shown on the event list. This is usually put into the "Summary" field.

  • Check Location - Specifies whether application will handle checking the threshold or the threshold engine (Standard thresholds only).

  • Status - Threshold status.

Meta

Default Thresholds

  • CPU High

  • CPU Trend

  • Device Down

  • Device No Longer Polled

  • Disk High

  • Disk Trend

  • Disk Trend Prediction

  • Fan Down

  • Fan Unavailable

  • Inbound Bandwidth Abnormal

  • Inbound Bandwidth High

  • Inbound Bandwidth Trend

  • Inbound Bandwidth Unused

  • Inbound Bandwith Trend Prediction

  • Inbound Discards High

  • Inbound Errors High

  • Interface Down

  • Latency High

  • Link Down

  • Link Jitter High

  • Link Latency High

  • Link MOS High

  • Link Packet Loss High

  • Link RFactor High

  • Memory High

  • Memory Trend Prediction

  • Outbound Bandwidth Abnormal

  • Outbound Bandwidth High

  • Outbound Bandwidth Trend

  • Outbound Bandwidth Unused

  • Outbound Bandwith Trend Prediction

  • Outbound Discards High

  • Outbound Errors High

  • Packet Loss High

  • Ping Jitter High

  • Ping Jitter Utilization High

  • Poll Duration Trend Prediction

  • Process Down

  • Response Time High

  • Temperature High

  • Temperature Unavailable

  • Transaction Down