Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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 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 anomaly as "Not an anomaly" which will in turn influence the anomaly model to better target true anomalies.

  • Generally applicable but not this one
  • Not applicable, don't show again
  • Too noisy, show more significant spikes
  • Other


Steps to complete:

  1. Navigate to the Anomaly view by clicking "Anomalies" in the top 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 to" option
    1. In the following popup specify the team or individual to take ownership of the possible anomaly and provide any additional details or comments to assist the assignee in resolving the issue.
    2. Select "Assign"





  • No labels