Anomaly detection by custom cost tag
We'd like to adjust our anomaly detection to allow selection of custom cost tag.
For instance, our primary cost tag is the Component tag, we now often get SKU-based anomalies that aren’t anomalies when looking at en entire Component tag value.
For instance: We may have a cluster tagged with Component=EMRCluster1 that switched from using one type of EC2 instance to the other. This will show up as an anomaly, but the entire service under this Component tag didn't necessarily have an anomaly.
30-50% of the anomalies we get now are now red herrings because of this.
My questions:
- Would it be possible to include custom tags in anomaly detection
- Would it be possible to do this based on a single cloud only? For instance, we may be using Component as a cost tag in AWS, but cost-0 in GCP.
Bob van Toorn
shared this idea
