Forum OpenACS Q&A: Monitoring

I find the monitoring package highly useful, especially when it is sending out reminders of errors happening on the site. Very good to see what is happening on the production site while you are not watching 😊. I was wondering though if there is a general rule to follow to make it available to the 5.3 release. Should it be imported into the oacs-5-3 branch, or should it just be tagged as openacs-5-3-compat?

In the long run we might think of making the monitoring package part of core, as we might do with the request monitor, as both give highly useful informations also to new users of OpenACS who want to see what is happening on their site. The missing link would be an OpenACS awstats package that analyzes the log files, bringing you (in conjunction with the other two) information on:

* What is happening at my site at the moment (request-monitor)
* How many users are accessing my site on average
* Where do my users come from
* What are the most accessed areas on my site
* What scheduled procedures are running in the background
* What errors happen on my site while I am asleep

Note, that none of these tools use the monitoring packages that are e.g part of .LRN giving more information about usage of OpenACS users. I hope to learn more about them and discuss (if time permits) good solutions during the conference in Vienna and the session on "Tracking users in OpenACS/dotLRN"

Hi Eduardo, I was about to test it again, sadly I cannot access it.

Is there any reason why your are not releasing your improvements on CVS HEAD then I could actually check it out on one of our instances and help clean up the code / make it generally applicable.

Hello Eduardo, can you send me the diff to the current version from HEAD so I could apply it? I added a couple more things to it so I am careful not to overwrite things.

Hmm.. the login does not seem to work. Can you make a tarball available ?