Before I reinvent the wheel ...
Has anyone worked out a method to configure two rsyslog agents on
different servers, writing to the same database at the same time?
In other words, if you have two rsyslog agents on two servers with all
your devices reporting to both (in case one fails), you don't want to
end up with duplicate entries in your database for everything.
A cold stand-by, with the second rsyslog process not running seems like
a poor (but possible) solution.
Using database features, like UPDATE ON DUPLICATE KEY might work,
depending on what you're inserting and if you can generate a unique key
per insert and aren't relying on an incremental value.
A feature that would be interesting is if rsyslog-backup would ping
rsyslog-primary and if it's not available, to start logging at that
point (otherwise, remain idle).
Just curious if others are doing this, and if you found a sharable solution.
Cheers,
Jacob
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
