From: | Tim Smith <randomdev4+postgres(at)gmail(dot)com> |
---|---|
To: | Vick Khera <vivek(at)khera(dot)org> |
Cc: | Edson Carlos Ericksson Richter <edsonrichter(at)hotmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Database and OS monitoring |
Date: | 2014-12-14 17:13:24 |
Message-ID: | CA+HuS5Geu0wkJ6NWT90Rx8Ob8hqE6e_oonSA+EXCMrSDyJ7wfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lots of great tidbits there from a guy who really knows his performance
stuff (ex-Sun, now Netflix)
On Sunday, 14 December 2014, Vick Khera <vivek(at)khera(dot)org> wrote:
>
> On Sat, Dec 13, 2014 at 1:55 PM, Edson Carlos Ericksson Richter <
> edsonrichter(at)hotmail(dot)com
> <javascript:_e(%7B%7D,'cvml','edsonrichter(at)hotmail(dot)com');>> wrote:
>>
>> I've been searching in web for guidelines on OS (Linux) and PostgreSQL
>> (9.3.5) active monitoring best practices.
>>
>
> Recent trends are more toward monitoring response latency by first
> establishing a baseline level of activity and latency, then alerting when
> those numbers get out of acceptable range.
>
> There are some open source tools to collect and sort and report this way
> (see Kibana and Grafana and their underlying data stores). I've not seen
> alerting tools based on this that are non-commercial, though. Two services
> I know of are Ruxit and Circonus.
>
> Personally I still use Nagios to tell my staff when things are down or not
> responding, but often that is too late to proactively fix things.
>
> One thing that'd be really cool is to use the new binary JSON storage in
> the upcoming Pg release to store the time series data for use with
> Grafana... but then you'd have a chicken/egg problem with monitoring
> itself. :)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2014-12-14 18:01:55 | Re: Blocking access by remote users for a specific time period |
Previous Message | Tom Lane | 2014-12-14 16:32:51 | Re: Error: "Out of memory while reading tuples." in pushing table from SAS to PostgreSQL on Mac |