Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0E9CE966A for ; Wed, 25 Apr 2012 13:00:18 +0000 (UTC) Received: (qmail 90974 invoked by uid 500); 25 Apr 2012 13:00:16 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 90835 invoked by uid 500); 25 Apr 2012 13:00:16 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 90827 invoked by uid 99); 25 Apr 2012 13:00:16 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 13:00:16 +0000 Received: from localhost (HELO mail-yx0-f180.google.com) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 13:00:16 +0000 Received: by yenl4 with SMTP id l4so54701yen.11 for ; Wed, 25 Apr 2012 06:00:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.42.134 with SMTP id o6mr2318015igl.72.1335358815026; Wed, 25 Apr 2012 06:00:15 -0700 (PDT) Received: by 10.42.240.135 with HTTP; Wed, 25 Apr 2012 06:00:14 -0700 (PDT) In-Reply-To: <64D96C44-A94B-4857-8AEF-284442A1A823@thenoi.se> References: <64D96C44-A94B-4857-8AEF-284442A1A823@thenoi.se> Date: Wed, 25 Apr 2012 14:00:14 +0100 Message-ID: Subject: Re: CouchDB & inspection From: Robert Newson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Have you seen /_stats ? B. On 25 April 2012 13:57, Martin Hewitt wrote: > Hi all, > > 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? > > 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. > > Thanks, > > Martin