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

55 results found

  1. Support integration of Statsig cost, just like databricks, mongo and other 3rd parties.
    Statsig is quite expensive and usage base so cost visibility, monitoring and alerting in a single pane is valuable

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Description
    Introduce a mechanism that allows invoices with active customer disputes or open invoicing / PSS support tickets to be clearly tagged or flagged within DoiT’s billing systems.

    Purpose
    This would give the Collections team immediate visibility that an invoice is already under investigation, enabling them to:

    temporarily pause follow-up or escalation actions, or

    adjust the tone and context of automated collection emails while the issue is unresolved.

    Why this matters
    Without dispute visibility, automated collections may trigger escalation messaging that is misaligned with the actual invoice status, creating unnecessary customer friction and confusion—especially for trusted, long-standing accounts.

    Outcome
    Improved…

    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  ·  Other  ·  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. Today we have real-time anomaly detection - rich with info, great to use and investigate, but get's dumped in to a shared slcak channel with 10s of people
    We tried building the cost alerts, did it with allocations we build in doit for each group, and sending by email to a dedicated slack channel. But we got a lot of false positives with it . we can only decide if it alerts on a % change or actual $ change. we only want to follow % change, but doing it without a min $ threshold to alerts just notified us…

    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)
  4. When Absolute or Percentage Change is selected for a report, an option to apply the Heatmap to only those columns should be available.

    Current behavior applies heatmap logic and color coding to every value present in the table, making it impossible to quickly identify cost drivers or savings by these change values.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. To support the proposed console integration of internal PSS support flow, we'd like the Console's Expert Inquiry to support the following:
    - recognise "visibility" attribute to determine if a product should be hidden from customer in the dropdown list
    - when a Doer is creating a new request under a customer tenant, a pop up dialog should be presented for the Doer to select whether the ticket will be private or viewable by the customer

    Please refer to the following requirement document for more details, including tags, assignee and UI mock-ups: https://doitintl.atlassian.net/wiki/spaces/fde/pages/1623883778/DoiT+Console+PSS+Internal+Request+Flow+Requirements

    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

    In Backlog  ·  0 comments  ·  Other  ·  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. Current behavior
    In Cloud Analytics reports, when using the filter or group-by control on resource ID, the selection dialog only lists up to 5000 distinct resource values. As a result, specific resource IDs that are visible in the report table (may not appear in the selection dialog and cannot be filtered or grouped on, even though they are present in the dataset.

    Impact
    This prevents customers from reliably drilling down to specific resources at scale, blocking important FinOps and DevOps optimization workflows. Customers are forced to export data to external tools to achieve the required level of granularity, which creates…

    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)
  7. The AWS assets page currently shows all accounts but there is no way of knowing if the account has been closed. We should add the AWS status/state of the account and not show closed accounts in areas like CloudFlow or CloudConnect.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Please reinstate and expand DoIT's Flexsave for RDS/Databases option. AWS's recent announcement of Database Savings Plans should help DoIT mitigate the risks of unused capacity and make Flexsave for RDS/Databases feasible. Ideally, Flexsave for RDS/Databases should work similarly to Flexsave for Compute.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Please reinstate and expand DoIT's Flexsave for RDS/Databases option. AWS's recent announcement of Database Savings Plans should greatly help DoIT mitigate the risks of unused capacity.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Customers with many AWS accounts need a fully programmatic way to complete the DoiT “Link account” + Kubernetes core enablement flow, especially during the EKS Intelligence → Kubernetes Intelligence migration. Today this must be done via the Console/CloudFormation flow and cannot be completed end‑to‑end via public APIs, creating manual work and coordination overhead for multi‑account orgs. The current Console flow relies on CloudFormation plus a backend webhook/validation step to register the role and mark features as enabled; this callback is not exposed publicly, so adding IAM permissions with Terraform alone doesn’t flip the feature state. As a result, there is…

    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  ·  APIs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. On the insights detail pages, it would be nice to have a column for the account alias in the table. So I can see [Redacted Account Name] instead of just [Redacted Account Number].

    6 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  ·  Insights  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for this idea! We've already had this in mind and this feedback helps us prioritize it – we will implement this within the next few weeks.

  12. Currently, all admins bypass SSO completely, which is a security gap since those sensitive accounts are the ones we need to be secured the most. I understand the use case for having a breakglass account, but making all admins bypass it with no way to enforce it defeats the purpose of having SSO enabled to begin with.

    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)
  13. Currently, when searching for an AWS account or GCP project, the result is just a static link to the asset details page. To check costs or settings, I have to click the result, wait for the page to load, and then navigate through menus again.

    Please make the search results more dynamic by adding "Quick Actions" directly in the dropdown. When I search for an asset ID, I would like to see buttons to:

    Open a Cost Report filtered specifically for that account.

    Go directly to the Cloud Flow or Attribution settings for that account.

    This would significantly reduce the…

    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)
  14. Allow for invoices to have "Invoice period" column which you can sort by. When you reissue an invoice that information does not exist or gets lost. All invoices should have (mandatory, by law) an explicit period listed for which the invoice is charged.

    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)
  15. Add a button next to invoice to more easily raise an issue around that invoice.

    Should help with speeding up payments.

    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)
    • Get a daily/weekly email with a combined summary of changes since the prior week

    • Use the DoIt API to get a list of changes/history that is currently displayed in the UI

    • Get notifications of changes, such as a slack webhook that fires any time a new snapshot/change is created

    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)
  16. Is there any chance if we can test on the GCP Marketplace if we can offer DoiT's DCI offering as an all upfront payment?

    A customer would be very keen to do this and we have the contractual mechanism on this side.

    Some Google teams have suggested it wouldn't be possible but Sebastian based on what he could see, seemed to think it would be possible

    Per House BP:
    Assuming all upfront means annual payment, I see that it is possible to create a private offer for such. However our backend doesn't support annual, so some refinement and development would…

    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)

    Due to previously planned work for the remainder of the year and into January, this work is slated for Q1 / early Q2 of 2026.

  17. There are cases when customers need to jump to previous months in their Budgets dashboard so they can check the percentage or any other data related to their budget. At the moment, only current month is shown on the dashboard. Please allow for an option to easily jump to previous months for quick inspection.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Bigquery Lens should have reports going back more than 30 days. I believe at least 3 months would be sufficient to see usage changes and activity.

    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)
  19. Can we have an additional Invoice API to get the actual invoice PDF files?

    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  ·  APIs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Due to previously planned work for the remainder of the year and into January, this work is slated for Q1 / early Q2 of 2026.

← Previous 1 3
  • Don't see your idea?