http://www.slony.info/bugzilla/show_bug.cgi?id=300

--- Comment #1 from Christopher Browne <cbbrowne at ca.afilias.info> 2013-07-11 13:47:40 PDT ---
A "first blush" idea is to add a log table that looks a lot like sl_components,
but augmented to provide a log rather than a per-component state, and change
the function component_state() to add a log entry in addition to capturing the
present state.

The cleanup thread would be augmented to delete old entries from the log.  In
effect, for each actor/event, delete all but the last N entries (say, all but
the last 10 entries, 10 being a configurable value).

That would cover uptime, SYNC stats, and the last timestamp, as suggested.

It would NOT capture when log switches actually take place; at present, that
logic takes place inside the function CleanupEvent(), so isn't directly
captured by the monitoring thread.  It should be easy enough to add logic to
CleanupEvent() which adds an extra log entry when a log switch actually does
take place, in effect, capturing the information inside the DB layer.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.