Mon Dec 12 20:24:19 PST 2005
- Previous message: [Slony1-general] replication stalled - with no errors raported by slon ?
- Next message: [Slony1-general] slony Installation Problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/12/05, Tim Goodaire <tgoodair at ca.afilias.info> wrote: > > Also, I am interested in your mrtg graphing of replication lag. It's a > project > that I've been meaning to look into. Would you mind sharing your mrtg > configuration? > not at all. first - since i use mrtg to graph data from multiple servers i use snmp (net-snmp to be exact). on database server i added this line to snmpd configuration: exec replicationLagTime /cvs/scripts/snmpReplicationLagTime.sh 2 where /cvs/scripts/snmpReplicationLagTime.sh looks like this: #!/bin/bash /home/pgdba/work/bin/psql -U pgdba -h 127.0.0.1 -p 5800 -d _DBNAME_ -qAt -c "select cast(extract(epoch from st_lag_time) as int8) FROM _irr.sl_status WHERE st_received = $1" then in mrtg configuration i added this target: Target[db_replication_lagtime]:extOutput.3&extOutput.3:public at db::30::: MaxBytes[db_replication_lagtime]: 400000000 Title[db_replication_lagtime]: db: replication lag time PageTop[db_replication_lagtime]: <H1>db: replication lag time</H1> Options[db_replication_lagtime]: gauge,nopercent,growright of course in your installation extOutput.NUMBER might be different, but that's easy to find out. and that's it. nothing fancier. depesz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20051212/323bc828/attachment.html
- Previous message: [Slony1-general] replication stalled - with no errors raported by slon ?
- Next message: [Slony1-general] slony Installation Problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list