6 results found
-
Stop Cost Anomaly False Positives
The customer reports that there is something wrong with the cost anomaly tool, and that they are receiving false alarms every day.
Because of this and the alert fatigue they plan to disregard Cost Anomalies moving forward, despite getting a lot of value from it in the past.5 votes -
Proposal to Adjust Monthly Recurring Charges Alerts: Shift from Cost Anomalies to Monthly Cost Awareness
Customers often receive monthly subscriptions or charges for cloud services on the 1st of each month, such as Cognito, IAM Analyzer, or backups. These charges frequently trigger cost anomaly alerts, causing unnecessary panic and notifications in Slack channels or emails. Instead of treating these as cost anomalies, it would be more appropriate to classify them as 'Monthly Cost Awareness' or 'Monthly Charges by SKU,' as they are expected expenses rather than anomalies.
1 vote -
Some notes writing capabilties
Right now, once the Cost anomalies get generated and assuming that is been investigated and understood the “why” that happen.
Now Engineer from the customer wants to put some notes or annotate the reason for that particular cost so that other people in the organisation won’t ask the same questions, and have the context when that alert generated again.
Can we add some capabilities to add Notes probably in the Navigator so that can be refer in the future.
1 vote -
Anomaly Acknowledgement flow
Customer Problem: Today we do not have any information about the below data:
- Customers do not have the ability to filter the active anomalies that they have treated/seen vs where they still have to take an action .
How many customers are actually performing any action for the anomalies we generate for them,
Identifying the false positive and gather customers feedback so that we can improve the product
1 vote -
Export List of Cost Anomalies
Customer would like to be able to easily export a list of all Cost Anomalies. Right now the only way to get a $$ total of them is to add them up manually.
1 vote -
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:
-…1 vote
- Don't see your idea?