helpful for error/warn from things, but NOT for sending MBs/GBs of logs and excepting it to be useful to search/manage/etc. It is also a syslog server, so you can always use it as remote log destination – they don't have a lot of tools to mange them, but possible – e.g. See my post about LTE tracking here: viewtopic.php?t=192103&hilit=dude+lte If you want to customize the device labels to show your own things. Beyond the link, more advanced monitoring is possible the 'probes' – that more complex, plenty of examples here: viewtopic.php?t=12402 – since they haven't changed much in 10+ years, likely most still work if you have other device types to monitor BUT complex.
You can further use a 'submap' via the same '+' so you click through to another map, or have a 'meta map' that has submap links to all the other maps to get overview of status. If you want to monitor devices on each of those routers, it's often helpful to create a NEW network map on a per-subnet & if desired you can enable discovery of new device on that map, for that particular subnet – this avoid a mega-map with too many item.
If you enable SNMP on the individual routers, by default it will show CPU/memory for the devices on the map & in general Dude likes to operate with SNMP not RouterOS commands.