Page 1 of 1

one mrtg graph for many links (consolidated graph)

Posted: Sat Dec 13, 2014 1:29 pm
by zaji_nms
Dear Expert

We desperately looking one (just one In/Out graph) of our 9 STM links, how possible from NagiosXI to combine all the values and give just one consolidate MRTG (aggregate value)

There is many links but here for example purpose taking two

First Link In : 0.8Gbps ,, Out : 1.5Gbps
Second Link ,, In : 0.9Gbps ,, Out : 1.9Gbps

so it should just one simple In/Out graph with values : In=1.7Gbps ,, Out=3.4Gbps (don't want multiple graph lines, just two lines, one for In , another for Out)

Regards

Re: one mrtg graph for many links (consolidated graph)

Posted: Mon Dec 15, 2014 11:16 am
by tmcdonald
In order for a graph to be made, MRTG has to run a check against a single network interface. It then writes the data to a RRD file, and Nagios runs a check against that RRD to build the graph.

A plugin would need to be created that can check multiple RRDs and add up the values, then store them into yet another RRD for the final result.

Re: one mrtg graph for many links (consolidated graph)

Posted: Mon Dec 15, 2014 12:32 pm
by zaji_nms
Dear tmcdonald

Is there any luck to get that, is it available? If not , hope in next version of NagiosXI its there.

There should be option for consolidate MRTG with Service Group, whatever services are there in that group, just aggregate. (if mixed services are grouped, just add MRTG whatever possible in similar group)

Regards

Re: one mrtg graph for many links (consolidated graph)

Posted: Mon Dec 15, 2014 2:11 pm
by sreinhardt
There is no plugin that I know of to do this. At this time, such a plugin is not planned, and I'm not sure if it would be written. We do have some alternative interface checks in the works, but they will not likely be available until 2015. As always, you are more than welcome to post a feature request on tracker.nagios.com or speak with [email protected] for custom development. This would likely be a rather small project if you went the custom development route.

Re: one mrtg graph for many links (consolidated graph)

Posted: Tue Dec 16, 2014 4:51 am
by zaji_nms
Dear sreinhardt

We did many tiny (one word , one/two lines) changes in PHP/Perl Script and somehow its ease our work but when we upgraded the version all gone, so its really discourage to do so. I managed myself otherwise we have to take help of some Expert and will cost every time there is upgrade.

So I hope, this minor changes, customization, should come from NagiosXI itself and will remain till customer is there, NagiosXI is there.

Regards

Re: one mrtg graph for many links (consolidated graph)

Posted: Tue Dec 16, 2014 10:13 am
by tmcdonald
In order to get the latest versions of plugins, we will of course need to overwrite the old with the new on an update. If you wish to keep the old modified versions of plugins, it is always a good idea to keep backups and restore them after an update.

Re: one mrtg graph for many links (consolidated graph)

Posted: Tue Dec 16, 2014 1:47 pm
by zaji_nms
Dear tmcdonald

Please close the case, me feel comfortable with this Forum as quick reply from you all (Experts).

Whenever you feel its good idea, suggestion, please you (all of you), forward our advice/suggestion/complaint to NagiosXI developer team.

FYI, all of user not reporting the issue, they keep quite, if there is some feature they will use, otherwise carry on....so whoever asking the small feature are less compare to who will use.

Please close this post.

Regards

Re: one mrtg graph for many links (consolidated graph)

Posted: Tue Dec 16, 2014 3:59 pm
by tmcdonald
I certainly understand your meaning, and I would like to assure you that we file internal feature requests frequently when we feel the suggestion would be a good addition to the product. We cannot, of course, implement 100% of suggestions, but we do consider every feature request that comes through.

We also have our public feature request site: http://tracker.nagios.com

You are more than welcome to file feature requests there if we have not done so internally, and our developers will still take a look at them. They may or may not get implemented, and if they do it may not be right away, but we do keep an eye on things.