multi-level map?

[mstyslavd]

Hello,
long been interested in the ability to create complex maps (multi-level)
what I mean?
There are devices, say the city level, below the city level, lower than the level of the house or office.
I want to display only the city level by default, and have all the lower levels minimized and open / hide as needed (if problems arise) on the same map.
why?
because such devices in the network can be 1000 or more and the simultaneous display of everything complicates the general perception.
is it possible?
thank!

[Howie]

You can make multiple maps at different scales and link between them... just use a node with INFOURL set to the other map's url in Cacti.

You will have to work out the scales etc yourself though.

[mstyslavd]

You can make multiple maps at different scales and link between them... just use a node with INFOURL set to the other map's url in Cacti.

You will have to work out the scales etc yourself though.

thank!
at the moment i have done so. although this is not exactly what I wanted. In addition, this option does not quite solve my problem.
Perhaps in the new versions you can work in this direction?

[Howie]

What direction, though?

Describe exactly how you think you'd configure this in a map, and how it would work for someone interacting with the map...

Do items just disappear and reappear as you zoom in? What about links that go to that item? Would it be zoom, or some kind of 'detail' slider?

Something else?

It's not something where it's obvious how it should work.

[mstyslavd]

What direction, though?

Thank you for your attention to my question!

I imagine this as additional map layers.
we have a top layer "city", on it nodes are put. each such node has lower level nodes. they are located on the layer "district". and so on, there may be several layers (city, district, quarter, house)
each layer has its own nodes
All this can remind a little of the directory system in the PC file system.
In addition, it would be nice if a notification was displayed on the top level layer in case of problems on the lower level layer
as you probably understood, I see the use of this functionality as a monitoring system of a distributed tree structure

[Howie]

OK, but:

1) what about links between layers? (e.g. the edge router for a POP that links to the backbone)

2) Weathermap doesn't know what a "problem" is. All it does is turn numbers into colours. I did start adding the concept of groups at one point, so that you could do things like "average traffic_in of all nodes in group 'transit'". That might allow for the definition of a "summary node".

If you did this as literal layers, using the existing ZORDER command, it wouldn't be very hard to have weathermap not draw items in e.g. 200 < Z < 400, but you would have strange things happen with links, and you would also need to have a map big enough to hold all those missing elements anyway - that is, in the editor, you'd see everything.

[Howie]

(Sorry, cut that short)

My point about the editor is that if you *don't* do it so that you are leaving space for those other elements, and do some other "magic" to rescale/redraw as things are added and removed, how is that different from using multiple maps as you do now? It would be about the same effort to maintain the different views, if they are in one map or multiple. Multiple might even be less confusing to edit...

Glad to discuss it!