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 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.
93 votesWork for this feature is now planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
52 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.
37 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.
-
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.18 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)
16 votesThanks for your suggestion.
The index transformation value use see in the header is actually not always an accurate value. There are four replicas in a replica set, each with it’s own copy of the index. When this header is returned it can from a different partition, each which may be at its own percentage of progress during an index rebuild.
This is something we hope to provide at some point but is on our backlog. Will mark as unplanned for now and change if this moves in the future.
thanks.
-
cosmosdb graph make input query multiline
Please replace the single line textbox of the cosmosdb graph data explorer query filter to a multiline textbox! As of today it is impossible to use even with the simplest gremlin queries.
13 votesHello and thank you for your suggestion.
This capability is on our backlog and we do plan on doing this but is not currently committed. Will mark as under review and when this gets committed will mark as Planned.
Thanks for your suggestion.
-
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.
12 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 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.
-
Data Explorer: Allow lazy loading collections to avoid perf overhead when tehre are many collections
Currently all collections are shown in the Data Explorer. This takes quite some time when an account has many collections. An option to lazy load collections would be nice.
12 votesWe have reviewed this and this is not on our roadmap at this time.
Will mark as unplanned and put on our backlog.
Thanks.
-
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.
-
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.
9 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.
7 votesHi Sidney. We took a look at this. It’s definitely possible but it’s not currently scheduled in our current roadmap.
We’ll add this to our backlog and look at this again soon.
Thanks!
-
Allow saving queries to disk in Azure portal
There is a nice feature in the Azure portal to open queries from disk but the workflow is rather awkward because you can't then save the changes back to disk.
I'd like to be able to edit my query files and save them directly from the portal.
I realise you can save them to another Cosmos DB but I don't want the cost of another database in each environment and I want to save my personal queries.
5 votesReviewing
-
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
4 votesThank 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.
-
Enable programmatic Jupyter notebook access
I see that it's not possible to enable Jupyter Notebook support using the CLI, SDK, REST API, or an ARM template. It would be great to be able to enable Jupyter notebooks from code and even add a notebook.
4 votes -
Improve refresh behavior in explorer UI
In the emulator and storage explorer interfaces, browsing the contents of a container is made more difficult when checking newly-added items. If you have clicked "load more" multiple times and scrolled down the list, clicking "refresh" resets the scroll position and loses all the previously loaded items.
It would be a nice quality of life improvement to make loading new items less disruptive. For example, "load more" should implicitly perform refresh for items created since last performed load query.
4 votes -
data explorer should not require IP exceptions
data explorer should not require IP exceptions
3 votesThank you for your suggestion.
At this time, this is not on our immediate roadmap. Will add to our backlog and look at this for future planning.
Thanks.
-
Show the container id in the tab view when using data explorer
When querying Cosmos DB using the Azure web portal, you select a container, and then you can select Items. This opens a new tab in the right hand window with the title "Items".
It would be very helpful if this also showed the container id, allowing for users to see at a glance which tab relates to which container.
2 votes -
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.
-
Display cost in the CosmosDB overview blade in the billing currency
The running cost that can be viewed in the CosmosDB account overview blade, which gives hour to hour, day to day or monthly at a glance is very convenient and useful.
However, this is displayed in USD only, and it doesn't say USD anywhere, so if your billing currency is also dollars (such as AUD), then this can be misleading.
Please display the cost in the billable currency, or at least explicitly state the cost is USD$ instead of just $.
1 vote
- Don't see your idea?