Add number of connected clients to Servers list in OttoDeploy

General
1

It would be really useful to have a column in the Servers list that shows the number of connected clients.

Thanks!

Tom Horton
VisionGift

2

Hey Tom,

Thanks for the feedback! Is the purpose of the list of connected clients to see how many people a deployment will affect? Someone else (I don’t remember who off the top of my head) requested similar information in the window where you kick off a deployment, which would get you the information right where you’re sending that deployment off. Would that get you the information you need or do you have a different use case?

-Kyle

3

Yes, the reason is to verify if there are connected users before a deployment. Isn’t there a new FMS feature for disabling new user access to database files? That would be interesting to be able to enable that feature and monitor the number of connected users before starting the deployment.

Tom

4

Yeah +1 for this. Would make day-time deployments a lot easier.

5

@vgtom the issue with this feature is that if you turn off new users and then use an Admin session to do something with the files it sometimes does not work because it is seen as a new connection…

6

@john_r Thanks for the heads-up on that feature. I already have a feature in my database to disable new logins before, during, and after maintenance. I enable it before migration to make sure users can’t log in right before migration and it stays enabled after migration so I can verify functionality before allowing users back in.

7

@kduval it was me who originally requested this, and I’d still love to see this feature implemented as it would prove a big help in determining whether it is safe to run a deployment. I often deploy to UAT server and I’d rather just do this when nobody is on the system, rather than having to deal with the hassle of disconnecting users

I’ve mocked up what I am envisioning:

Screenshot 2025-02-26 at 4.22.42 PM
Screenshot 2025-02-26 at 4.22.42 PM2940×1108 238 KB

I do like that you can already specify a custom message to show users if there are connected users, but as far as I can see OttoDeploy will just force disconnect user connections (not sure what the timeout is for that).

It would be nice to have an option to just not run the deployment if there are connected users, especially if deployments have been scheduled - which if memory serves there is some way to do that not via the OttoDeploy interface.