In this topic, you can find information about creating an Analytics definition from Operations UI.

Procedure

  1. Log in to Operations UI, see the Start Operations UI in VMware Telco Cloud Operations User Guide for more information.
  2. Click Analytics.
  3. To go to Analytics Definition, click Create.
  4. Provide the following details:
    Parameter Description
    Name Provide the definition name.
    Duration Type Provide the duration type as hourly. Default is hourly.
    Note: If you select Duration Type as hourly, then you must wait for approx. one hour to see the data.
    Metrics Select one or more relevant metrics from any one metric type.
    Note: For few metrics types the device types and entity types are pre-populated. Select Other, to add device types and entity types of your choice.
    Device Type Provide the device type as Switch, Router.
    Note: It accepts one or more comma-separated multiple values, First letter must be in the capital: S, R.
    Device Name Provide the name of the device, appears same as in the Smarts topology.
    EntityType Provide the device entity type, such as Port, Interface.
    Note: It accepts one or more comma-separated multiple values, First letter must be in the capital: P, I.
    EntityName Provide the instance name.
  5. To add selection criteria, click Add a criteria.
    Note:
  6. Provide the following details:
    Parameter Description
    Criteria Name Provide the criteria name.
    Device Type Provide the device type as Switch, Router.

    It must match with the Smarts topology device type name.

    Note: It accepts one or more comma-separated multiple values, First letter must be in the capital: S, R.
    Device Name(s) Provide the name of the device (appears same as in the Smarts topology), or regular expression which matches to a single or multiple device names.
    Note: It accepts one or more comma-separated regular expressions.

    For example: The dot* (.*) can be used for all devices name.
    EntityType Provide the device entity type, such as Port, Interface. It must appears same as in the Smarts topology.
    Note: It accepts one or more comma-separated multiple values, First letter must be in the capital: P, I.
    EntityName(s) Provide the complete name (appears same as in the Smarts topology), or regular expression which matches to a single or multiple device names.
    Note: It accepts one or more comma-separated regular expressions.

    For example: The dot* (.*) can be used for all the entities name.
  7. Click Add.
    Anamoly Definition page appears.
  8. Click Advanced Options.
  9. Provide the following details:
    Parameter Description
    Consumption Rate Provide the number of Kafka consumers which are used by the anomaly definition while reading metric data when the definition is deployed.
    Processing Rate Provide the number of Flink parallelism used by the anomaly definition while processing the metric data.
    Validation Factor Defines the lower and upper bound for mean and standard deviation in the following way:
    • Upper bound = mean + n * standard deviation.
    • Lower bound = mean – n * standard deviation
    • Where 1>= n <=3
    EnableLower class Anomaly Acceptable options are:
    • True
    • False
    Note:

    If true, Analytics Service generates the anomaly for the metric value which is less than the lower class boundary(LCB) else ignored.
  10. Click OK.
    Anamoly Definition page appears.
  11. Click Save and Deploy.
    Note: If you want to edit existing definitions, then you need to wait until duration completes (for example, approx. one hour for hourly definition) for edited parameters to take effect.