Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: CouchDB & inspection
From: Martin Hewitt <martin@thenoi.se>
In-Reply-To: 
 <CABvT1DHqvPBrU2qDp_L-viJbEyE_qHA-80DV=rMNbbs9EH+t6Q@mail.gmail.com>
Date: Wed, 25 Apr 2012 14:39:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E13C5669-0D7B-4AE8-9759-E29167AAE0AB@thenoi.se>
References: <64D96C44-A94B-4857-8AEF-284442A1A823@thenoi.se>
 <CABvT1DHqvPBrU2qDp_L-viJbEyE_qHA-80DV=rMNbbs9EH+t6Q@mail.gmail.com>
To: user@couchdb.apache.org

I haven't seen /_stats, that's a very useful link, thanks Robert.

Martin=20

On 25 Apr 2012, at 14:00, Robert Newson wrote:

> Have you seen /_stats ?
>=20
> B.
>=20
> On 25 April 2012 13:57, Martin Hewitt <martin@thenoi.se> wrote:
>> Hi all,
>>=20
>> We're in the process of adding a load of instrumentation to our =
servers, apps and so on, and I was wondering if there's a way we can =
hook into CouchDB to extract basic inspection details like request =
duration, that sort of thing?
>>=20
>> We're trying to make sure we can pinpoint where any bottlenecks =
appear, so measuring everything app-side, whilst simpler, doesn't quite =
give us the insight we're looking for.
>>=20
>> Thanks,
>>=20
>> Martin