8 results found

1. Don't search for entire document set of a collection on a new tab by default

   When I want to search for documents of a collection I select the collection on the left pane and then a new tab is opened, that shows information as seen in picture big-collection.png.

   However, the problem with this default configuration is that is searches for the entire document set to display the information Displaying documents 1-20 of 1183373. The executed query is:

   {code}
   {
   "appName": "MongoDB Compass",
   "command": {
   "aggregate": "progress",
   "pipeline": [
   {
   "$match": {}
   },
   {
   "$skip": 0
   },
   {
   "$group": {
   "id": 1,
   "n": {
   "$sum": 1
   }
   }
   }
   ],
   "hint": "id_",
   "cursor": {},
   "maxTimeMS": 5000,
   ...
   {code}

   This query already takes >500ms to be executed and once we grow our dataset even larger this is going to be a big problem performance wise.

   We want to see how many documents there are in the collections but on a new tab page it is completely enough by default to show only 20 documents and either do a lazy loading of further pages or only display the total number of documents in the overview line. If we want to search for more documents we can still do this manually afterwards. On the new tab load the entire document set simply should not be collected.

   When I want to search for documents of a collection I select the collection on the left pane and then a new tab is opened, that shows information as seen in picture big-collection.png.

   However, the problem with this default configuration is that is searches for the entire document set to display the information Displaying documents 1-20 of 1183373. The executed query is:

   {code}
   {
   "appName": "MongoDB Compass",
   "command": {
   "aggregate": "progress",
   "pipeline": [
   {
   "$match": {}
   },
   {
   "$skip": 0
   },
   {
   "$group": {
   "id": 1,
   "n": {
   "$sum": 1
   }
   }
   }
   ],
   "hint": "id_",… more

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Notify users when a database is being rate limited

   Suggestion: When a database is being rate limited, please indicate this on the dashboard.

   And/or send an email to the developer, so they can take action, like upgrading the DB tier.
   (Preferably before they're locked out of the database for 7 days).

   Context:

   Just had a production outage, because the M5 database we were using went from 2.5 seconds for a response, to 120 seconds a response.

   There was no warning, no alerts, no emails, and nothing on the dashboard to indicate we were being rate limited. I waited 2 hours with chat support and got nowhere.

   Finally got an answer the next day, that we were being rate limited.

   Suggestion: When a database is being rate limited, please indicate this on the dashboard.

   And/or send an email to the developer, so they can take action, like upgrading the DB tier.
   (Preferably before they're locked out of the database for 7 days).

   Context:

   Just had a production outage, because the M5 database we were using went from 2.5 seconds for a response, to 120 seconds a response.

   There was no warning, no alerts, no emails, and nothing on the dashboard to indicate we were being rate limited. I waited 2 hours with chat support and got nowhere.

   Finally got an… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Take too much time preloading database statistics

   As you can see, My MongoDB instance has over 10K databases and over 400K collections, Every time I connect to it with Compass, I have to wait for more than one minute before Compass is ready to use. This 'collecting information process' is unnecessary because I don't care how many collections are there, all I want is jump into one of these databases and start my work.

   So I would be appreciated if there is an option to skip this 'preloading' process.

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Historical log of slow operations

   Compass's "slowest operations" feature in the performance tab has been very helpful for debugging collection scans due to missing indexes.

   The only problem is that I have to sit there and watch it to try and "catch" the slow operations with a click before they disappear. I'm running many databases on this server, and the server is talked to by many web servers running various apps and tools, and my debugging process usually starts with noticing spikes in the Operation Execution Time (from the free monitoring page).

   There are obviously other ways to log slow operations, but I've found Compass so useful that I'd love to be able to do all my index debugging from within the Compass UI.

   It would be useful to be able to click a "record" button, and maybe even set a threshold for the number of milliseconds required to trigger the slow operation catcher. Those operations would then get added to a list which I can come back and check later.

   This is related to this idea: https://feedback.mongodb.com/forums/924283-compass/suggestions/38666326-show-user-accumulated-query-time-per-query-shape-i

   Compass's "slowest operations" feature in the performance tab has been very helpful for debugging collection scans due to missing indexes.

   The only problem is that I have to sit there and watch it to try and "catch" the slow operations with a click before they disappear. I'm running many databases on this server, and the server is talked to by many web servers running various apps and tools, and my debugging process usually starts with noticing spikes in the Operation Execution Time (from the free monitoring page).

   There are obviously other ways to log slow operations, but I've found Compass… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. use AI to optimise aggregation pipeline

   Now that AI is being introduced, it would be very useful to use AI stage wizard to optimise the aggregation pipeline so that it runs optimally in Atlas

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. shortcut to update data

   shortcut to update data instead of having to scroll down long lines to press update

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Mobile app

   It would make viewing/editing db documents on mobile easier. Currently it is very difficult

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. View sub collections as dropdowns or directories and adding a search feature for collections

   I think MongoDB Compass is an incredibly powerful software using which one can do easy queries and manipulations to data. I also like the UI - its clutter free and easy to use.

   I want to request an additional feature in Compass which isn’t currently there:

   Viewing sub collections as dropdowns or directories(Tree structure)

   Generally, sub collections are namespaced using a period(.) and they make sense since the data becomes easy to organise and work with.

   Say we have nx.ny.na.nb…(n - nodes, x y a and b are integers) type collections

   1. If only a single final collection exists under a particular parent node, then the final collection is directly displayed under the parent node without further nesting.

   2. The root node is always nested.

   3. If a parent node is also a final collection, then the parent node is nested and the final collection is displayed as a child of itself.

   4. If a subcollection ends with a period(.), its treatment will be same as point 3.

   5. For more than one consecutive periods, it is treated as a single collection under its parent. No further nesting occurs.

   6. Collections starting with period would be treated as a single file.

   7. If the parent node only has a single child which is in turn a parent, then both of them can be conglomerated into a single directory. Exception - root node
      (Example: Instead of 'n0'->'n1'->n10.coll,n20.coll, it could be 'n0.n1'-> n10.coll, n20.coll[ .coll are just way of representing individual collections])

   So if n10.n20 is the only sub collection under n0.n1 and n0.n2 has n66, n55, n66.n95, n55.n85, n66., n66.....54, n66.n95.n54 and n55.n85.n86 as sub-collections the output would be this -

   https://upl.io/o50cvs

   For the dropdown view, I have shown it in the developer forum -

   https://developer.mongodb.com/community/forums/t/feature-request-view-sub-collections-as-dropdowns-in-compass/4860

   Adding a search bar to search for collections would also be helpful for those who know exactly what they are looking for.

   Implementing this would greatly improve readability, and de-clutter the collections for databases.

   I think MongoDB Compass is an incredibly powerful software using which one can do easy queries and manipulations to data. I also like the UI - its clutter free and easy to use.

   I want to request an additional feature in Compass which isn’t currently there:

   Viewing sub collections as dropdowns or directories(Tree structure)

   Generally, sub collections are namespaced using a period(.) and they make sense since the data becomes easy to organise and work with.

   Say we have nx.ny.na.nb…(n - nodes, x y a and b are integers) type collections

   1. If only a single final collection exists under a… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance/Speed  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close