5 results found

1. Slack Connect Channel Name

   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

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

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

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

5. 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 →