Skip to content

DoiT Cloud Intelligence

Welcome to the DoiT Cloud Intelligence Customer Feedback Portal.

Please help us improve our product by providing feedback or ideas for new features.  Your input helps us improve our offerings and we pride ourselves on responding and reacting to ideas across our customer base.  When leaving an idea, please be as specific as possible about the problem you are encountering and what your ideal solution looks like.  

Thank you in advance for your comments
If you have any questions please file a ticket in our Console

DoiT Cloud Intelligence

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

6 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Cost Anomalies  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Real time cost anomalies!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Cost Anomalies  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?