Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0EA9A11EBE for ; Thu, 24 Apr 2014 09:16:56 +0000 (UTC) Received: (qmail 30204 invoked by uid 500); 24 Apr 2014 09:16:54 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 29021 invoked by uid 500); 24 Apr 2014 09:16:51 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 28325 invoked by uid 99); 24 Apr 2014 09:16:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 09:16:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kxepal@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-we0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 09:16:44 +0000 Received: by mail-we0-f178.google.com with SMTP id u56so1932288wes.37 for ; Thu, 24 Apr 2014 02:16:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=of61J1GjGDpkU26ZEKUp1/rvRJp+4g8LVwO/1x6hpZ4=; b=uldPYslfrpiZjcgYIM9Nf5j1FexpyVR8WbxQincJQTArZ0fFu5UuwiWszCidBcZd9Q 9sO0PNNzQb13HHcWTui1a3IjY3blA4zA9zudbmP9+LH9adpE9gsFlG+7wfQ03ZCe7X8j UFGflKkdkszXcngxPzuExoh2pEyNX5c9JwUH0Ya7/RR+BMFFqFIJoxcG55n7yAs3/16G 7AOpO2Hbu8SrToRE4Fb2UgnV5MXPZo+g1XH6haV/dOy8lh6738k41cXyA3PMLr8J8XxY yjaHkjJbZm4CUPl3JSt1QSXs7wtXN0Y15S0rttQpzKbKtr2rpCuaCikX3nL78Ax0Tc7J 3bjA== MIME-Version: 1.0 X-Received: by 10.180.76.146 with SMTP id k18mr5445864wiw.5.1398330983546; Thu, 24 Apr 2014 02:16:23 -0700 (PDT) Received: by 10.180.184.135 with HTTP; Thu, 24 Apr 2014 02:16:23 -0700 (PDT) Date: Thu, 24 Apr 2014 13:16:23 +0400 Message-ID: Subject: [ANN] CouchDB monitoring: you're doing it wro...you can do it better! From: Alexander Shorin To: "user@couchdb.apache.org" , "dev@couchdb.apache.org" Cc: "marketing@couchdb.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi everyone again, Actually, I have another one thing to share with you for today: it's the post-guidance I wrote about monitoring CouchDB: http://gws.github.io/munin-plugin-couchdb/guide-to-couchdb-monitoring.html While it located in the same repository as plugin for specific monitoring system, it's completely project neutral (with a bit exception at the end) and aims to cover all the possibilities for monitoring CouchDB server state. Just using only /_stats isn't enough. If you prefer Zabiix or Nagios or something else you'll also may found some interesting bits there. As for discussion topic I'd like to ask everyone about how you monitor your CouchDB in production? Which metrics are important for your and which ones you feel missed? Experience sharing and cool stories about how monitoring helps you to keep CouchDB good and well is welcome! P.S. English isn't my native language, so please if you'd noticed any misspelling or sentences with incorrect syntax, please don't shy to send me private email with corrections. Thanks! -- ,,,^..^,,,