How do you all deal with keeping winbox connections open to multiple devices?

There's got to be a better solution than how I do it:

Open just for looking at the LOG ?
I send all log that I want to see at once to the syslog (DUDE) [action REMOTE]
In the RoS with DUDE I send those logs to disk (2000 files with 32000 lines each) [topic DUDE, action DISK]

For the desktop it is a Windows problem (multiple desktops, collapse of windows on task bar, .etc,etc... )

Seems to be an XY problem. Ask what you wish, not about winboxes.
Very true noted above, if it's just for logs, you can log to remote.

How do you all deal with keeping winbox connections open to multiple devices?

I think I speak for almost everyone,
writing that there is no one who does such a foolish thing.

As written above, explain what you want to achieve in the end, not how to correct your flaw in how you handle things.

I think I speak for almost everyone,
writing that there is no one who does such a foolish thing.

I instead suspect that there are plenty of people doing even more foolish things, only they don't have the ingenuity (or the guts) to publicly admit doing them.

Not only for looking at logs.

How do you manage multiple MT devices if not by keeping multiple instances of Winbox open?

I'd prefer not to do something foolish, so kindly share how the more experienced people do it.

Do like this

Do like this

Love it!

What are you doing that you need to be actively making changes to that many routers at the same time?
Personally I don't think i have ever needed more than two open at the same time.

What are you doing that you need to be actively making changes to that many routers at the same time?
Personally I don't think i have ever needed more than two open at the same time.

Improving, learning, experimenting, maintaining, monitoring -- that's the whole point.

Improving, learning, experimenting, maintaining, monitoring -- that's the whole point.

I thought that the point was more like improvise, adapt, overcome, let it be (i.e. have the d@mn network running, then leave it alone until/if it breaks ) .

Another tip : do not use the "admin" username. (valid for any product)
It will increase security by not using the default administrative-login user.