Re: Database health check/auditing

From: Tim Cross <theophilusx(at)gmail(dot)com>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Database health check/auditing
Date: 2018-02-16 20:04:51
Message-ID: 87y3js7lb0.fsf@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Thomas Kellerer <spam_eater(at)gmx(dot)net> writes:

>> situation: I have just commenced a DBA and developer role for an
>> organisation with a number of Postgres databases (9.4 and 9.6
>> versions). There has been no dedicated DBA and a number of the databases
>> were setup by people with little to know Postgres or database
>> experience. I need to get an overview on what I'm dealing with and start
>> prioritising what to address first.
>>
>
> You might want to have a look at OPM: http://opm.io/

Looks interesting. Nagios is what is used here for monitoring and
although rusty, once upon a time, I use to cut quite a lot of perl, so
reasonable skill set match. Will check it out.

Although on-going monitoring of the systems is definitely required, the
first step is to just get an overall handle on the situation. There is
no documentation and configuration, maintenance etc has been patchy.

Tim

--
Tim Cross

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2018-02-16 20:05:35 Re: gathering ownership and grant permissions
Previous Message Tim Cross 2018-02-16 19:54:04 Re: Database health check/auditing