Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread Tim Clarke
On 24/07/17 15:01, PAWAN SHARMA wrote: > > > > On Mon, Jul 24, 2017 at 7:28 PM, Tim Clarke > wrote: > > > > On 24/07/17 14:47, PAWAN SHARMA wrote: > > > > Hi Tim, > > > > Facing below issue > > > > [abc@test:/home/psharm89/nrpe-2.15]# >

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread PAWAN SHARMA
On Mon, Jul 24, 2017 at 7:28 PM, Tim Clarke wrote: > > > On 24/07/17 14:47, PAWAN SHARMA wrote: > > > > Hi Tim, > > > > Facing below issue > > > > [abc@test:/home/psharm89/nrpe-2.15]# > > Redirecting to /bin/systemctl restart xinetd.service > > Failed to restart xinetd.service: Unit xinetd.servi

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread Tim Clarke
On 24/07/17 14:47, PAWAN SHARMA wrote: > > Hi Tim, > > Facing below issue > > [abc@test:/home/psharm89/nrpe-2.15]# > Redirecting to /bin/systemctl restart xinetd.service > Failed to restart xinetd.service: Unit xinetd.service failed to load: > No such file or directory. > [abc@test:/home/psharm8

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread PAWAN SHARMA
On Mon, Jul 24, 2017 at 5:50 PM, PAWAN SHARMA wrote: > > On Mon, Jul 24, 2017 at 5:20 PM, Tim Clarke > wrote: > >> We use nagios for all alerting, it'll do what you need. >> >> Tim Clarke >> >> >> On 24/07/17 12:38, Achilleas Mantzios wrote: >> > pgbadger is a very nice reporting tool, overall,

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread PAWAN SHARMA
On Mon, Jul 24, 2017 at 5:20 PM, Tim Clarke wrote: > We use nagios for all alerting, it'll do what you need. > > Tim Clarke > > > On 24/07/17 12:38, Achilleas Mantzios wrote: > > pgbadger is a very nice reporting tool, overall, albeit not exactly at > > the system side, but more to the DBA side.

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread Tim Clarke
We use nagios for all alerting, it'll do what you need. Tim Clarke On 24/07/17 12:38, Achilleas Mantzios wrote: > pgbadger is a very nice reporting tool, overall, albeit not exactly at > the system side, but more to the DBA side. > For system level monitoring maybe take a look here : > https://

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread Achilleas Mantzios
pgbadger is a very nice reporting tool, overall, albeit not exactly at the system side, but more to the DBA side. For system level monitoring maybe take a look here : https://wiki.postgresql.org/wiki/Monitoring#check_postgres . Also you might want to write a script that parses logs for FATAL and

Re: [GENERAL] monitoring PostgreSQL

2017-07-24 Thread Nikolay Samokhvalov
okmeter.io is good (though it's cloud-based and costs some money), I'm using it and definitely can recommend. There much more tools, see: https://wiki.postgresql.org/wiki/Monitoring On Mon, Jul 24, 2017 at 4:27 AM, PAWAN SHARMA wrote: > Hi All, > > > Please provide me a list of tools which we c

Re: [GENERAL] Monitoring PostgreSQL connections using cricket and

2006-01-05 Thread Tony Wasson
On 1/5/06, Steve Crawford <[EMAIL PROTECTED]> wrote: > > Resting Connections - connections that have no query information. I > > suspect these are connections starting up or shutting down, but feel > > free to clue me in. > > OK, this appears to be version-dependent but it can mean that > stats_que

Re: [GENERAL] Monitoring PostgreSQL connections using cricket and

2006-01-05 Thread Steve Crawford
Resting Connections - connections that have no query information. I suspect these are connections starting up or shutting down, but feel free to clue me in. OK, this appears to be version-dependent but it can mean that stats_query_string is false or that the user you are connecting as has no p