>Как МИБы в файле конфигурации мртг подцеплять?
А что зайти на www.mrtg.org уже модно?
# * You can also explicitly define the OID to query by using the
# following syntax 'OID_1&OID_2:community@router'
# The following example will retrieve error input and output
# octets/sec on interface 1. MRTG needs to graph two values, so
# you need to specify two OID's such as temperature and humidity
# or error input and error output.
# Target[ezwf]: 1.3.6.1.2.1.2.2.1.14.1&1.3.6.1.2.1.2.2.1.20.1:public@myrouter
# * mrtg knows a number of symbolical SNMP variable
# names. See the file mibhelp.txt for a list of known
# names. One example are the ifInErrors and and ifOutErrors
# names. This means you can specify the above as:
# Target[ezwf]: ifInErrors.1&ifOutErrors.1:public@myrouter
# * if you want to monitor something which does not provide
# data via snmp you can use some external program to do
# the data gathering.
#
# The external command must return 4 lines of output:
# Line 1 : current state of the 'incoming bytes counter'
# Line 2 : current state of the 'outgoing bytes counter'
# Line 3 : string, telling the uptime of the target.
# Line 4 : string, telling the name of the target.
# Depending on the type of data your script returns you
# might want to use the 'gauge' or 'absolute' arguments
# for the "Options" keyword.
# Target[ezwf]: `/usr/local/bin/df2mrtg /dev/dsk/c0t2d0s0`
# * You can also use several statements in a mathematical
# expression. This could be used to aggregate both B channels
# in an ISDN connection or multiple T1's that are aggregated
# into a single channel for greater bandwidth.
# Note the whitespace arround the target definitions.
# Target[ezwf]: 2:public@wellfleetA + 1:public@wellfleetA
# * 4:public@ciscoF
Это вырезка из mrtg.cfg.sample.