knobdy wrote:Sorry, but I have another request - if possible. How about a "call-out" that can be attached to a link or node and used to describe them in greater detail than the label can but not an image or snapshot like the hover popup is. Something akin to what you might see on a flow chart or the like. My use would be, for instance, on a secondary link I have to a failover firewall - which should never see any traffic unless we have a problem.
OK - but two questions: what should it do when you have an OVERLIBGRAPH as well (which you probably would want for a link), and how do you see it being configured? Is it fetching text from elsewhere, or one line specified in the config? Or some more complex HTML-style thing?
Another possible use - or a seperate addition for that matter - is a way of stating port numbers/names. It would be nice if it could pull the info directly from Cacti too - but since this is pretty close to a physical network diagram (depending on how you use it) that additional level of feedback would be excellent.
This is what I was thinking about. Someone on the mailing list asked for a similar thing, and I was playing with it before that... something that took (for example) the Cisco interface description line. I experimented at one time with having text drawn along the side of the link arrows, to allow this kind of comment text, but it had a few drawbacks: first, you
must use a freetype font to get the rotation required. second, freetype is not always very good at small text, especially rotated small text. finally, I did all that before I added curves, which make the whole thing more complicated
I wouldn't mind being able to add switch port references and telco circuit references into my maps, too, but I don't want to have something that's either overly complex or so simple it doesn't do enough and keeps being patched and tweaked.
There's a similar chain of 'would be nice' stuff for changing the colour of nodes based on some NMS data (e.g. Nagios state). Suddenly there's a whole slew of stuff that's needed just to support the 'small thing'
Anything like that makes the day that the editor supports everything disappear into the distance too, unfortunately.
It needs a bit of designing/planning.