Previews: July 2007 Archives
Recently I've been working on a new version of my webcam software for Snyggast Chatten. Basically it allows our users to broadcast their webcams and view others. Here is a quick GUI preview:

The new system is re-written from the ground up. The GUI is better, users can report rule violations, we can maintain bans easier. Everything is simply better. More information will follow..

The new system is re-written from the ground up. The GUI is better, users can report rule violations, we can maintain bans easier. Everything is simply better. More information will follow..
Introduction
There are many good sites for website statistics. Tools such as Google Analytics are invaluable for any webmaster. But how do you measure the success of a chat? a IRC system? While total number of users per day is interesting, the real value is in the current number of users combined with other factors.
Helios, our new statistical software I've been working, is an internal tool for us on Snyggast Chatten. It collects data every five minutes, pretty much like mrtg. MRTG stands for Multi Router Traffic Grapher, and outputs images like this:
Where a webmaster can easily overlook the network usage of a particular server. The idea is to output similar graphs but include data such as current numbers of users, ram usage, etc.
Collected data
Currently we are collecting the following data every five minutes:
Relations, the real power
The real power of Helios is relations. In a 24 hour graph we can not only see where our tops are, but also the relationship between numbers of users and, for example, free ram. This provides us with valuable information about how the server feels but also how much a particular optimization gave us.
The actual charts
I've built the system around the open source grapher Open Flash Charts. It's a flash grapher, and it's open source. Since we will be measuring numbers of users (0-600) and it's relation with ram usage (0-2500 MB free) we need double Y-axes. The problem is that not many (if any) grapher actually supports this by default. But since Open Flash Charts are open source I could implement it myself. Turns out that many other users have been asking for this feature for a long time and my double y-axes code will be integrated in the next release of the software. It's always good to be able to contribute to projects..
Sample Chart
This is how the system currently looks:
At a first glance it's quite blurry and might be hard to see the relations. This is because the large number of data we actually need to see. The main line (with the dots) are numbers of chat users, the smaller line with dots are numbers of webcam users and the other 2 lines are how much ram we have left.
Why the name Helios?
In greek mythology, Helios is the sun god and referred to as the "the all-seeing". A fitting name for a system which idea is to monitor and see pretty much everything.
There are many good sites for website statistics. Tools such as Google Analytics are invaluable for any webmaster. But how do you measure the success of a chat? a IRC system? While total number of users per day is interesting, the real value is in the current number of users combined with other factors.
Helios, our new statistical software I've been working, is an internal tool for us on Snyggast Chatten. It collects data every five minutes, pretty much like mrtg. MRTG stands for Multi Router Traffic Grapher, and outputs images like this:
Where a webmaster can easily overlook the network usage of a particular server. The idea is to output similar graphs but include data such as current numbers of users, ram usage, etc. Collected data
Currently we are collecting the following data every five minutes:
- IRC data (Numbers of users, users in both public channels, active admins, webclient users)
- System data (Ram usage, HDD usage, CPU usage)
- Webcam data (Numbers of webcam users
Relations, the real power
The real power of Helios is relations. In a 24 hour graph we can not only see where our tops are, but also the relationship between numbers of users and, for example, free ram. This provides us with valuable information about how the server feels but also how much a particular optimization gave us.
The actual charts
I've built the system around the open source grapher Open Flash Charts. It's a flash grapher, and it's open source. Since we will be measuring numbers of users (0-600) and it's relation with ram usage (0-2500 MB free) we need double Y-axes. The problem is that not many (if any) grapher actually supports this by default. But since Open Flash Charts are open source I could implement it myself. Turns out that many other users have been asking for this feature for a long time and my double y-axes code will be integrated in the next release of the software. It's always good to be able to contribute to projects..
Sample Chart
This is how the system currently looks:
At a first glance it's quite blurry and might be hard to see the relations. This is because the large number of data we actually need to see. The main line (with the dots) are numbers of chat users, the smaller line with dots are numbers of webcam users and the other 2 lines are how much ram we have left.
Why the name Helios?
In greek mythology, Helios is the sun god and referred to as the "the all-seeing". A fitting name for a system which idea is to monitor and see pretty much everything.
Recently I implemented support for double, stand-alone y-axis in Open Flash Charts. Turns out that John Glazebrook (main coder) has gotten "LOTS of requests for 2 Y axis" and my contribution will be included in the next release of Open Flash Charts. That way all users can benefit from my modifications..
Technical details (to other Open Flash Charts users)
If you want to try out double y-axis before the next release, download my open-flash-chart.swf and add this to your data file:
&y2_axis_colour=#164166& // Same as regular documentation
&y2_label_style=10,0x164166& // Same as regular documentation
&show_y2=true& // Do we use double axels?
&y2_lines=1& // Which of the lines should be drawn based on the y2-axel? (1,2,3 etc)
&y2_left=70& // Left margin (how far left should we push the regular content)
&y2_min=0& // Same as regular documentation
&y2_max=2400& // Same as regular documentation
&y2_legend=Free Ram (mb),12,0x164166& // Same as regular documentation
Good luck! If you got any questions, simply contact me
Technical details (to other Open Flash Charts users)
If you want to try out double y-axis before the next release, download my open-flash-chart.swf and add this to your data file:
&y2_axis_colour=#164166& // Same as regular documentation
&y2_label_style=10,0x164166& // Same as regular documentation
&show_y2=true& // Do we use double axels?
&y2_lines=1& // Which of the lines should be drawn based on the y2-axel? (1,2,3 etc)
&y2_left=70& // Left margin (how far left should we push the regular content)
&y2_min=0& // Same as regular documentation
&y2_max=2400& // Same as regular documentation
&y2_legend=Free Ram (mb),12,0x164166& // Same as regular documentation
Good luck! If you got any questions, simply contact me
