Столкнулся с проблемой - может кто подскажет.
Установлен mrtg.
Есть необходимость снимать показания как бит в сек.
А вопрос соб-но такой:
по target что должно передаваться в mrtg ? Передаю как бы биты в сек.
Но как заставить mrtg думать, что там именно биты ?
т.е. с масштабом не лады.

Вообще, в каких единицах измерения думает mrtg, что ему данные передаются ?
И как этим масштабом манипулировать ?

• mrtg - единицы измерения бит в сек,ksergey, 07:48 , 19-Апр-06
  • mrtg - единицы измерения бит в сек,tian, 08:01 , 19-Апр-06

Options

The Options Keyword allows you to set some boolean switches:
growright

The graph grows to the left by default. This option flips the direction of growth causing the current time to be at the right edge of the graph and the history values to the left of it.

bits

All the monitored variable values are multiplied by 8 (i.e. shown in bits instead of bytes) ... looks much more impressive :-) It also affects the 'factory default' labeling and units for the given target.

perminute

All the monitored variable values are multiplied by 60 (i.e. shown in units per minute instead of units per second) in case of small values more accurate graphs are displayed. It also affects the 'factory default' labeling and units for the given target.

perhour

All the monitored variable values are multiplied by 3600 (i.e. shown in units per hour instead of units per second) in case of small values more accurate graphs are displayed. It also affects the 'factory default' labeling and units for the given target.

noinfo

Suppress the information about uptime and device name in the generated webpage.

nopercent

Don't print usage percentages

transparent

make the background of the generated gifs transparent ...

integer

Print summary lines below graph as integers without comma

dorelpercent

The relative percentage of IN-traffic to OUT-traffic is calculated and displayed in the graph as an additional line. Note: Only a fixed scale is available (from 0 to 100%). Therefore for IN-traffic greater than OUT-traffic also 100% is displayed. If you suspect that your IN-traffic is not always less than or equal to your OUT-traffic you are urged to not use this options. Note: If you use this option in combination with the Colours options, a fifth colour-name colour-value pair is required there.

gauge

Treat the values gathered from target as absolute and not as ever incrementing counters. This would be useful to monitor things like disk space, processor load, temperature, and the like ...

In the absence of 'gauge' and 'absolute' options, MRTG treats variable as a counter and calculates the difference between the current and the previous value and divides that by the elapsed time between the last two readings to get the value to be plotted.

absolute

This is for data sources which reset their value when they are read. This means that rateup does not havt to build the difference between this and the last value read from the data source. The value obtained is still divided by the elapsed time between the last two readings, which makes it different from the 'gauge' option. Useful for external data gatherers.

unknaszero

Log unknown data as zero instead of the default behaviour of repeating the last value seen. Be careful with this, often a flat line in the graph is much more obvious than a line at 0.

withzeroes

Normally we ignore all values which are zero when calculating the average transfer rate on a line. If this is not desirable use this option.

Example:

Options[ezwf]: growright, bits

Маны-то читал, но не до конца осознал.
Если более конкретно сформулировать вопрос-то:
В каких единицах измерения воспринимает данные mrtg ? Было бы понятно, если бы у mrtg была директива на счет того, в каких единицах поступают входные данные.
Я так понимаю, он их принимает как байты. Если в опциях чтоит bits - то это значит, то умножает на 8 данные.
MaxBytes - просто сравнивает поступающие данные со значением этой директивы, и если более - то не участвуют в графике.
Верно ?