Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 17693 invoked from network); 30 Jul 2009 22:12:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Jul 2009 22:12:25 -0000 Received: (qmail 14553 invoked by uid 500); 30 Jul 2009 22:12:25 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 14444 invoked by uid 500); 30 Jul 2009 22:12:25 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 14416 invoked by uid 99); 30 Jul 2009 22:12:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jul 2009 22:12:24 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jul 2009 22:12:13 +0000 Received: from [90.152.138.125] (mk090152138125.a1.net [90.152.138.125]) by indoqa.com (Postfix) with ESMTP id AC96B1A0001 for ; Fri, 31 Jul 2009 00:11:50 +0200 (CEST) Message-ID: <4A721AA6.8010308@apache.org> Date: Fri, 31 Jul 2009 00:11:50 +0200 From: =?UTF-8?B?UmVpbmhhcmQgUMO2dHo=?= User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [c3 monitoring] Statistics module. References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Dariusz Łuksza wrote: > Hi all, > > Currently I'm finishing milestone 3 (actually it is "cache overview") > of my GSoC project and I've started to wondering about last part of > this project: statistics module. > > I want that this module would be as much useful as it could be, so the > main question is what statistics should be exposed in this module ? > > One proposition is monitoring of cache. Showing what cache entry's are: > * most often read > * most often generated > > I think that having some informations about pipeline usage would be > also useful. Right now I think that exposing hit count for every named > (it means that it has set "jmx-group-name" parameter) pipeline. This > would be useful for proper cache configuration. > > Any other propositions ? I think it is a good idea to get an overview of all cache entries that are never used at all. Also a general request counter would be useful (number of request in the last 5 minutes, 60 minutes, 24 hours, since system start). Finally a list of all available properties (see the settings bean) would be a good idea. -- Reinhard Pötz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinhard@apache.org ________________________________________________________________________