1. REST API for Unified Assurance Core
  2. Tasks
  3. Metrics
  4. Abnormal Profiles

Get Abnormal Profiles

get

/api/metric/AbnormalProfiles

Gets the abnormal profiles that match the specified query parameters. Abnormal profiles are used by abnormal thresholds and the Metric Abnormal Threshold Engine. If no parameters are specified, all abnormal profiles are returned.

Request

Query Parameters
  • The fields to filter the results by. You cannot filter by fields that contain a state.
    This parameter's value uses the following JSON format:
    { "property": "property", "value": "propertyValue", "operator": "operator", "conjunction": "conjunction" }
    If you use multiple JSON objects to combine filters, for example, to filter by several different device names, you cannot combine OR and AND conjunctions. The conjunction used for the last object applies to the entire list.
    • Default Value: OR
      Allowed Values: [ "AND", "OR" ]
      The conjunction between filters.
      Example: AND
    • Default Value: LIKE
      Allowed Values: [ "eq", "ne", "gte", "gt", "lte", "lt", "LIKE", "NOT LIKE", "re", "not re", "NOT IN" ]
      The filter operation to use.
      Example: eq
    • The name of the field to filter on.
      Example: name
    • The value of the field to filter on.
      Example: test
  • The number of records to limit results by. If you do not also set the start parameter, records start at 0.
    Example:
    100
  • The field and direction to sort results by. You cannot sort by fields that contain a state.
    This parameters value uses the following JSON format: { "property": "property", "direction": "direction" }
    Example:
    [
    {
        "property":"Name",
        "direction":"ASC"
    },
    {
        "property":"Value",
        "direction":"DESC"
    }
]
  • The page of results to start from. This parameter is ignored if you do not also set the limit parameter.
    Default Value: 0
    Example:
    1

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : schema
Match All
Show Source
Nested Schema : SuccessfulGetOperation
Type: object
The response body for a successful get operation.
Show Source
Nested Schema : type
Type: object
Show Source
Nested Schema : data
Type: array
Show Source
Nested Schema : metricAbnormalProfilesRead
Type: object
Show Source
  • Abnormal Profile ID
    Example: 1
  • Name of abnormal profile
    Example: Default Abnormal Profile
  • The degree to which the confidence bands smooth a weighted average (more weight being given to recent observations, less to older observations). Values are from >0 to 1. The closer to 1 the Alpha value becomes, the closer the predicted value will be to the weighted average of the last n observations.
    Example: 0.999497
  • The degree to which the smoothing function considers the slope (amount of increase or decrease) of the weighted average of 2 adjacent data points. Values are from >0 to 1. The closer to 1 the Beta value gets, the more the Algorithm will consider the slope of the previous (n-1) data point to the current data point (n) when predicting the next data point (n+1).
    Example: 0.00224
  • Scaling factor, used to influence the width of the confidence bands generated by the Algorithm. Values are between 2 and 3.
    Example: 3
  • Epsilon scaling. Values are >0 to 1.
    Example: 0.492391
  • Used with Window Length by the Abnormal Thresholding Engine to determine whether to generate a threshold violation event. If Violation Threshold data points fall outside the confidence band within a Window Length number of points, then the data points are considered "abnormal" and an event will be generated.
    Example: 3
  • The degree to which the smoothing function considers seasonal data when forecasting a data point. Values are >0 to 1. The closer to 1 Gamma gets, the more the Algorithm will weight seasonal patterns when forecasting expected values.
    Example: 0.487092
  • Used with Violation Threshold by the Abnormal Thresholding Engine to determine whether to generate a threshold violation event. If Violation Threshold data points fall outside the confidence band within a Window Length number of points, then the data points are considered "abnormal" and an event will be generated. Values are between 0 and 28.
    Example: 5

Default Response

Failed operation
Body ()
Root Schema : schema
Type: object
Show Source
Nested Schema : errors
Type: array
The list of errors reported. Validation errors will be keyed by record field.
Show Source
Nested Schema : items
Type: object
An error.
Back to Top