Cheshire Cat Computing

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Any chance you've had the opportunity to test this out yet.

Back in work today, and I've been able to test it out.

It appears you have located a genuine bug... the groupsep option does work, but if you are using default group names (the last component of the directory name containing the cfg files) then the directory name is truncated *before* applying the group split. This problem seems to have managed to get inserted in a couple of versions back and not noticed.

So, I'm working to make a fix now which shouldnt be too hard. I can let you have beta6 if you want when the fix is done.

A workaround is, of course, to define explicit group names in the routers2.conf, and multilevel will correctly split these according to the groupsep character (so the bug is, technically, in the bit which calculates the default group names, not in the multilevel code, although it makes no difference to you)

Let me know if you want the beta with the fix when it becomes available. Thanks for reporting this problem so I can fix it!

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

OK, I have a fix in v2.18beta5

This wasn't too hard to do (just change basename() into a function to strip confpath from the front for the default group name) but was a bit awkward to track down in the code. All seems OK now. If you want a copy, email me.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I'm trying to do something similar but can't get my head round how to do it!

I've got all my mrtg.cfg files in a directory with the .rrd files in subdirectories below, one subdirectory per device. I've also created some cfg files containing a subset of devices and/or targets with include statements to bring in the bits of config file I need - e.g. one of these contains all devices for a specific part of my organisation and another contains constructed graphs showing both inputs and outputs on specific pairs of connected targets, i.e. 4 plots per graph using mirror format, very pretty. These extra config files are in subdirectories under the main cfg file directory.

The multi-device graphs work well as there aren't many so they are all comfortably displayed on one page. However, the subsets of devices are quite large and have non-unique port numbers so I really want these to be grouped together in the left hand menu so that the individual devices can be selected.

I've set group and multilevel and targetnames and tried all sorts of settings but all I ever get is a single entry on the devices menu and a long list of targets in the right hand menu. Am I doing something really silly?

I'm running 2.18 beta5.

Hope this make sense.

cheers

Steve

The Grouping (with or without Multilevel) groups the Devices (ie, the cfg files) by directory in the lefthand menu.

The Targets menu contains one entry per Target[] in the selected cfg file, apart from target[]s with routers.cgi*InMenu[]:no and routers.cgi*Ignore:yes. The Targets menu cannot be grouped in this manner.

To group the Devices menu, you create separate directories (or subdirectories) and place the cfg files into the appropriate directory, then (optionally) set an additional description for the directory in the routers2.conf. Multilevel grouping will split the groups based on the separator character in the descirption.

To group the Targets, the only way to do it is to remove the Target from the menu (using routers.cgi*InMenu[]:no) and the create one or more userdefined Summary pages, and place the Targets into those. For example, we have all our oracle-related Targets set with InMenu[]:no but also 'routers.cgi*Summary[]:oracle nodetails' . This creates a userdefined summary page, 'oracle', with only graphs and it can be used as a second-level menu.

In the case of interfaces (eg, on a switch) you can also use the 'active' keyword, which suppresses the graphs/lines of any Target which has zero activity during the time period (so you can hide the graphs of switch ports which are not in use).

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11