10 results found

1. Add context to DoiT Insights when using the "Contact Support" button

   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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →

2. Cost Anomaly Detection - Exclude Attribution from algorithm

   Hello Team,

   Customers currently can add an Attribution for Anomaly Detection to monitor abnormal spend behavior on a specific segment of their business. A customer just surfaced the need of excluding a specific Attribution from the Anomaly Detection logic due to the nature of that segment of the business, where they are expecting those anomalies to happen. The desired outcome would be that all infrastructure linked to that Attribution would not be flowing into the Cost Anomaly algorithm, hence the anomalies would not get surfaced as per customer preference.

   Do you think this would be possible?

   Kind Regards,

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cost Anomalies  ·  Delete…  ·  Admin →
   Declined  ·  AdminSebastian Caparroz (Admin, DoiT) responded

   Can be done currently by disabling default anomalies and monitoring for anomalies an attribution that excludes the desired selection.

3. Support for Attribution Templates

   We use DoiT to create Attributions to allow us to view client-specific costs. Overall this works well for us.

   One improvement would be if we could configure Attribution "templates" containing specific fields even if the data doesn't exist yet. For example, only a subset of our customers are using Dataproc and so only that subset of customer data is labelled in the billing data. When I create a new Attribution I must exclude our dataproc label for the customer if their data doesn't exist yet. Eventually, when the customer migrates to Dataproc, their Attribution will be incorrectly missing the data from DataProc until I remember to add the missing label.

   I'd love a way to create an Attribution Template where I can configure the labels (and values) in advance based on future values. Then once the data becomes available the Attribution would automatically pick it up.

   Thanks.

   We use DoiT to create Attributions to allow us to view client-specific costs. Overall this works well for us.

   One improvement would be if we could configure Attribution "templates" containing specific fields even if the data doesn't exist yet. For example, only a subset of our customers are using Dataproc and so only that subset of customer data is labelled in the billing data. When I create a new Attribution I must exclude our dataproc label for the customer if their data doesn't exist yet. Eventually, when the customer migrates to Dataproc, their Attribution will be incorrectly missing the data… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  0 comments  ·  Attributions & Attribution Groups  ·  Delete…  ·  Admin →

4. Advanced GKE Metrics

   More Advanced Kubernetes Metrics

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Kubernetes  ·  Delete…  ·  Admin →
   Declined  ·  AdminRyan Sosin (Principal Product Manager, DoiT) responded

   Not enough information

5. Display reports in local time zone

   When report graphs are plotted against time, allow the time zone to be set.

   I recently investigated a cost increase due to database activity. The cost anomaly graph and report were shown in UTC. I understand this is the time zone AWS reports the costings, but it would be very helpful for me to align the spike in usage with some event at work, without having to convert the time zones.

   This will not make much different for daily/monthly graphs, but I was looking at an hourly graph, where having the times displayed in local time zone would be very helpful.

   When report graphs are plotted against time, allow the time zone to be set.

   I recently investigated a cost increase due to database activity. The cost anomaly graph and report were shown in UTC. I understand this is the time zone AWS reports the costings, but it would be very helpful for me to align the spike in usage with some event at work, without having to convert the time zones.

   This will not make much different for daily/monthly graphs, but I was looking at an hourly graph, where having the times displayed in local time zone would be very… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Analytics & Reports  ·  Delete…  ·  Admin →
   Declined  ·  AdminRyan Sosin (Principal Product Manager, DoiT) responded

   Following the same pattern that the public cloud providers use.

6. Region filter on the cloud incidents page

   Customers will generally be interested in cloud incidents specific to the regions they use. It would be helpful if there was an option to include a region-specific filter on the cloud incidents page. This would help to provide more meaningful data.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   Declined  ·  AdminRyan Sosin (Principal Product Manager, DoiT) responded

   Cloud incidents are already filtered based on customer regions.

7. Enhanced Access to Granular AWS Cost and Usage Data Summary

   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 for customers to directly access the most granular and raw dataset available within DoiT, similar to AWS CUR, without the need for aggregation or data processing that removes essential keys.

   Single query data retrieval: Enable the retrieval of the full dataset in a single query to avoid the need for multiple requests and data merging.

   Dimension and metric selection: Allow customers to select specific dimensions and metrics for download, as per their internal reporting and analytical tool requirements.

   Performance considerations: Ensure that the method for accessing and downloading data is optimised for performance to handle large datasets without significant delays or issues.

   Use Case:
   The feature would be particularly beneficial for customers like Criteo, who have transitioned to being billed by DoiT instead of AWS directly and are implementing FinOps practices that require detailed data analysis.

   Impact:
   This feature would empower customers with precise data for cost management and optimisation, aligning with advanced FinOps practices and internal BI tool integration.

   Merci :)

   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… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   Declined  ·  AdminGaurav Juneja (Senior Product Manager, DoiT) responded

   Discussed with the customers, this is no longer a gap and current data from DoiT is enough for their analytics.

8. Restrict Creation of Usage Alert to SKU Level
   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  0 comments  ·  Budgets & Alerts  ·  Delete…  ·  Admin →

9. Flexsave for Elasticache and Opensearch
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Declined  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →

10. Projection Line vs. Daily Usage Bar in DoIT Console

    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 projection line on top of the existing daily usage bar chart within the DoIT console. This feature should provide the following capabilities:

    • A projection line that extends across the daily usage bar chart, indicating expected spend for the current period based on historical data or user defined forecasts.
    • The ability to compare actual daily usage against the projected spend visually, enabling users to identify trends or deviations from expected patterns.
    • Customisable projection settings that allow users to set the basis for the projection, such as average historical usage, growth rate or %, or a fixed budget amount. Interactive elements such as hover details that provide additional context on specific data points, both for actual usage and projected figures.

    Suggested Solutions:
    - Enhance the current daily usage bar chart with an additional line graph that represents the projected spend.
    - Allow users to input or select the parameters for the projection, including the time frame for historical data consideration and the desired projection model - it could could be linear, polynomial...
    - Provide options for visual customisation, such as line color, to distinguish the projection line from the actual usage bars clearly.

    Impact:
    The addition of a projection line vs daily usage bar would empower users to make more informed decisions regarding their cloud spend. It would facilitate early detection of potential overages or underutilisation (why not adding the ramp plan?), enabling proactive adjustments to cloud resources and budget allocations. This feature would be particularly beneficial for CFOs, financial analysts, FinOps personas and cloud cost management teams who are responsible for budgeting and forecasting.

    Merci :)

    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… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Cloud Analytics & Reports  ·  Delete…  ·  Admin →
    Declined  ·  AdminRyan Sosin (Principal Product Manager, DoiT) responded

    This was removed from the product because it generated confusion for users.