Request: Visibility of Connected Users when Deploying

OttoDeploy
,
1

Hi there.

I have a feature request and wondering if something like this is possible in a future version.

When I do deployments - often staging versions - I’d like to know before running the deployment if any users are connected to the solution. I always feel a little apprehensive doing deployments with users connected. I realise there is an option to send the a message, but other than that they’ll be disconnected.

It would be great to know how many users are connected to each file being deployed (and thus closed). It might allow me to make better choices about delaying a deployment or at least contacting the users via phone/email prior to a deployment instead of surprising them :slight_smile:

While this can be done, it’s a bit clunky as you have to go to the Servers tab, and open either the Otto or FM admin console to view this information. I’d love to see it right there in the deployment setup beside the destination files. even if it were a #, or maybe a tooltip with list of users on that # would be awesome, thanks!

2

Hey Daniel,

We could possibly add this onto the review screen when sending a deployment, I think that would make the most sense here. Do you agree?

-Kyle

1 Like
3

Absolutely , that would be very helpful and the most logical place to put it, thanks :+1:

1 Like
4

I was just going to request the same, when I found this thread.
Let me push it a bit further.

In addition to seeing how many users are currently connected to the solution, it would be good to have a possibility to list them along with client type (Pro vs WebDirect vs Data API etc). It could be done at least by clicking a link that takes me to the OttoFMS web interface, but event that does not seem to be able to list the clients now, so we have to go to the Admin Console, but there we have to do it for one database at a time. Otto could just collect all users sessions which are affecting at least one of the files being included in the deployment.

If no users are connected, it would be even better to see how long ago the last one disconnected. My usual practice is to wait at least 1 minute after last user disconnects before starting the deployment.

And final one, but that can be understood as a separate feature request - in addition to “Start Now” and “Schedule for Later” it would be great to be able to schedule the deployment for “After All Users Leave” and ideally be able to specify how long to wait after last user leaves.

1 Like