We now exports stats, every 24 hours:
http://xw01.lri.fr:4320/stats/tables.xml
http://xw01.lri.fr:4320/stats/user.gz
http://xw01.lri.fr:4320/stats/host.gz
http://xw01.lri.fr:4320/stats/team.gz
(Directory listing is forbidden, but you can download the files: I will update server's configuration file later to enable directory listing)
XtremLab Stats Counter??
-
- Established Member
- Posts: 227
- Joined: Sat Sep 10, 2005 11:27 pm
-
- Established Member
- Posts: 227
- Joined: Sat Sep 10, 2005 11:27 pm
-
- Established Member
- Posts: 227
- Joined: Sat Sep 10, 2005 11:27 pm
As it happens, my system destroys each project's database each time a project is updated for performance reasons. It has the side effect that I don't have to handle removing old records. He he.
When updating ranks, my system only updates ranks for those accounts that have been registered to the All-In-One system, as it would take a while to caclulate ranks for all the accounts in the database!
My script does some checks - one of these checks looks for the account ID stored by the All-In-One system against the user table for the project. If the record is not found, then it aborts with an error, as it usually means that the XML stats are corrupt.
With XtremeLab starting from scratch, this check gets tripped several times! So I have added a force argument to the update script so that I can automatically purge these records from the All-In-One database.
I did this about 10 mins ago, and the latest project stats are now available, and I have re-instated the cron job for the project.
Neil.
When updating ranks, my system only updates ranks for those accounts that have been registered to the All-In-One system, as it would take a while to caclulate ranks for all the accounts in the database!
My script does some checks - one of these checks looks for the account ID stored by the All-In-One system against the user table for the project. If the record is not found, then it aborts with an error, as it usually means that the XML stats are corrupt.
With XtremeLab starting from scratch, this check gets tripped several times! So I have added a force argument to the update script so that I can automatically purge these records from the All-In-One database.
I did this about 10 mins ago, and the latest project stats are now available, and I have re-instated the cron job for the project.
Neil.
-
- Established Member
- Posts: 227
- Joined: Sat Sep 10, 2005 11:27 pm
And all done from the other side of the Atlantic, go get a beer for the good work you have doneNeil wrote:As it happens, my system destroys each project's database each time a project is updated for performance reasons. It has the side effect that I don't have to handle removing old records. He he.
When updating ranks, my system only updates ranks for those accounts that have been registered to the All-In-One system, as it would take a while to caclulate ranks for all the accounts in the database!
My script does some checks - one of these checks looks for the account ID stored by the All-In-One system against the user table for the project. If the record is not found, then it aborts with an error, as it usually means that the XML stats are corrupt.
With XtremeLab starting from scratch, this check gets tripped several times! So I have added a force argument to the update script so that I can automatically purge these records from the All-In-One database.
I did this about 10 mins ago, and the latest project stats are now available, and I have re-instated the cron job for the project.
Neil.
-
- Established Member
- Posts: 227
- Joined: Sat Sep 10, 2005 11:27 pm