[discore]

Originally Posted by Dave#

The script only allows one value for $data and this gets passed to mrtg - this is fine but I have modified your script to graph some other data like registered users, totposts and total threads

http://www.fu-1.net/mrtg/regusers.html
http://www.fu-1.net/mrtg/totposts.html
http://www.fu-1.net/mrtg/totthreads.html

I'd like to be able to graph threads/posts on the same graph but am struggling with the Perl

2 things is no problem. MRTG can't graph more than 2 things at a time (as far as I know). Maybe other graphing programs like Cricket are more flexible, not sure.

But we can at least combine Total Posts/Threads. Use this script which adds a new "totaltp" section and makes displaying 2 numbers possible. Then add this to your MRTG config file:

# Total threads/posts
Target[totaltp]: `/etc/mrtg/vB.pl totaltp`
MaxBytes[totaltp]: 10000000
Title[totaltp]: Total Threads/Posts
PageTop[totaltp]: <H1>Total Threads/Posts</H1>
ShortLegend[totaltp]: Threads/Posts
YLegend[totaltp]: Threads/Posts
Legend1[totaltp]: Total Threads
Legend2[totaltp]: Total Posts
LegendI[totaltp]: Threads
LegendO[totaltp]: Posts
Options[totaltp]: growright,nopercent,gauge

Changing the the path to vB.pl of course. That will give you graphs that look like this. Doesn't look that great with my board's 1:20ish thread to post ratio, but the new code and configuration should make further modifications easier.

Originally Posted by Dave#

Also do you know how to to stop MRTG converting values into K ie 6.4K rather than 6,400?

The best way I've found is by adding:

kMG[totaltp]: ,,

To the MRTG config. "totaltp" gets replaced by whatever label is appropiate. This doesn't change the digits on the YLegend (left side digits on the graphic), probably because they'd get too big to fit in the image. All of the configuration directives can be found here. Maybe there's a better way.

Originally Posted by Dave#

Finally I am using this remotely so your script calls uptime on the box running mrtg not the mysql box

Hehe, you could maybe run SNMP on the database server and rewrite the script to get date/time of remote machine via SNMP, but that's quite a bit of work for something as arbitrary as uptime. You're probably best off simply adding "noinfo" to the Options for each label to supress the whole bit about uptime.