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 possible anomaly as "Not an Anomaly" 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:
Response
Impact on Model
Generally applicable but not this one
Leaves the model unchanged and thus scenarios like this will continue to be identified and communicated
Not applicable, don't show again
Updates the model so it will not identify scenarios like this as anomalies
Too noisy, show more significant spikes
Updates 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
Items marked with "Other" will be reviewed by the YotaScale team to determine the appropriate impact to the model
Steps to complete:
Navigate to the Anomaly view by clicking "Cost" and then "Anomalies" in the side navigation
Select the desired anomaly from the list of anomalies on the left panel
Click the "Actions" button from the bottom left of the individual anomaly panel
To resolve the anomaly select either "This is an anomaly" or "This is not an anomaly"
Provide more details in the following popup
Select "Submit"
To assign the anomaly to another team or individual for further analysis you can select the "Assign To" option
In the following popup specify the team or individual to take ownership of the possible anomaly
Provide any additional details or comments to assist the assignee in resolving the issue