Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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.

SQL API: Query language features, syntax using SQL API, indexing, any other core features in Azure Cosmos DB.

Gremlin API: Graph features and capabilities using Gremlin API.

Cassandra API: Features and capabilities using Cassandra 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.

Azure Synapse Link: Features related to Azure Cosmos DBanalytical store and Azure Synapse Analytics run-time support

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.

Security:
Authentication, authorization,permissions and encryption features.

Monitoring:
Metrics, monitoring, alerts,and diagnostics features.

Server-side: Stored procedures, Triggers,and User-Defined Functions.

Managed Apache Cassandra: Featuresand capabilities related to Azure Managed Instance for Apache Cassandra.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Pin To Dashboard Cosmos Db Number of Requests Chart

    Like other charts, Can we have an option to pin to dashboard for monitoring Throttled requests for cosmosdb

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  2. Base metrics of the "Average RU/S" on the whole selected period

    In the troughtput Metrics the indicator about Average RU/S should be modified as follows:
    •The label/tooltip should be clear about the fact that the average refers to the last hour and not the selected period
    OR
    •The calculation should be done on the whole selected period (From-To or Last Week)

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. cosmos db metric not raising/recording http 401/403 response

    cosmos db metric not raising/recording http 401/403 response.
    It will be helpful if this is included as part of metrics

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  4. Record the request unit cost in App insights

    Hi, what would be great is that when we record a database read/write in app insights, we can also get a record of the RU's with the response. This will allow us to find what are the most costly actions and also trace any issues that may occur in the event of a 429

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  5. Make more metrics available at less granularity than PT5M

    NormalizedRUConsumption is available with the following granularities :PT1M, PT5M, PT1H, P1D

    This is useful. I was able to pull per collection level details from Azure Monitor for an account with 111 collections at hour granularity for 28 days with no issue (c. 75,000 data points).

    I also wanted some other details though - specifically ProvisionedThroughput at the moment (though this comment applies to a lot of available metrics).

    The fact that this is only available at 5 minute granularity means that I have to request 895,104 data points for the same number of collections and periods and then aggregate it…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  6. Inconsistent casing returned for database names by NormalizedRUConsumption and ProvisionedThroughput

    I found when requesting metrics from NormalizedRUConsumption that in some cases the database names were returned with different casing than are used by the ProvisionedThroughput metric.

    I would expect there to be some canonical form that is used throughout.

    An example of why this causes an issue is that I do the request for NormalizedRUConsumption first and then (in power query) call a function that gets the ProvisionedThroughput for that database. This fails to return anything for some databases where the casing is different (and passed as $filter parameter to Azure Monitor)

    It isn't clear how one would know up…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base