Azure Cosmos DB
Have feedback for Azure Cosmos DB product? Submit your idea here or upvote other ideas. All feedback is monitored and reviewed by the Azure Cosmos DB team.
This site is for feature suggestions only. For technical questions or issues, please submit them to StackOverflow,where we and the community can better help you.
Please use the following categories when submitting your idea.
Gremlin API: Graph features and capabilities using Gremlin API.
MongoDB API: Features and capabilities using MongoDB API.
Table API: Features and capabilities using Table API.
Etcd API: Features related to using etcd as a configuration store for Kubernetes.
Built-in Apache Spark: Features related to built-in Apache Spark in Azure Cosmos DB.
Built-in Notebooks: Features related to built-in Notebooks in Azure Cosmos DB.
SDK: Features related to Azure Cosmos DB SDKs for SQL API.
Change Feed: Features related to Change Feed.
Management: All management features, backup/restore,monitoring, ARM, PowerShell and CLI.
Portal: All features for Azure Portal and Cosmos DB Explorer.
Emulator: Features related to the Azure Cosmos Emulator.
Other: Features not related to any other category.
-
Pin the Graphs from the Metrics Page to Azure Portal Dashboards
I would love to be able to pin the graphs on the Metrics tab of the Azure Portal blade for Cosmos DB to my Azure Dashboard. Many other services allow this and it's great to get an overview of health, status and usage. Also great for Ops dashboards, sharing, etc.
Right now the work around is to manually point the diagnostic logs to an OMS workspace and recreate the query in Log Analytics, and then pin it. It kinda sucks and your graphs are way better.
74 votesWork for this feature is now planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
Please don't surprise your customers with Azure Cosmos DB costs...
1. RU/s are confusing, new and different. Please assume that your current and potential customers are not going to understand how they work for a while.
2. Notify your customers via portal alerts when their costs are on track to increase by more than 50% on the next invoice.
3. Every service needs a trial mode. There needs to be a very cheap and limited way that current and potential customers can test drive Azure services without being surprised by thousands of dollars in charges.
4. Don’t default to 800 RU/s when creating an Azure Cosmos DB Table with the…29 votesHi Robin, thank you for your feedback. Will take one at a time.
1. We realize RU/s (provisioned throughput) is a different model than people may be used to. It is however, not different than say provisioning a VM where you are paying for compute, IO and memory. Customers here too do not want to over-provision as there are unused resources. The same goes for Cosmos DB. Where we need to do better, is in helping people measure their usage and tune their RU/s. This work is planned and ongoing.
2. We are currently planning on enhancements to Azure Advisor in the portal around this.
3. Cosmos DB has three different means for Trial. There is the Azure Trial itself. There is also our Emulator (https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator). Finally, there is TryCosmosDB, (https://azure.microsoft.com/en-us/try/cosmosdb/)
4. I will review this with our SDK team. Agree we should use minimums as…
-
TTL default value needs to be blank for mishandling
When TTL selected "On", default value in the text box should be blank to prevent from user's mishandling to unintentionally delete data.
I did it and had deleted data.. So I strongly request this.
I think little tweak can achieve my request.21 votes -
20 votes
This was mistakenly closed. Am moving it back to Started. Will prioritize this to get it completed and notify here once done.
Our apologies for the confusion.
-
monitor and kill queries
Add ability to monitor (ie. see SQL query) and kill long running user queries from within Data Explorer.
14 votesThis capability is not on our road map today but we do provide query metrics using our SDK’s. You can read more about what we provide here, https://docs.microsoft.com/azure/cosmos-db/sql-api-sql-query-metrics#query-execution-metrics.
Thank you for your suggestion.
-
Add Intellisense to azure portal
The query explorer should have intellisense
12 votesWe are working on this but do not have an ETA for this yet. Will update here as we get closer to releasing.
Thank you for your suggestion.
-
Interactive JavaScript Shell
It would be great to have a JavaScript shell (either on the Azure site or something we can connect to) to throw code against for testing purposes as well as do single operations.
11 votesThank you while we reviewed this.
At this time this feature is not on our road map. We will leave this marked as unplanned for now and will revisit this in upcoming cycles and will update here if this changes.
Thank you for your suggestion and votes.
-
Make triggers be able to fire from Azure portal
Triggers in DocumentDB should act like triggers in SQL Server, which means when you update documents from Azure portal, the triggers should be fired as well. Right now, this feature is missing. Triggers only can be fired from application code.
10 votesAt this time this feature is not on our road map. We will leave this marked as unplanned for now and will revisit this in upcoming cycles and will update here if this changes.
Thank you for your suggestion and votes.
-
Add pre/post trigger support to Data Explorer
Today, you can demo most of Cosmos DB to DBAs and IT Pros using the portal and Data Explorer.
Unfortunately, to demo pre/post triggers, you would need to open an IDE and write an application and that loses most of the non-developer audience at a conference or user group talk.
It would be great if we could, optionally select a pre/post trigger to run as part of the "New Document" experience in the Data Explorer.
4 votes -
Expose index transformation progress in the portal
When going to the Scale and Settings tab I can see in the browser dev tools that the header x-ms-documentdb-collection-index-transformation-progress is returned to the client however this information is not shown anywhere in the UI.
It would be useful if this information was displayed in the portal (possibly only if less than 100/ a transformation is currently in progress)
4 votes -
data explorer should not require IP exceptions
data explorer should not require IP exceptions
3 votes -
Multi-line Graph/Gremlin query textbox in the portal
In the Azure Portal, the graph query text box allows pasting of multi-line queries, but if the query is longer than the query textbox, you have to scroll horizontally (using arrow keys). I frequently debug queries using this interface, but I usually end up having a separate text editor open so I can view the entire query, copying/pasting back and forth.
Allowing for at least a few lines of text with a vertical scrollbar would be great (like we have now for SQL queries). Optional word-wrap would make it even better.
3 votes -
Graph DB - more query tabs
You should add more query tabs on CosmosDB for Gremlin, so that users can run different queries and compare the result without deleting every time the content of the textbox
1 voteThank you for your suggestion. This is currently not on our roadmap but want to get feedback and input.
How many tabs do you think you need?
thanks.
-
File name messes up with status after uploading JSON documents to Cosmos DB
File name messes up with status after uploading JSON documents to Cosmos DB when the file name is a little too long. It ruins the look and feel of Azure
1 voteWork for this feature is now planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
Clear Rate Limiting warning faster
When you reach a rate limit, and then subsequently increase the RU's the Map shows Orange / rate limited for a long time (a few hours it seems) after it has been increased and no longer rate limiting...
1 voteHello Anton. Thank you for your suggestion. Yes, the rate limit graphic is overly aggressive. We are planning to change that behavior so it more closely maps actual rate limiting.
This work is planned but we do not have a precise ETA. Will update here either when this is started and for sure when it is complete.
Thank you for your suggestion.
- Don't see your idea?