82 results found
-
Return "Login" Button
Please return "Login" button back to doit.com!
1 voteWe just brought this back due to popular demand. It relies on the "doit_app" cookie, which console.doit.com sets on each login. If you've logged in at least once, you should see "Log in" instead of "Start for free" (trial).
-
MCP streamable http auth with api token
I would love to connect HolmesGPT running on EKS to the DoIt MCP but for this I need to be able to use a bearer token for connection rather than click-in-browser-based auth
2 votesThanks for the suggestion, and good news: this is now live.
https://mcp.doit.com/mcp accepts a DoiT personal API token as a bearer header, so headless clients like HolmesGPT can connect without the browser sign-in.
Create a token from Profile → Personal API tokens in the DoiT console, store it as a Kubernetes Secret, and point HolmesGPT at the server like this:
mcp_servers:doit:description: "DoiT Cloud Intelligence"config:url: "https://mcp.doit.com/mcp"mode: streamable-httpheaders:Authorization: "Bearer {{ env.DOIT_API_KEY }}"health_check_tool: "validate_user"Tools run with the token's own permissions, the same as the local server. A dedicated token for the agent, rotated on a schedule, is the recommended setup.
If anything doesn't work as expected, please email vadim @ doit dot com
-
WebUI page title
Update the console to put "DoiT" in the page name. That way I can find it in the plethora of tabs that I have open. Currently it just says "Home", like a ton of other things do.
2 votesHello,
Based on your suggestion, we've decided to update the title we use for the Cloud Intelligence™ Console. The change has already gone through our global deployment pipeline, so you should see the updated title today or tomorrow.
Thanks for the idea. We're looking forward to the next ones you may have.
Vadim
-
Expose customerFeedback for cost anomalies
I recently asked you to add a new endpoint for updating cost anomalies programmatically (https://uservoice.doit.com/forums/957092-doit-cloud-intelligence/suggestions/51537587-allow-an-anomaly-s-status-to-be-updated-programmat), which has been implemented. However, the
customerFeedbackfield is not returned in any GET endpoint. This causes a problem for a system doing automatic triage of the anomalies because any manual decisions and changes made in the web console remain invisible through the API.What I'd like to see is the fields from the PATCH endpoint (https://developer.doit.com/reference/patchanomaly) returned by a GET endpoint, e.g. https://developer.doit.com/reference/getanomaly.
1 voteHi, thanks for the feedback!
The `customerFeedback` field has now been added to the GET anomaly by ID endpoint: https://developer.doit.com/reference/getanomaly.
Please reach out again if you have any questions or further feedback.
-
Hide filters in reports
Option to toggle hide over a filter, so I dont have to delete and add back on everytime
1 voteYou can now turn report filters on and off without deleting and recreating them. Use the switches beside items in Filter results and Group by to compare configurations while keeping your selections and order intact.
The report reruns automatically after each change, and saving preserves the on/off states for next time.
Thanks for suggesting this, please let us know how it works for you!
-
GitHub issues
Also offer to create GitHub issues in addition to Jira stories. This allows those using GitHub project/issues as their Agile board to also benefit from auto-creation.
1 voteWe've added GitHub Issues support to Threads. To turn it on, go to https://console.doit.com/integrate/integrations/github-issues/manage and connect your GitHub organization.
-
Allow an anomaly's status to be updated programmatically via the API.
The Anomalies API is currently read-only (
GET /analytics/v1/anomaliesandGET .../anomalies/{id}). There is no way to change the state of an anomaly through the API.Please add a write path - for example
PATCH /analytics/v1/anomalies/{id}-supporting an acknowledge / dismiss / resolve state transition, ideally with an optional note or external-reference field so an anomaly can be linked to a record in an external system. This would mirror the status-update capability the Insights API already provides viaPATCH /insights/v1/sources/{sourceID}/insights/{insightKey}.This may also merit adding another endpoint to the API for listing ackowledement reasons.
Use case:
Teams that…1 voteWe've added a write path to the Anomalies API that mirrors the console's review workflow:
```
PATCH /anomalies/v1/{id}
```
You can now set an anomaly's `reviewStatus` (`NEEDS_REVIEW`, `UNDER_REVIEW`, or `RESOLVED`), qualify a resolution with `ANOMALY_CONFIRMED` or `NOT_ANOMALY`, and optionally attach a `resolutionNote` with a feedback reason and comment.
Feedback reasons cover both directions — e.g. `MISCONFIGURATION`, `UNINTENTIONAL_PROVISIONING`, and `EXPECTED_COST_SPIKE` for confirmed anomalies; `FAULTY_ANOMALY_DETECTION_MODEL`, `LOW_IMPACT`, and `INCORRECT_DATA` for non-anomalies — so your automation can close the loop on triage done in external systems.
A few notes based on your suggestions:
- **Acknowledgment reasons** are documented directly in the OpenAPI spec as self-describing enums (no extra endpoint needed), including which reasons are valid for each resolution — validation is enforced server-side.
- The change is recorded in the anomaly's review history and feed exactly like a console update, so DoiT and your downstream tools stay in sync without duplicate triage.
- It…
-
Hide or Delete offboarded accounts
Requesting a formal enhancement within PartnerOps for us to Hide and/or Delete any "offboarded" accounts in both T2 & T3. As it stands today, we can unlink their AWS account from PartnerOps so that no new data is coming in and they can maintain their historical data.
This is great, but we do feel there is a need to be able to delete, or hide at the very least, accounts that are no longer transacting. This will help keep all tenant levels cleaner and give Ingram and Resellers the ability to clean up their tenants of old accounts that are…
1 voteWe released the ability to Deactivate tenants and hide them from the customer tree on the 12th August 2026.
-
Add acknowledgement and alert dates to Cost Anomalies API
Would it be possible to add new fields to the data returned by Anomalies API? Namely:
- acknowledgement timestamp
- first notification sent timestamp (as this is not the same as anomaly start)These pieces of data are critical for tracking internal SLAs on cost anomalies but are currently missing and have to be inferred and approximated from other sources.
1 voteWe've now released the requested attributes as `acknowledgedAt` and `notifications` to both the List and Retrieve Anomaly endpoints. See our developer docs for more information: https://developer.doit.com/reference/listanomalies.
Please let us know if this release serves the intended purpose.
-
As a User, I want to be able to request a Workshop or Training but I struggle to find it.
I want a logical place to request services from DoiT to get deeper help with an AI project, improve my architecture, security, or spot hidden inefficiencies in my costs to improve my cloud operations. I should be able to do this from the same place where I can search my past support cases.
When I go to my past support cases,
Add an option for 'Professional Services' next to the “Create a request” button so I can get services without having to get in touch with my Account Manager.8 votes -
Understand Reservation Cost and usage in BiqQuery
We would like to be able to run reporting where we can understand the usage of BQ against the Reservations. This would allow us to have a more robust chargeback/showback.
2 votesThis idea has been shipped for more accurate cost estimates in BQ Reservations for Real-time Cost Anomalies. Implementing the reporting nuances is being handled via an FDE engagement and we will revisit how to bring this data in (if possible/plausible) with Sayle et al.
-
SSL - DoiT Console / Onboarding
Secure Sockets Layer (SSL): The impact of SSL on the DoiT Console has not been fully tested yet. Given the importance of encrypted communications, I would like to raise this feature request to UserVoice on behalf of our customer Autorola.
This way, we / the DoiT Product Team can evaluate and address it accordingly whether this is 1/ a straightforward fix or 2/ a more involved process.
13 votes -
Limit Results by Total or Percentage Change
When using the data views of either percentage change or absolute change, The customer would like to be able to limit those results by both value and/or top/bottom.
For Example if viewing spend using percentage change, they would like to be able to use the limit result feature to say only show me the accounts that have percentage change 25% or more.
5 votesThis is now live. In Limit results, you can now keep only the rows whose change is above or below a value, as an absolute change or as a percentage. For example, only the accounts with a change of 25% or more. It also works when you compare 2 time ranges.
-
customer domain
I noticed the customer's domain is no longer visible in the customer's profile and was replaced with just the customer name. Can we please put the domain in the dropdown menu for the customer? BizOps needs to be able to locate the domain everyday for audits, EUR, etc. and be able to copy/paste quickly. We already do a lot of manual work and this adds a couple more steps trying to locate it.
4 votes -
Service accounts for API use
Hello,
It'll be a good feature to be able to create read-only API keys, so the API access can be automated with less risk.
Thanks
7 votes -
Re-alerting for an active anomaly if the cost spikes by 2X or 3X
Today, once we notify for an anomaly, we do not notify again if an anomaly is active but the cost has spiked by X times, lets say twice. As a result, customer who ignored the anomaly in first place based on its cost missed the opportunity to react when the cost spike became more considerable.
6 votes -
Invoice API, download the PDF invoice
Can we have an additional Invoice API to get the actual invoice PDF files?
2 votes -
Compare non-consecutive time periods in cloud analytics
The customer—specifically the person responsible for FinOps—would like the ability to compare specific time periods while excluding everything in between. For example, they want to compare June 2024 vs. June 2025, or Q2 2024 vs. Q2 2025, without including the months in between.
This is similar to the “this period vs. last month” view we currently offer, but they’re looking for a customizable comparison between non-consecutive timeframes—essentially, a way to isolate and break down specific months or quarters year over year.
MoM, QoQ, or YoY
4 votes -
Swagger/OpenAPI Spec
Please publish a full Swagger/OpenAPI spec for your API so we can generate type-safe clients in a language of our choice. This makes the time to value much quicker with the API.
1 voteThe YAML file can now be downloaded by clicking on the "OpenApi" button in our Developer Docs (https://developer.doit.com/reference)
Direct link: https://developer.doit.com/openapi/doit-api.yaml
-
Allow us to restrict sign ins to SSO only
Allow us to restrict sign ins to SSO only.
1 voteThanks for your input, Gabriel!
We do exactly that once SSO is enabled.
Once SSO is enabled only admins can bypass SSO and sign-in with password (we allow admins to bypass it in order to prevent users from locking out everyone with a wrong SSO configuration).
We will add this information to the SSO UI and the Help Center docs to clarify this, thanks!
- Don't see your idea?