From: Alan Hodgson <ahodgson@lists.simkin.ca>
To: pgsql-performance@lists.postgresql.org
Subject: Re: Details after Load Peak was: OT: Performance of VM
Date: Tue, 06 Feb 2018 07:30:59 -0800
Message-ID: <1517931059.5522.16.camel@lists.simkin.ca> (raw)
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>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ahodgson@lists.simkin.ca, pgsql-performance@lists.postgresql.org
Subject: Re: Details after Load Peak was: OT: Performance of VM
In-Reply-To: <1517931059.5522.16.camel@lists.simkin.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox