Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 5598 invoked from network); 18 Feb 2010 13:52:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Feb 2010 13:52:16 -0000 Received: (qmail 81885 invoked by uid 500); 18 Feb 2010 13:52:15 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 81808 invoked by uid 500); 18 Feb 2010 13:52:15 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 81800 invoked by uid 99); 18 Feb 2010 13:52:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2010 13:52:15 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [209.191.125.66] (HELO web38605.mail.mud.yahoo.com) (209.191.125.66) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 18 Feb 2010 13:52:07 +0000 Received: (qmail 56981 invoked by uid 60001); 18 Feb 2010 13:51:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1266501105; bh=C6e2X4fu3343Q0dbQ81B8ZaYxjqVuM9RvSjMurynAGI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=dmHGn7rmbK5pn7fvMr/egiPeA77qwiNt9c8qRl4XKmiYixGvUTHnFJWZg5EKgYORHEzPVRu0RCeSbRW8cN9KtYqQiUC+6l1lR/MULuflninK3jtxy2dwCIrqoHhrqgfxFhZfq+Gyyp4rLA5Mnc/QoUTJK93L+6JkO33kaYeekWk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=FRL0uxSK2BckCjVsazRr7lkCe3VftPpGUPTz6vGhDkWP3UyMRw0lwR/Y39kSDHi3rP5VXUHgpTCI0mU1gm2nkdtlR8PL5vCXVqpBcaHzyonwFjLaz4g4MeWKp+v/Or9enE27XR65sXeDSzOuIJSFgRcqvayzmdmrpuN5UUQ9JSw=; Message-ID: <790998.56400.qm@web38605.mail.mud.yahoo.com> X-YMail-OSG: 45geOU8VM1lnvrpHpz3k4DLAQMGDx2sKviVasJdmon760iJLcdO1wdBJpCMoG7f_eVONB80eQilfbM.8kP57SsEjyb77kve0gME8d2IHbwH63SkiMz9LL5HJwBrv17wqKnFGkii8kFXoCejK3HsdqLsUYR9TrAKCmo3x4Lvz60i3WxMvPXY4IIvEi2EoMBq7PeJUcXUoodMrnUfLeVT1dkJynb70aAUMeNaXksSzOjBifpIsLPkjJHaliDDDGbGOWSNuxsuo6Ofm2QY1mkIXoHF8C0bfKA-- Received: from [84.251.6.98] by web38605.mail.mud.yahoo.com via HTTP; Thu, 18 Feb 2010 05:51:45 PST X-Mailer: YahooMailRC/300.3 YahooMailWebService/0.8.100.260964 References: <4B7D3FEC.5040905@gmail.com> Date: Thu, 18 Feb 2010 05:51:45 -0800 (PST) From: Andrey Adamovich Subject: Re: [jr3] monitoring/instrumentation/JMX To: dev@jackrabbit.apache.org In-Reply-To: <4B7D3FEC.5040905@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-34660276-1266501105=:56400" --0-34660276-1266501105=:56400 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable +1=0A=0AOther areas for potential monitoring:=0A=0A* number of JCR sessions= (created, active, dead) (per workspace)=0A* number of created nodes (per w= orkspace)=0A* number of read operations (per workspace)=0A* may be some ind= ex size/progress monitoring=0A=0AAndrey =0A=0A=0A=0A_______________________= _________=0AFrom: Justin Edelson =0ATo: dev@jackra= bbit.apache.org=0ASent: Thu, 18 February, 2010 14:26:04=0ASubject: [jr3] mo= nitoring/instrumentation/JMX=0A=0AAs I mentioned in the JCache thread, I'd = like to have Jackrabbit expose=0Amonitoring data (presumably via JMX). The = most obvious place for this is=0Aaround caches, but I imagine there are oth= er places where monitoring=0Adata could be useful.=0A=0AAny ideas?=0A=0AJus= tin=0A=0A=0A=0A --0-34660276-1266501105=:56400 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
+1

Other areas for potential monitoring:

* number = of JCR sessions (created, active, dead) (per workspace)
* number of cre= ated nodes (per workspace)
* number of read operations (per workspace)* may be some index size/progress monitoring

Andrey


From: Justin Edelson <justinedelson@gmail.com>
= To: dev@jackrabbit.apache.org=
Sent: Thu, 18 February= , 2010 14:26:04
Subject: [jr3] monitoring/instrumentation/JMX

As I mentioned in the JCache = thread, I'd like to have Jackrabbit expose
monitoring data (presumably v= ia JMX). The most obvious place for this is
around caches, but I imagine= there are other places where monitoring
data could be useful.

An= y ideas?

Justin
=0A
=0A=0A=0A=0A --0-34660276-1266501105=:56400--