Monitoring hot standby replication for failure - Mailing list pgsql-admin

From Mark Steben
Subject Monitoring hot standby replication for failure
Date
Msg-id CADyzmyxM9_10Wa8gu-HLbJZ9zR-w+1pwZ2yTaVqJH0AdDnD7Jw@mail.gmail.com
Whole thread Raw
Responses Re: Monitoring hot standby replication for failure  (Frank Alberto Rodriguez Solana <franknigth@gmail.com>)
Re: Monitoring hot standby replication for failure  ("Jehan-Guillaume (ioguix) de Rorthais" <ioguix@free.fr>)
Re: Monitoring hot standby replication for failure  (Shreeyansh Dba <shreeyansh2014@gmail.com>)
List pgsql-admin
Good afternoon,

We are running postgres 9.4.  We are outsourcing our databases to another datacenter owned by a third party company.  The methodology we are using to move the database is hot standby log shipping replication.  We will run streaming replication for several days then, when the time comes to pull the trigger and make the move, I will complete recovery, bring in a 'production' version of postgresql.conf, restart the database, and hand it over to the apps.  

We want to make sure that during the several days of replication we are immediately notified if a problem arises - a missing log, a production outage, etc.  Is there a monitor or an 'in-the-box' procedure, or perhaps a condition to check during hot standby or streaming replication to ensure things are still running as planned, or if there is a problem?  

Thanks for any insights. 

--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  CRM division of Dominion Dealer Solutions 
95D Ashley Ave.
West Springfield, MA 01089

t: 413.327-3045
f: 413.383-9567

www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
 www.drivedominion.com





pgsql-admin by date:

Previous
From: Michael Banck
Date:
Subject: Re: Is there a way to log only a particular user connection attemptsin Postgres?
Next
From: Frank Alberto Rodriguez Solana
Date:
Subject: Re: Monitoring hot standby replication for failure