9 results found
-
Cost Anomaly Detection - Attribution overview
Hello Team,
currently neither admin users can look up what Attributions have been set for anomaly detection - since it only exists on individual user level within Notification preferences.
It would be useful for admin users to be able to look into what attributions have been set for anomaly detection among the teams, or filter out for cost anomalies of specific attributions within the Anomaly page.
In addition, a filter option could be added to the Attribution page to be able to see which attributions have been clicked in for Anomaly Detection.
Such setting would be crucial for ENT super…
3 votes -
Recommendations based on Anomaly Acknowledgement
DCI should be able to provide recommendations based on Anomaly status in the Anomaly acknowledgement flow.
One such use case is customer acknowledge an anomaly with: "No, this wasn't an anomaly" . System can check notification settings to see if this customer has configuration to suppress the anomalies based on severity or cost threshold. If not, we can make such recommendations to the customer or send notifications so that they can avoid such noise in the future.
3 votes -
BigQuery near real-time cost anomaly for on-demand pricing model
BigQuery provides native views such as INFORMATIONSCHEMA.JOBSBY_ORGANIZATION(https://cloud.google.com/bigquery/docs/information-schema-jobs-by-organization) which contain near real-time metadata about all jobs submitted in the organization or project.
Late last year, I developed a custom solution for a local customer who had a huge cost spike because of an application bug.The idea is to run a Cloud Function job that check the cost of BQ jobs in the past hour (can be user defined). If it exceeds a threadshold (let's say $100), it will write a log to Cloud Logging, which then trigger an alert based on a custom Cloud Logging metric.
…
2 votes -
Multiple cost anomaly alerts if the cost of the anomaly is rising
Customers would like to have the option to receive multiple notifications (cost anomaly notification) on cost anomalies once the initial one is detected, but costs keep rising.
Eg. if the cost anomaly is detected at $1000, the customer would like to see additional notifications sent out if the cost anomaly rises even further (after certain thresholds).1 vote -
Enable real-time cost anomalies for GCP Compute Engine service
Enable real-time cost anomalies for GCP Compute Engine service
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.
6 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.
3 votesWe have already build a way to identify such monthly cost spikes and suppress them. We already support a range of services there already and any other new service can be requested to this list via our support ticket. Here is the information about existing capability https://help.doit.com/docs/governance/cloud-anomalies#spikes-at-the-beginning-of-the-month
-
Add button to review anomaly with CRE (similar to Insights)
We should implement an easy way to open a ticket with a CRE from a cost anomaly page like we do with Insights.
Just like a customer might want to review an Insight with a CRE to go over whether its relevant in the context of their business / strategy, a customer might want to troubleshoot an anomaly with a CRE.
I’d bet there have already been situations where a customer opened a ticket to review a detected anomaly with a CRE.
Could also be a good up-sell for Essentials customers as well, who have anomaly detection but don't have…
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?