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

50 results found

  1. Older historical AWS accounts are currently not being searchable in the filters in Cloud Analytics and need to be added manually.
    Could we make historical AWS accounts searchable in filters in Cloud Analytics without manually adding an account?
    This will help to have an overview of all account data from reports.

    We need that for our data integrity as the integrity is false vs AWS cost explorer
    On AWS Cost Explorer, they appear as Redacted

    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

  2. Got this question from a customer I think it is good idea to add chat capabilities somehow for our tickets :slightlysmilingface:

    "Is chat support available? I recently had a great experience with Pressable, the company that hosts our WP site. I had an issue moving a staging site to production with DNS, and the tech was able to help within a few minutes of chatting back and forth. I provided screenshots and a video of what was happening. Could your reps provide a similar experience?"

    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

    3 comments  ·  Other  ·  Admin →
  3. Issue: trying to query large and granular datasets from the Billing data source.
    This is not possible without pagination since the rate limit and payload size limit are insufficient to do it in scale.
    Pagination is already implemented in other endpoints in the analytics API but not in the endpoint that will be most affected by it.

    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

    Declined  ·  0 comments  ·  APIs  ·  Admin →
  4. Bonjour Product Team,

    I am writing to propose a new feature for the DoIT console that I believe would significantly enhance the ability of users to manage and forecast their cloud spend more effectively.

    Issue Summary:
    Currently, while the DoIT console provides valuable insights into daily cloud usage and costs, it lacks a visual representation that compares actual daily usage against projected usage over time. This makes it challenging for users to quickly assess whether their cloud spend is tracking as expected against budget forecasts.

    Desired Outcome:
    I would like to see the implementation of a feature that overlays a…

    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

  5. Allow DoiT Anomaly detection users to create and manage threads for the the actions required to triage and resolve anomalies.

    4 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

    Declined  ·  0 comments  ·  Cost Anomalies  ·  Admin →
  6. Additionally, the DoiT budget report doesn't include taxes, while our AWS budget does. Could it be possible to customize the configuration to include taxes in the budget cost?

    4 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

  7. Request for a flag for legacy clients under "partner-led premium support" who receive Partner Escalation at no cost.

    We need to track "grandfathered" customers who receive PE (Partner Escalation) on GCP without being charged as a result of having a qualifying B2B agreement. A proposed solution involves creating dummy contracts in the console for these customers and adding a flag to identify grandfathered customers.

    Core Problem: Grandfathered customers receiving PE on GCP are not being charged, but there's no clear flag to indicate this, leading to confusion for CRE teams and auditors, as they are dependent on a PLPS contract…

    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

  8. Please make it possible to rename the slack connect channel.

    The slack channel for notifications was automatically created and added to our organization as a shared slack connect channel. The name of this channel is just our company name, so it is really hard to see that this channel is actually related to doit

    Usually our slack connect channels have the name of both companies so you can immediately see which partner organization the channel belongs to

    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

    Declined  ·  1 comment  ·  Other  ·  Admin →
  9. They would like the ability to set default sharing settings for all of their Cloud analytics reports. For instance they would want to have have view-only sharing settings be the default for all user-created custom reports.

    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

  10. Stacked column chart unclear for this type of report. The sums at the top of the columns are unclear. Perhaps we should restrict the type of report you can build if you view your data this way? https://drive.google.com/file/d/1fCEVzsh4DYYjRs_W-r4GXiYTMRetWpMB/view

    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

  11. Customer would like to clean up the GCP Lens by removing the CUD utilization widgets since there is no data to be shown at the moment.

    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

  12. 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

  13. Add the context in the anomaly notification which is like highlighting the usage and cost impact along with the timing when it occurred during the day

    An example: Hey, between 2-3AM on May 5th you had 150M requests which lead to a charge of 110$ and this is why we triggered the anomaly"

    2 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

  14. Please add an option to deliver reports via email in CSV or Excel format to recipients that are not Doit Console users. For example the ability to send the email report to a distribution list or someone that would not want to use the Doit Console. Thanks!

    2 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

  15. Add ability to add/set/paste any email address into Budget's settings, so DoIT customers will not need to enroll this email address as user in DoIT platform and no need to manage permissions etc. Just please make the same as in AWS Bugdets, where any email can be specified and thats all.

    2 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

  16. This is an idea for all lenses

    Add a "Contact an <Lens> Expert" button to all Lenses dashboards that would automatically open a CRE ticket with all relevant context.

    For example the GKE Lens should have a "Contact a GKE Expert)
    This way customers have better experience and quick access to our CRE team

    2 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

    Declined  ·  0 comments  ·  Other  ·  Admin →
  17. It will be very useful for customers and internal teams (CRE/TAM/AM) if we add context (link to original insight, screenshot, insight text, potential saving, project names) when a customer clicks the "Contact Support"

    For example: https://console.doit.com/customers/2Gi0e4pPA3wsfJNOOohW/insights/core/gcs-multi-region-storage

    PS:
    We are missing the governance category in UserVoice

    2 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

    Declined  ·  1 comment  ·  Other  ·  Admin →
  18. Today budget alerts are send when the actual percent of the budget is consumed. In order to reduce false alarms, it would be great if there would be an option to only send the alert if the projected cost of the budget will reach 100%.
    For example, if I have a budget alert set to 50% and the predicted spend will not reach 100% this month the alert will not be sent.

    2 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

  19. More Advanced Kubernetes Metrics

    2 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

    0 comments  ·  Kubernetes  ·  Admin →
  20. Hey la Product Team !

    Summary:
    Customers require access to granular and raw AWS cost and usage data that mirrors the level of detail found in AWS's Cost and Usage Report (CUR).
    The current DoiT console and API provide aggregated data, which lacks some of the required keys present in AWS CUR, such as 'usage start' and 'usage end' dates. Additionally, the inability to fetch the full dataset with a single query
    needs to run multiple requests and merging, which is not ideal and raises concerns about potential performance issues.

    Request details:
    Direct access to raw data: provide a method…

    2 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

    0 comments  ·  Other  ·  Admin →
← Previous 1 3
  • Don't see your idea?