[mrtg] update to how to show 383 MB Ram in cfg file
Johannes Prost
Johannes at yorktondigital.ca
Wed Mar 21 05:40:34 CET 2007
Am 20 Mar 2007 um 22:00 hat Johannes Prost geschrieben:
short update to this:
after cut / paste the target log, it is no longer written. Is this caused by wrong values
too ? The other tragets are all updated as expected.
One mistake below, which was changed before the update:The second OID. It has to read
.1.3.6.1.4.1.311.1.1.3.1.1.1.2.0
Johannes
> Hello all,
>
> it's a stupid question, but I am relly mixed up and don't get it to work properly.
> I want to graph free & committed RAM. The OID's I have correct, but the output which mrtg
> graphs is not correct and at the same time the line is just "dead", no up's and down's so
> to speak.
> Here my cfg snippet:
>
> Target[ram]:
> .1.3.6.1.4.1.311.1.1.3.1.1.1.1.0&.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0:xxxxx at 192.168.100.20
> AbsMax[ram]: 383000
> MaxBytes[ram]: 383000
> Options[ram]: growright, gauge, nopercent, nobanner
> YLegend[ram]: RAM
> ShortLegend[ram]: B
> LegendI[ram]:
> LegendO[ram]:
> Legend1[ram]: Available RAM
> Legend2[ram]: Committed RAM
>
> The machine has physical 383 MB Ram. My log file of the cfg file says nothing about an
> error. The file with the data of the target is running every 300 sec. but the numbers are
> the same all time, no updates. So I am assuming it must have to do something with the
> coorect MB size set for MaxBytes AbsBytes.
>
> Any help very appreciate.
>
> Johannes
>
> _______________________________________________
> mrtg mailing list
> mrtg at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
More information about the mrtg
mailing list