olivier demah wrote:
Upayavira wrote:
isn't there a simpliest way ?olivier demah wrote:
Hi,
I would like to know what each of you, use to produce stats based on the logs.
Is there a tool like webalizer / awstats (used to parse apache logs) for jetty ?
if not ; how can i produce W3C log format ?
I've read http://wiki.cocoondev.org/Wiki.jsp?page=ConfiguringTheLogs but i dont see how to make log like apache ones.
You should run Apache in front of Jetty, and use Apache's logs. We use awstats, which serve us fine.
For a full discussion of why and how, see http://wiki.cocoondev.org/Wiki.jsp?page=ApacheModProxy
Regards, Upayavira
There may well be, but I've never needed to find it. Having Apache front ending Jetty might seem complex, but the benefits are huge, and I've never regretted putting it there. From modest beginnings (with Apache using mod_jk2 to communicate with Tomcat, and then Jetty), I've now got Apache forwarding requests to two Jetty instances on load balanced servers, with complex configuration scripts forwarding to different Cocoon webapps, depending upon the client the page refers to (e.g. client A gets v1.1, whereas client B gets v1.2). That would have been very difficult (if not impossible) to manage without Apache there. And also, using Apache's cool 'graceful' restart feature, I can upgrade a client from v1.1 webapp to v1.2 webapp without any downtime at all.
So I know it might not be that straightforward, but the benefits are huge. And I'm afraid I don't know of another way.
Regards, Upayavira
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
