From: andreas.papst@UNIVIE.AC.ATSubject: MRTG stuff for SQUIDHello,I use MRTG for monitoring squid. With squid 2.0 release you canuse SNMP-requests for this task.Based on the works of:matija.grabnar@arnes.si(http://www.arnes.si/~matija/mrtg-for-squid-0.3.tar.gz),kostas@nlanr.net(http://ircache.nlanr.net/Cache/Statistics/mrtg/mrtg-squid-patch)and possibly others, I patched MRTG to satisfy the new squid 2.0requirements and added some features, that I thought MRTG musthave.So I have add new code for displaying correct units to theprevious patches "perminute" and "perhour" ("option" tokens),which allow to mesure not only per second.Then I have created a new option token "dorelpercent", whichallows to caclulate the percentage of IN-stream / OUT-stream onthe fly and display it on a fixed scale from 0% to 100%. For myrequirements, this does good work. Maybe someone wants a floatingscale, it should not be a problem to implement it too. But thengive me an option to keep my fixed scale. If IN-stream is alwaysless than OUT-stream both lines (OUT-stream and relative percent)are always displayed on top of IN-stream bulk. Otherwise thisoption makes no sense. With this option you can display hitrates,errorrates (for router monitoring: rel. droprates) easily now.If you use this options please consider, that you need a 5thcolourname/value pair in your Colours statements!Due to some discussion on this list, I have implemented twotokens too:"kilo" and "kMG""kilo" should contain the value of k (1000 or 1024), where 1000 is thedefault."kMG" is a comma separated list of multiplier prefixes, usedinstead of "", "k", "M", "G", "T" on the MRTG display. Leave theplace free, if you want no prefix.Also a not complete list of OIDs for the new SQUID release isadded.I hope you enjoy it.Examples for mrtg.cfg:You can measure now responsetimes in ms and display it with MRTGcorrectly with:kMG[measure-ms]: m,,k,M,G,Tshort[measure-ms]: sYou can display now MB/s as 1024*1024 B/s with:kilo[volume]: 1024A sample config for squid:Target[proxy-hit]: cacheHttpHits&cacheClientHttpRequests:public@proxyTitle[proxy-hit]: HTTP HitsPageTop[proxy-hit]: <H2>proxy Cache Statistics: HTTP Hits / Requests</H2>Suppress[proxy-hit]: yLegendI[proxy-hit]:  HTTP hitsLegendO[proxy-hit]:  HTTP requestsLegend1[proxy-hit]:  HTTP hitsLegend2[proxy-hit]:  HTTP requestsYLegend[proxy-hit]: perminuteShortLegend[proxy-hit]: req/minOptions[proxy-hit]: nopercent, perminute, dorelpercentTarget[proxy-srvkbinout]: cacheServerInKb&cacheServerOutKb:public@proxyTitle[proxy-srvkbinout]: Cache Server Traffic In / OutPageTop[proxy-srvkbinout]: <H2>Cache Statistics: Server traffic volume (In/Out) </H2>Suppress[proxy-srvkbinout]: yLegendI[proxy-srvkbinout]:  Traffic InLegendO[proxy-srvkbinout]:  Traffic OutLegend1[proxy-srvkbinout]:  Traffic InLegend2[proxy-srvkbinout]:  Traffic OutYLegend[proxy-srvkbinout]: per minute#ShortLegend[proxy-srvkbinout]: kb/minShortLegend[proxy-srvkbinout]: b/minkMG[proxy-srvkbinout]: k,M,G,Tkilo[proxy-srvkbinout]: 1024Options[proxy-srvkbinout]: nopercent, perminuteandreas.papst@UNIVIE.AC.AT