Don’t think so, someone managed to add it to their dashboard via external image, not sure if you can put a title on the widget, haven’t tried it. I’m using How to add a custom menu item to categorize aggregates.
Also you might be interested in showing the Aggregate Totals and Volume Totals, so change your URL like this
Just beware if you do it this way , ignore the right side column for total volume per interface, these numbers are incorrect on my instance, don’t think it was designed to jam nototal=0 into the url bar for combined graphs.
However doing so will get you a correct aggregate volume at the bottom and that’s what matters.
Two other options you may want to consider - you can create “bills” and add whatever interfaces to them you like, or set up ports with specific tags similar to what Chas has suggested that will allow them to be marked as transit, peering, or core interfaces in your config file.
Just bringing this up again, I’m trying to fix the “generic_multi_bits_separated.inc.php”, but if some one can also confirm they also see the same issues;
I believe this is the bad data in the aggregate graph view with noagg=0 and nototal=0;
Per-line aggregate Total figures can be corrected if divided by 8 (this looks to be because “generic_multi_bits_separated.inc.php” is multiplying to get Bytes, but for some reason is also double multiplying the totals?)
MAX peaks are not preserved in the aggregate view, and are more obvious in a Year/Two year view, in comparison to a Single graph Year/Two year view.
Aggregate Maximum must be using AVERAGE instead of MAX. MAX is never fetched in the DEF. I believe MAX should be fetched to preserve peak traffic like it does in “generic_data.inc.php”.
Historic Max peak data is shown correctly on individual interfaces (ports_bits) - and LibreNMS preserves max peak through RRD sampling overtime… which is awesome
but for Historic aggregates (multiport_bits), Max peak is incorrect (looks to me like it’s actually displaying the average) I think this is just a code issue in multiports_bits that needs changing. For the last 1 month it’s fine but anything older looks to be incorrect. You can compare this by checking an aggregate graph, and then the individual graph inside that aggregate 6 months ago.