[rt.blitzed.org #365] per-server user counts for web site
"Andy Smith via RT" <[email protected]>
| Newsgroups | gmane.network.irc.blitzed.web |
|---|---|
| Message-ID | <[email protected]> |
Mon Mar 08 15:37:03 2004: Request 365 was acted upon.
Transaction: Ticket created by grifferz
Queue: web
Subject: per-server user counts for web site
Owner: Nobody
Requestors: [email protected]
Status: new
Ticket <URL: http://rt.blitzed.org:80/Ticket/Display.html?id=365 >
15:28:13 < mark> but per server stats would be nice
15:29:11 < mark> and useful
15:29:48 <@grifferz> mrtg writing into rrds or just a perl script updating rrds?
15:29:58 < mark> latter
15:30:04 < mark> rrd graphs are more flexibile
15:30:09 < mark> -i
15:30:11 <@Silencer> mark is anti mrtg I guess :(
15:30:18 < mark> no
15:30:39 < mark> mrtg is nice for what it was designed for
15:31:35 < mark> we could make a stacked graph with total users
15:31:36 <@grifferz> so how would it work.. every 5 mins a perl script looks at all servers in thales, then reads user count for each, updates an rrd by server name or else creates it if it doesn't exist?
15:31:39 < mark> each server a separate color
15:31:47 < mark> yes
15:32:16 <@grifferz> what about servers that delink.. will they stay there or be deleted somehow?
15:32:24 < mark> we could do that manually
15:32:29 < mark> it's not really a problem
15:32:32 < mark> rrds are small anyway
15:32:43 < mark> the web page can make sure they aren't visible
15:34:19 <@grifferz> how would the web page know which servers should be visible?
15:34:50 < mark> thales?
15:34:56 < mark> or whatever
15:34:58 < mark> some blitzed db?
15:35:04 <@grifferz> right
15:35:21 <@grifferz> same way as the server list then
15:35:24 < mark> yes
15:35:25 <@grifferz> seems reasonable
15:35:30 <@grifferz> I will probably have a go at this
15:35:36 < mark> cool