Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1ej5DD-0000Qo-Dk
	for pgsql-performance@arkaria.postgresql.org; Tue, 06 Feb 2018 15:31:11 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1ej5DB-000586-SI
	for pgsql-performance@arkaria.postgresql.org; Tue, 06 Feb 2018 15:31:09 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <ahodgson@lists.simkin.ca>)
	id 1ej5DB-00057x-7s
	for pgsql-performance@lists.postgresql.org; Tue, 06 Feb 2018 15:31:09 +0000
Received: from athena.simkin.ca ([2607:f040:1001:2::ff:2])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <ahodgson@lists.simkin.ca>)
	id 1ej5D4-0006je-8B
	for pgsql-performance@lists.postgresql.org; Tue, 06 Feb 2018 15:31:08 +0000
Received: from skynet.simkin.ca (unknown [IPv6:2607:f040:1001:103::1002])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by athena.simkin.ca (Postfix) with ESMTPSA id 77045DC696F5
	for <pgsql-performance@lists.postgresql.org>;
 Tue,  6 Feb 2018 07:30:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.simkin.ca;
	s=athena; t=1517931059;
	bh=sFSSnV32sWV61YiUgADPWaq/S2+ACWVbgI/L+bTsD2w=;
	h=Message-ID:Subject:From:To:Date:In-Reply-To:References:
	 Content-Type:X-PGP-Key:Mime-Version:Sender:From:To:Subject:Date:
	 Reply-To;
	b=CkW4LNYlnyGO8PiCGZx6AKY3+yJdTvJd/IoaZA5jR2b3zLmAM1Goa+oPCbWIaa/gD
	 wMmOUM/cQOhDou9/BYUje4e83zx3eS8PEz7bmvpFrwbjprIQy3WEIcqLcbAa+Ws/wj
	 WrqNf0ZgZzzEBndCBud/0ZJntpFXGurJ+ecCGAtWX03v7wt6HHVSyU6jGIxOB7JSph
	 NB4GcU2cUQxlMu8P+aCtTIUbxfTalIY/yZcVt18lM0Z3HmHBRoto1pMAyzOemJtzTu
	 yJBWPjxm9jTqLOlyAYMxA1rYzRU4YX+fKuQzmO+qfLe7eWmoFmCaCCZAlduWdI7eJ9
	 8oMg1bYPVnjpg==
Received: from skynet.simkin.ca (skynet.simkin.ca [IPv6:::1])
	by skynet.simkin.ca (Postfix) with ESMTP id 137C6200F3034
	for <pgsql-performance@lists.postgresql.org>;
 Tue,  6 Feb 2018 07:30:59 -0800 (PST)
Message-ID: <1517931059.5522.16.camel@lists.simkin.ca>
Subject: Re: Details after Load Peak was: OT: Performance of VM
From: Alan Hodgson <ahodgson@lists.simkin.ca>
To: pgsql-performance@lists.postgresql.org
Date: Tue, 06 Feb 2018 07:30:59 -0800
In-Reply-To: <e02f17cb-bea7-3ad3-61ba-7798149078b0@thomas-guettler.de>
References: <3bc54eb3-135d-692c-47e2-208189a350d7@thomas-guettler.de>
	 <91fec1f8-d11d-2413-6b57-5310ab0e3b8a@a-kretschmer.de>
	 <e02f17cb-bea7-3ad3-61ba-7798149078b0@thomas-guettler.de>
Content-Type: multipart/alternative; boundary="=-nO1X0Dbkm7pAW3vmw659"
X-PGP-Key: fp="EF82 6F8D A3BA A096 FFA3 05F2 A7A0 40A5 34E5 AA0B";
 id="0x34E5AA0B";
 get=<https://sks-keyservers.net/pks/lookup?op=get&search=0xA7A040A534E5AA0B>;
 get=<https://athena.simkin.ca/pgp/ahodgson.public.asc>
X-Mailer: Evolution 3.24.6 
Mime-Version: 1.0
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk


--=-nO1X0Dbkm7pAW3vmw659
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Tue, 2018-02-06 at 15:31 +0100, Thomas Güttler wrote:
> 
.... But one thing is still unclear. Imagine I see a peak in the chart. The peak
> was some hours ago. AFAIK sar has only the aggregated numbers.
> 
> But I need to know details if I want to answer the question "Why?". The peak
> has gone and ps/top/iotop don't help me anymore.
> 

The typical solution is to store stats on everything you can think of
with munin, cacti, ganglia, or similar systems.

I know with ganglia at least, in addition to all the many details it
already tracks on a system and the many plugins already available for
it, you can write your own plugins or simple agents, so you can keep
stats on anything you can code around.

Munin's probably the easiest to try out, though.
--=-nO1X0Dbkm7pAW3vmw659
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit

<html><head></head><body><div>On Tue, 2018-02-06 at 15:31 +0100, Thomas Güttler wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>
.... But one thing is still unclear. Imagine I see a peak in the chart. The peak
was some hours ago. AFAIK sar has only the aggregated numbers.

But I need to know details if I want to answer the question "Why?". The peak
has gone and ps/top/iotop don't help me anymore.

</pre></blockquote><div><br></div><div>The typical solution is to store stats on everything you can think of with munin, cacti, ganglia, or similar systems.</div><div><br></div><div>I know with ganglia at least, in addition to all the many details it already tracks on a system and the many plugins already available for it, you can write your own plugins or simple agents, so you can keep stats on anything you can code around.</div><div><br></div><div>Munin's probably the easiest to try out, though.</div></body></html>
--=-nO1X0Dbkm7pAW3vmw659--