Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dETog-0002u2-CB for pgsql-admin@arkaria.postgresql.org; Sat, 27 May 2017 04:59:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dEToe-0005AE-S6 for pgsql-admin@arkaria.postgresql.org; Sat, 27 May 2017 04:59:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dETod-00059y-AZ; Sat, 27 May 2017 04:59:03 +0000 Received: from mail-vk0-x230.google.com ([2607:f8b0:400c:c05::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dEToU-0001pV-FR; Sat, 27 May 2017 04:59:02 +0000 Received: by mail-vk0-x230.google.com with SMTP id h16so13288773vkd.2; Fri, 26 May 2017 21:58:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BAgRCHuQeimLwlIPMEBu6raED5ps1ixPC/as8IMN9os=; b=lD+HaIrxSZHDQRgko3kL+XJpvP2tB9jqUHWXOdjREDVZ8/Tqn68hCzCAVQw3FZzY6v tqZmWxiCvJWgteY6IyJOWEzbmdd+sN2PfHiWKIKFkJt/GsWHbyjkOnu+Xi9S7H/2qpSi YpWxm+JAidJp5W8TjZjeoE1VjvRSWgpqaPZt3bdAaTMuHXWiq9SUt99VYsDFDsNltRBj 40qh2Tyg4NWUb7l2ItEwTeeO8JX6zZUDkFVQmxJomauD242Xkvg8qufL7aSj8Jwr/ixH 70/8Ud0iOCjVckPodRWrdJuKG2GQjgoWmHvd+2tGgWeWPNOFTcnzQE7sVAZ4VnOGC0M4 Pdww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BAgRCHuQeimLwlIPMEBu6raED5ps1ixPC/as8IMN9os=; b=aEgtxSmgu6zvj6fMekTRMA/x1RoG9Bu8B1ApDVreWikmsMI7BC50J5z7nbT3mHyVog LCNsqAJj2ngNfj6SnmkJc6V+emzjbpr6N15MoA35uerLjfczrXZAaIqfpzR7y6s0gaXL qJPnCsCB3d9KuZNsLZd/kCDx5QqqYtAMMw1iuMXebhletChVdodTwiwsuBjgprx9W9NO x0sv9bgyNJTUpLzYl4mTvn2nLC2eglwahXQi01dMjSa8kIUZt78VxBZTS+37nTvo4iLo rFCA25u2D1TKP5/1pG4Jnlw3t80uvs86jHUnOWfggadQBYawL0cmByysPuSJb9OfF567 nQmg== X-Gm-Message-State: AODbwcBPSnfZWlpY2KQObNFuthiJikSGNdAt7MXoIfb0Fu/B+46ippPw p9AiQywqaG2q2kRwJGno3XOpYkVQig== X-Received: by 10.31.63.202 with SMTP id m193mr2513034vka.103.1495861132603; Fri, 26 May 2017 21:58:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.74.12 with HTTP; Fri, 26 May 2017 21:58:52 -0700 (PDT) In-Reply-To: References: From: Dave Stibrany Date: Sat, 27 May 2017 00:58:52 -0400 Message-ID: Subject: Re: [PERFORM] Monitoring tool for Postgres Database To: "Sunkara, Amrutha" Cc: Ravi Tammineni , "pgsql-admin@postgresql.org" , "pgsql-performance@postgresql.org" Content-Type: multipart/alternative; boundary="001a114dd79a71373c05507a4fbe" X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --001a114dd79a71373c05507a4fbe Content-Type: text/plain; charset="UTF-8" We've found pghero to be a good first line of defence. It doesn't have alerting yet, but it's great for a quick high level healthcheck. Also +1 for Datadog. Extremely flexible and elegant UI + powerful alerting capabilities. On Fri, May 26, 2017 at 10:32 AM, Sunkara, Amrutha wrote: > We have been using Nagios to monitor the system level stats. The database > level stats that we gather are custom scripts that we have nagios poll to > get the database health. You could use pg badger to generate reports > against your database logs as well. Pg_badger reports are your bffs for > performance related specs.. very close to AWR reports that oracle provides. > > Sotrage/Disk latencies -- we have oracle's os watcher we running regularly > on these hosts to generate iostats as well. > > Thanks. > -Amrutha. > > On Thu, May 25, 2017 at 3:48 PM, Ravi Tammineni < > rtammineni@partner.aligntech.com> wrote: > >> Hi, >> >> >> >> What is the best monitoring tool for Postgres database? Something like >> Oracle Enterprise Manager. >> >> >> >> Specifically I am interested in tools to help: >> >> >> >> Alert DBAs to problems with both configuration and performance issues >> >> Deadlocks, Long running queries etc., >> >> Monitoring of overall system performance >> >> General performance tuning >> >> Storage/Disk latencies >> >> >> >> >> >> Thanks >> >> ravi >> > > --001a114dd79a71373c05507a4fbe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We've found pghero to be a good first line of defence.= It doesn't have alerting yet, but it's great for a quick high leve= l healthcheck.=C2=A0

Also +1 for Datadog. Extremely flex= ible and elegant UI + powerful alerting capabilities.

On Fri, May 26, 2017 at 10:= 32 AM, Sunkara, Amrutha <amrutha@nytimes.com> wrote:
We have been using Nagios to = monitor the system level stats. The database level stats that we gather are= custom scripts that we have nagios poll to get the database health. You co= uld use pg badger to generate reports against your database logs as well. P= g_badger reports are your bffs for performance related specs.. very close t= o AWR reports that oracle provides.

Sotrage/Disk latenci= es -- we have oracle's os watcher we running regularly on these hosts t= o generate iostats as well.=C2=A0

Thanks.
-Amrutha.

On Thu, May 25, 2017 at 3:48 PM, Ravi Tammineni = <r= tammineni@partner.aligntech.com> wrote:
<= div class=3D"h5">

Hi,

=C2=A0

What is the best monitoring tool for Postgres databa= se? Something like Oracle Enterprise Manager.

=C2=A0

Specifically I am interested in tools to help:

=C2=A0

Alert DBAs to problems with both configuration and p= erformance issues

Deadlocks, Long running queries etc.,<= /p>

Monitoring of overall system performance

General performance tuning

Storage/Disk latencies

=C2=A0

=C2=A0

Thanks

ravi



--001a114dd79a71373c05507a4fbe--