Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Step

A step-by-step guide to responding to anomalies

Perquisites

  • Connect AWS accounts to YotaScale
  • Configure tag management
  • Define tag categories
  • Define dimensions
  • Define perspectives

    Description:

    YotaScale The Yotascale software provides the ability to respond to possible anomalies in one of the following ways:

    • specifying that it is not an anomaly and why
    • specifying that it is an anomaly
    • assigning the possible anomaly to another team or individual for further analysis


    You can provide more detail when marking a possibly possible anomaly as "Not an anomalyAnomaly" which will in turn influence the anomaly model to better target true anomalies.   The following table shows the different responses you can provide when marking something as "Not an Anomaly" and how that response will impact the model and how it behaves:


    ResponseImpact on Model
    Generally applicable but not this oneLeaves the model unchanged and thus scenarios like this will continue to be identified and communicated
    Not applicable, don't show againUpdates the model so it will not identify scenarios like this as anomalies.
    Too noisy, show more significant spikesUpdates the threshold so that the threshold to identify anomalies is increased and thus fewer anomalies will be generated unless they cross the higher threshold.
    Other<WHAT IMPACT TO THE MODEL DOES THIS CHOICE HAVE?>Items marked with "Other" will be reviewed by the YotaScale team to determine the appropriate impact to the model


    Steps to complete:

    1. Navigate to the Anomaly view by clicking "Cost" and then "Anomalies" in the top side navigation.
    2. Select the desired anomaly from the list of anomalies on the left panel.
    3. Click the "Actions" button from the bottom left of the individual anomaly panel.
    4. To resolve the anomaly select either "This is an anomaly" or "This is not an anomaly"
      1. Provide more details in the following popup.
      2. Select "Submit"
    5. To assign the anomaly to another team or individual for further analysis you can select the "Assign toTo" option
      1. In the following popup specify the team or individual to take ownership of the possible anomaly and provide
      2. Provide any additional details or comments to assist the assignee in resolving the issue.
      3. Select "Assign"
    Image Removed

    Image Added

    Filter by label (Content by label)
    showLabelsfalse
    max5
    spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@868
    showSpacefalse
    sortmodified
    reversetrue
    typepage
    cqllabel = "anomaly" and type = "page" and space = "CK"
    labelstags mapping


    Page Properties
    hiddentrue


    Related issues