8 results found
-
Enable importing Google Cloud billing account historical data both standard and detailed BQ exports.
Most Google customers do not have BQ export enabled for their direct / other partner billing accounts. The few who do, usually have only the standard BQ export options. Importing historical data makes the Navigator more useful faster and enables customers to compare their better new DoiT pricing with their older pricing. Allow customers to import all types of BQ exports and not just the new detailed schema which most customers do not use.
29 votes -
Improve Insights API / CRE UI to enable semi-automated submissions by CREs
Hi,
I think it would be great for customers and CREs alike if CREs could, quickly and seamlessly, create multiple Custom Insights based on findings from deep technical dive meetings they hold with customers.
A pilot use case I had in mind is Technical Kick-Offs (TKOs): These are multi-hour engagements that comprehensively cover the customer's architectural design as it involves walking through a long check-list of things to ask about. I have a CSI board task set up (https://doitintl.atlassian.net/jira/core/projects/CSI/board?selectedIssue=CSI-1507&text=insights) which describes the following workflow I'd like to build that, if enabled by an upgrade to the Insights API…
5 votes -
Submit Support Tickets directly from Slack (Ava Chatbot to Human Led)
I have a few customers who are requesting that we offer a chatbot or an ability to directly submit support tickets and manage them through Slack. They had this feature at their last partner and it made it very easy for them to communicate and update support tickets.
4 votes -
Testing notifications to verify setup
Hi Team, would it be possible to add a "Test Alert" button for Cost and Budget Alerts. This allows customers to verify if the channel is working correctly without altering the logic of their alerts.
10 votes -
Right-sizing Serverless Workloads
PerfectScale is making right-sizing Kubernetes workloads a breeze. Cloud companies (including Doit) have a lot of their workloads in serverless technologies as well, AWS Lambda and ECS/Fargate, GCP Functions and CloudRun. The basic principle is very similar, looks at the CPU/Memory/GPU/Network usage of the workload, and adjust configuration as needed.
Cloud companies heavily rely on serverless and containerized workloads such as AWS Lambda, AWS ECS/Fargate, GCP Cloud Functions, and Cloud Run. These platforms promise automatic scaling and flexibility, but in reality, workload sizing presents significant challenges:
- Many companies allocate excessive resources (CPU, memory, GPU) out of fear of performance bottlenecks.…
2 votes -
Open AI integration with DoiT Cloud Intelligence
The rapid adoption of OpenAI, has revolutionised business operations. However, the increased utilisation of these powerful tools often leads to rising and unpredictable costs, compounded by the escalating expenses associated with cloud infrastructure.
DoiT Cloud Intelligence (DCI) integration with OpenAI is designed to provide customers with a comprehensive solution for monitoring and managing their OpenAI expenses alongside their existing cloud costs, ensuring unified visibility and control over their IT investments. Additionally you can leverage DoiT existing and new FinOps capabilities to exercise better control over your costs, and ensure that AI investments yield maximum value while remaining within budget constraints.
1 vote -
Ingest AWS email notifications and AWS Personal Health Dashboard events to the Cloud Incidents
Be able to ingest AWS Health events from the Master Payer Account and linked AWS accounts and show them in the Cloud Incident panel.
If possible, be able to read each customer's MPA email to extract any notifications we might come up with. eg: Abuse reports, Automated alerts sent via email
5 votes -
S3 File-Level Cost Allocation Tags
This feature will allow users to assign AWS cost allocation tags at the file level within S3 buckets. This will provide more granular insights into resource usage and cost distribution.
Users can tag individual files based on project, department, or any other relevant identifier, and the DoiT console will then track and report costs associated with these specific tags.
This should be a feature that should be an opt-in per bucket due to the possible cost associated with analyzing and retrieving that metadata.1 vote
- Don't see your idea?