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

56 results found

  1. Can we have an API method to get a ticket by ticket ID with all the metadata and comments?

    For internal DoiT usage, can we have this working just with a ticket # since they are unique across customers? For example:
    curl --request GET \
    --url 'https://api.doit.com/support/v1/tickets/id' \
    --header 'Authorization: Bearer API_KEY' \
    --header 'accept: application/json'

    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  ·  1 comment  ·  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)
  2. Description:
    Users would like the ability to view aggregated cost data for resource groups in Cloud Diagrams, not just individual resources. For example, clicking on an ECS cluster should display the total grouped cost of all its sub-resources.

    Use Case:
    This would help teams quickly assess the total cost impact of a service or component (like an ECS cluster or auto-scaling group) without manually summing individual resource costs.

    Requested By:
    Flavio Alberti (THRON)

    Impact:
    Improves financial visibility and supports more accurate cost analysis directly from the diagram view.

    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)
  3. The customer—specifically the person responsible for FinOps—would like the ability to compare specific time periods while excluding everything in between. For example, they want to compare June 2024 vs. June 2025, or Q2 2024 vs. Q2 2025, without including the months in between.

    This is similar to the “this period vs. last month” view we currently offer, but they’re looking for a customizable comparison between non-consecutive timeframes—essentially, a way to isolate and break down specific months or quarters year over year.

    MoM, QoQ, or YoY

    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)
  4. Have direct flows for app data flows based on tags/names

    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)
  5. Due to security scans and their results, customers may require to update the S3 policies for the S3 buckets that DoiT manages and uses for EKS Lens.

    Please review whether ths following policy can be implemented for all customers (attached)

    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)
  6. Enable integration with AWS CloudTrail to fetch near real-time infrastructure change logs. Additionally, by linking each change event to the specific IAM role or user that made the modification, teams gain clearer accountability and traceability.

    User Benefit:
    * Gain near real-time visibility into infrastructure changes
    * Enhance team accountability by identifying which IAM role/user made each change
    * Keep precise audit log that's easy to read and won't miss small transient changes. This will help with compliance and internal governance for enterprise customers

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Ability to embed Cloud Diagrams as a widget within relevant features like CloudFlow, Anomalies and Insights. This would allow customers to visualize infrastructure contextually without switching screens or losing focus on the task at hand.

    The widget should support filtering to only show relevant parts of the diagram, such as affected resources in an anomaly, or impacted resources in CloudFlow, helping users quickly understand the context, relationships, and impact.

    This functionality will improve user experience by:
    * Enhancing cross-feature integration and context sharing
    * Reducing cognitive load during troubleshooting or investigations
    * Improving collaboration and visibility by providing infrastructure context…

    7 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. There is a request to add an estimated 'bill without DoiT' directly into the Invoice Explainer. Currently, customers struggle to see the value we provide because they can only view the AWS bill to DoiT and the DoiT bill to them. We also need to know how many are using the console reporting to see their savings. This lack of transparency on the invoice creates confusion, particularly around renewals, leading to the impression of overpayment and potentially jeopardizing customer trust. By including a 'bill without DoiT' comparison, we can clearly demonstrate the savings and prevent this recurring issue, ultimately improving…

    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)
  9. Allow users to customize the import settings during Cloud Account onboarding.

    Users should be able to filter resources based on:
    * Region (e.g., import only us-west-2)
    * VPC (e.g., focus on specific VPCs for diagram clarity)
    * Tags or Allocations (e.g., import only resources tagged with Environment=Production or belonging to a specific team)
    * Resource Name Patterns (Regex Support) (e.g., import only resources with names matching .-prod-.)

    User Value:
This feature will provide more control over what gets imported into Cloud Diagrams, helping reduce visual clutter and improving relevance, especially for large environments. It also supports security and scoping…

    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)
  10. Integrating data from EKS agents into Cloud Diagrams. This enhancement would enable us to display private EKS clusters that are not visible through standard AWS APIs, and allow us to show performance, health, and configuration data directly within the diagram view.

    Benefits:
    * Improved visibility into private and internal EKS clusters, which are currently not represented in diagrams
    * Real-time performance metrics (CPU, memory, pod utilization, etc.) can help platform teams identify issues more quickly
    * Health status indicators for clusters, nodes, and workloads directly in the diagram improve troubleshooting and monitoring workflows
    * Enhanced context for security and cost…

    13 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)
  11. If there is a gradual increase in cost on daly basis such increase will not be considered as an anomaly as the data would look like an expected increase however if we compare this cost over month to month the increase can be significant. Hence it is worth generating anomalies on such cost spikes on Monthly granularity.

    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)
  12. Today, once we notify for an anomaly, we do not notify again if an anomaly is active but the cost has spiked by X times, lets say twice. As a result, customer who ignored the anomaly in first place based on its cost missed the opportunity to react when the cost spike became more considerable.

    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

    In Backlog  ·  1 comment  ·  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)
  13. Customers with shared resource accounts that need to be split amongst business units (or some other allocation) need to create allocations for those accounts and then do cost splitting. This can get tedious for large customers.

    Instead of requiring 100% coverage of allocations in order to do cost splitting, allow customers when using an allocation to split by account to re-allocate the costs for shared resources.

    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)
  14. Add exchange rate pricing to billing column in reporting

    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)
  15. When the Snowflake Lens is first connected, there is nothing on the screen that would designate it's processing. Similar to AWS Lens, EKS Lens, Pulse, etc - it would be extremely helpful to provide visualization of some sort that billing data is getting ingested.

    Here's link showing the lack of information on end user's side: https://share.zight.com/rRuKk9ge

    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. Can we add Cloud Diagrams to the quick links in the DCI search?

    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)
  17. We should provide “Insight” on untagged BigQuery spend. Something like “xx% of your BigQuery queries is not labeled/tagged

    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)
  18. Currently, customers using the Doit console to purchase Microsoft 365 subscriptions or licenses are limited to monthly billing. Annual subscriptions require direct engagement with our sales team. This necessitates the creation of annual contracts, often for a small number of licenses, which consumes significant time in managing Ironclad and Salesforce for minimal revenue.

    To improve efficiency, I propose enabling customers to purchase a limited number of Microsoft 365 licenses (e.g., fewer than 50) through our console with both monthly and annual billing options. This would significantly reduce the administrative overhead associated with low-volume annual contracts.

    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. I noted that currently, Cloud Diagrams CFN stack needs to be deployed to any account, and does not seem to leverage the org account's Resource Explorer access on all resources. I would think access to that would allow for gathering the info needed to generate a diagram, but perhaps the data are incomplete?

    But if that's possible, then it could also become a standard onboarding product as well (optional) for customers.

    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)
  20. Expand DoiT’s real-time anomaly detection capabilities to cover additional AWS services, such as Amazon ECS.

    Use Case:
    In the event of a container being compromised—whether due to a security breach or a misconfiguration—the resulting spike in resource consumption can quickly lead to unexpected charges, potentially costing hundreds or even thousands of dollars before the issue is detected.

    By leveraging real-time anomaly detection, these incidents can be identified proactively using your usage logs, often before they appear in standard cloud billing or usage reports, which typically have a delay of 24 to 48 hours. This early detection helps minimize financial impact…

    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  ·  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)
  • Don't see your idea?