Is there any examples for setting up Netmrg to say graph the number of users currently connected to a port or a series of ports on a server?
What type of platform are you wishing to run this on?
On a Linux platform, it would be possible to do this with NetMRG. A small custom script would be needed to handle this, but would be fairly easy to write.
Yes, Linux -- Suse Professional 9.0.
The intended use for the script is that the server will be a dedicated game/mud hosting server and I would like to see how many gamers are connecting to all the gameworlds we have available.
As I am a newbie to snmpd, rrdtool, mrtg, and this tool... might as well start here and see if this will work in the long run for support or possibly adjusting some of the hosting packages I intend to offer.
I know this information is available in 'netstat', and I'm pretty sure you could pull this from SNMP as well. The only real problem is the fact that you need to count the number of connections per port, so it's not something that would be built in to NetMRG already, and would have to be a custom script (which is why we support custom scripts).
How would something like this work for you? I assume you run certain types of game servers on certain ports; does a particular game server run on multiple ports, or does each game server listen only on one port (the later would be slightly easier to implement)? I was envisioning something like
[code19cb1519429]sumConnections.pl -p 5113 -h localhost -c public[/code19cb1519429]
and this would return a number like '22' that NetMRG could graph. the '-p 5113' would be the port the server listens on, the '-h localhost' could would be the host running the server (and SNMP), and '-c public' would be the SNMP community string. The script would connect via SNMP and gather the information and count up the connections, and return the value.
Does this sound like the situation you're in?
I run a series of muds on the server so each normal account would have their game running on say port 1501. (Development ports would be like 1502, and so on).