24 results found
-
Make historical AWS accounts visible in Cloud Analytics
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 Redacted5 votes -
Report subscription in slack shows differently to actual report
The report which is sent to Slack should be the same format as the report that I have setup in the portal. I have a report which is a table and when its sent to slack it turns into a bar chart. This is not how I would expect the report to be displayed. It should show me what I setup in the portal
1 voteThe image in Slack is meant to be a preview. Sending large quantities of raw data to Slack is unpredictable and a security risk.
-
Make historical AWS accounts visible in Cloud Analytics
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.1 vote -
Add support for any email address in Budgets
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 votesThis is part of our overall security strategy to keep our platform and your data secure. Unfortunately, we will not allow content to be shared outside of our user management controls.
-
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 -
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 UserVoice2 votes -
Console should retain login for longer
When I go to the Console, it requires that I log in again. I think it times out after a day. Other apps, including secure ones, allow much more time before timing out.
Some apps are transactional, so you log in occasionally to perform specific tasks. But if we want to have a true "console" it needs to be convenient and available.
1 vote -
Removing the "noise" of Flexsave accounts under the "Project/Account ID" filter in reports
Customers are seeing hundreds of Flexsave accounts when they are trying to filter out certain accounts under the "Project/Account ID" selection, is there a way that we could put a button on the bottom of the window that just "removes all DoiT Flexsave accounts" so that customers can just views their accounts instead of all 269 accounts (ex. Roscommon Analytics)
1 voteFiltering all Flexsave accounts can be done using the Project/Account Name dimension.
-
Include tax & support charges in forecast
Make the forecast on the pulse and lens dashboards include tax and support.
I'm not sure it does that already and it always adds an extra large chunk on top of whatever was forecasted.
1 voteSupport cost is already included in the cost that we show in our reports or dashboard hence also factored in the forecast already.
Rejecting the request to include Taxes, as we are excluding the taxes intentionally. Taxes are recalculated at the time of the invoices based on the currency or the country customers like to choose for the invoices. Which they have the flexibility to change as well. Hence taxes are neither included in our cost reports not in the forecasting.
-
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…5 votesThis was removed from the product because it generated confusion for users.
-
Default Sharing Settings
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 votesMay be more relevant in the future, but for now we will not be taking on this request.
-
Clarify Percentage Change View in Reports
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 -
Remove CUD Widget in DoiT Navigator when no info is present.
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 -
3 votes
-
Cloud Vendor Logo to our prebuilt Dashboard
I would it look better if we added logos next to Lens? For example, AWS Lens :aws: and GCP Lens :gcp_new:. It's not a burning issue, but I believe it would enhance the appearance. Also, it will be helpful when you create Custom Dashboards as well. I see them on Home screen but not when we click on Dashboard tab. Thanks.
1 voteWe purposely stopped doing this in the new dashboards design.
-
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 voteCan be done currently by disabling default anomalies and monitoring for anomalies an attribution that excludes the desired selection.
-
1 vote
We opted for using labels instead of folders for this purpose. You can do this by navigating to https://console.doit.com/analytics/all and editing labels there. You need the "Labels Manager" permission (enabled by default for Admins and other roles).
-
Advanced GKE Metrics
More Advanced Kubernetes Metrics
2 votesNot enough information
-
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 voteCloud incidents are already filtered based on customer regions.
-
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…2 votesDiscussed with the customers, this is no longer a gap and current data from DoiT is enough for their analytics.
- Don't see your idea?