Hi Tom, Did you ever get CAS working with logback and return JSON. I have just started to experiment with Loggly here at the Kuali Foundation. We are using CAS 3.5.2. I wonder if you could share your logging configuration and how you swapped out log4j (excluded from overlay etc).
On Friday, December 20, 2013 3:34:42 PM UTC-5, Tom Poage wrote: > > Happy Friday. > > Anyone kicked around trying to change the CAS server build to emit logs > as JSON? I was initially thinking of Inspektr audit entries (vs. > multi-line or delimited audit logs) to allow easy parsing, filtering, > etc. but other log sources might also benefit. > > CAS (3.5.2, 4.0RC) uses slf4j, though underneath appears to bind to/rely > on log4j 1.2 (perhaps I'm not reading the POM correctly). The log4j 1.2 > source shows what it supports is rather archaic, e.g. RFC 3164 from > circa 2001. Does the CAS server have known dependencies requiring log4j > 1.2? > > Seems there could be (at least) two ways to go: both log4j 2.x and an > extension to Logback (Loggly) support JSON, not to mention a bunch of > improved logging features. Don't want to (re)start any Stack Overflow > wars, but preference? Any plans to update? Offhand I don't see anything > related on issues.jasig.org. > > http://logging.apache.org/log4j/2.x/manual/layouts.html > https://github.com/qos-ch/logback-extensions/wiki/Loggly > http://www.loggly.com/docs/log-types/ > > Thanks! > Tom. > > -- > You are currently subscribed to [email protected] <javascript:> as: > [email protected] <javascript:> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
