SP logging to syslog can not set syslogHost

[Nate Klingenstein]

My preferred approach for pulling logs together across nodes is rsyslog best-effort over tcp as a secondary logging mechanism to a local on-disk something.  That gives you a higher probability of capturing interesting events no matter when or where they happen or what is done to the node subsequently, without introducing a centralized single point of failure.

On Jul 30, 2014, at 10:33 AM, "Cantor, Scott" <cantor.2 at osu.edu<mailto:cantor.2 at osu.edu>> wrote:

My suggestion to anybody trying to use syslog would be to just run
something like minion to tail the log and remote the entries that way. I
would be leery in the extreme of tying the SP to a remote logging source.

But if somebody else has made it work, they're welcome to comment.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140730/23e617ad/attachment.html