[mrtg] Re: Newbie OS X User

[Dan Tappin]

Thanks for the help Drew.

I had MRTG running already but the package I installed set-up a
preconfigured SQUID cache CFG that is a good start for me to dig through.

I do not have much experience with SNMP so here is a dumb question...

My SQUID cache example...

The mrtg-squid.cfg file has the following line:

Target[cacheServerErrors]:
cacheServerErrors&cacheServerErrors:public at localhost:3401

So this means that MRTG is asking public at localhost:3401 for
cacheServerErrors data?  What is the structure on the
<<handle1>>&<<handle2>> in front of the address?

The OS X system I am playing with acts as our office router, webserver,
e-mail, and DNS server.  I am assuming that I could monitor each of these
with MRTG?

I have also seen CPU and disk usage which would be cool.  We also have an
office with 40+ PC sharing this connection.  Could I also use MRTG to
monitor web / e-mail traffic on them or does MRTG need to be running on each
system being monitored?

I have a lot of things I would love to add to this but I think I am turning
this into quite a make work project!  To start I would like to monitor the
TCP/IP traffic in and out of the office and the servers CPU and memory usage
and uptime.

Are you using OS X?  Do you have some example CFG files you would be willing
to share with me?

Thanks for all your help.

Dan

> It's easy to make something that is easy really difficult.
> 
> If you have mrtg, perl and a web server installed, the only thing left to do
> is tell mrtg what device and what information you want to monitor.  mrtg then
> creates simple html pages that you can then view through a web browser.  (You
> know all of this already, I know).
> 
> So, you first run a script which creates a configuration file vaguely similar
> to the following:
> 
> cfgmaker --global "WorkDir: \http\html\mrtg" --global "Options[_]:
> growright,bits" public at 192.168.1.25
> whatever_name_I want.cfg
> 
> Broken down into plain English:
> - Run the cfgmaker script
> - With these options
> - On this device
> - And create this output file
> 
> It's easy to get lost in the forest because of the trees, so forget about the
> options for the sake of understanding.  You could run:
> 
> cfgmaker public at 192.168.1.254 --output filename.cfg
> 
> This is the same command with no options and will run just fine.  The only
> problem here is that you want your html files to end up in a certain
> directory.  That is the function of the --global "WorkDir: \blah\blah" option
> listed above.  Simply put in the directory where you want your html files to
> go.
> 
> Also, you might want your graphs to go from right to left and be in bits
> instead of bytes (or maybe not, it's up to you).  That's why they call them
> options, they're all optional.
> 
> You now have a configuration file (which you can later change manually, or
> change through running the cfgmaker script again.
> 
> Now all you need to do is run mrtg using this freshly minted configuration.
> 
> mrtg your_config_file_name.cfg
> 
> Simply; "run mrtg and use the config_file_name.cfg" file.  This will run mrtg,
> collect info from the device listed in the config, and output html files to
> the directory you specified to cfgmaker.  All you need to do now is point a
> web browser to the files that were created and see the magic.  (Remember that
> you'll have to run mrtg a couple of times over the period of a few minutes
> before you see any data.)
> 
> Don't worry about indexmaker yet.  Get mrtg to run with a config that you've
> created.  Once you can view the graphs, then move on to indexmaker.
> indexmaker does not create any new data, it simply organizes what you already
> have created.  So, don't worry about organizing what you don't have.
> 
> Drew Hawn
> Santa Barbara


--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi