[COMPASS-3577] Add connection field for custom appName value when connecting to database Created: 18/Apr/19  Updated: 29/Oct/23  Resolved: 27/Jun/19

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: 1.17.0-beta.5
Fix Version/s: None

Type: Bug Priority: Trivial - P5
Reporter: Jason R Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: feature
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Documentation Changes: Needed
Documentation Changes Summary:

Add instructions for the new appName field in connection settings

Sprint: Iteration Dingo, Iteration Echidna, Iteration Giraffe, Iteration Ferret, Iteration Hedgehog

 Description   

Currently, Compass creates 5 or 6 connections to a database when connecting. These connections do not include the "appName" parameter when connecting. 

As an administrator of a MongoDB, when listing connections, it is very useful to have a clear indicator of which processes / clients have opened connections (and how many). 

It would be nice if Compass can pass a default name as the appName parameter, or ideally allow users to enter a custom appName value in the connection settings before connecting to the DB. 

Not a critical requirement, obviously... but is a good nice to have.



 Comments   
Comment by Jason R [ 17/May/19 ]

Windows 10.

When trying to re-run the mongodb-compass-community-1.17.0-win32-x64.msi, I see the initial "installing" modal, but it quickly disappears and then nothing happens. 

The Compass FTE experience / setup is never displayed.

I do see MongoDB Compass Community Machine-Wide Installer in the Windows 10 Apps list (under settings), but the app directory & files are not installed to the Programs folder.

At this point, I am completely blocked from using Compass (including not being able to test the issue I reported).

Comment by Massimiliano Marcon [ 06/May/19 ]

What OS? Beta and stable usually are considered 2 different applications and you can have both installed at the same time.

Comment by Jason R [ 25/Apr/19 ]

Also... after installing the 1.18 beta, I cannot re-install 1.17 stable community.

Any suggestion for how to get a working installation of Compass again? If not, I will also file a separate bug report for this.

Comment by Jason R [ 25/Apr/19 ]

Hi Massimiliano,

When I run db.currentOp(true) to get the list of connections while Compass is running, the only connection with appName included is from my own app. 

All of the other connections show something similar to:

{    "host" : "MY_LOCALHOST:27017",    "desc" : "conn30",    "connectionId" : 30,    "client" : "127.0.0.1:57346",    "active" : false,    "currentOpTime" : "2019-04-25T01:03:33.194-0700" }

 

Also, I installed Compass 1.18 beta and tried it. I get the same result.

 

Is it possible that Compass does not keep the connection active? Does it connect, retrieve the results to display the current 'page', then disconnect?

Comment by Massimiliano Marcon [ 24/Apr/19 ]

rick_c137 we are sending it, and the server receives it properly. Can you check again? Maybe try Compass 1.18 beta just in case?

Generated at Wed Feb 07 22:33:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.