29 results found
-
Anomaly detection on the Usage data
Expand our existing cost anomaly detection using the billing data to also support the anomaly detection on the usage data
1 voteWe will reconsider the priority of this feature later in this year, hence declining the request for now.
-
Shareable Links for Dashboards
Dashboard URLs get stale very quickly because they rely on the name rather than an id. I can't find a share link for dashboards, I assume it doesn't exist. It's annoying because any rename will break existing links.
1 vote -
Store report configuration in the browser URL
I often explore data in reports, tweaking the filters and groups etc. I run into issues with that:
- I can't easily share the report with someone else. I'd have to save it, but I don't want to keep it around forever. Instead I take a screenshot, but it's not interactive.
- If I close the tab and re-open it, my changes are gone. Same thing if the tab reloads for some reason.
1 vote -
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.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 -
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.
-
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.
-
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 -
Japanese Local Payment Methods
Customer problem:
I would like to have flexibility with the different payment methods that a provider supports and thus be able to pay with the one that suits me best. I.g.: Japanese local payment methods such as JCB and Furikomi.
1 vote -
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).
-
Anomaly detection by custom cost tag
We'd like to adjust our anomaly detection to allow selection of custom cost tag.
For instance, our primary cost tag is the Component tag, we now often get SKU-based anomalies that aren’t anomalies when looking at en entire Component tag value.
For instance: We may have a cluster tagged with Component=EMRCluster1 that switched from using one type of EC2 instance to the other. This will show up as an anomaly, but the entire service under this Component tag didn't necessarily have an anomaly.
30-50% of the anomalies we get now are now red herrings because of this.
My questions:
-…1 voteThis is currently possible using the allocations. We understand that manual work is required to create multiple allocations however it is just a one time effort. We are declining it for now as it doesn't take higher priority than the other capabilities planned for anomaly detections however we will be revisiting this in the future once we get more customer data.
-
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…
1 vote -
Allow for comparisons of partial months
Currently you can only do full month comparisons which makes it cumbersome to quickly compare how you're doing this month vs last at a granular level.
For example, we're currently 22 days into May. I want to see this month vs up to the 22nd of last month.
It's possible to do this breaking it down by days, but that gets very tedious trying to scroll up and down to compare the data, losing your place etc.
1 voteYou can do this by adding the "Day" dimension in the "Group by" section in the left panel in Reports.
You can also select view options like "Row Heatmap" to make it easier to see days where there has been an increase vs. decrease.
-
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.
- Don't see your idea?