Logger Configuration & Hello!

[Renvoize, Martin]

Thanks Scott,

That's very informative and proves my understanding isn't 100% there yet.

I think I'll knock together a parser script to filter out the parts of the
logs I'm interested in after the fact then; thinking about it now, it makes
perfect sense that you can't do this prior to the end of an authentication
event.

Cheers

Martin

Martin Renvoize
Software Engineer, PTFS Europe Ltd
Content Management and Library Solutions
Skype:
Landline: 0203 286 8685
Mobile: 07725985636

http://www.ptfs-europe.com


On 15 July 2014 15:16, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 7/15/14, 8:27 AM, "Renvoize, Martin" <martin.renvoize at ptfs-europe.com>
> wrote:
>
> >Onto a question, I'm have a multi-tenant web app that I'm implementing
> >shibboleth authentication for.  I'm using ApplicationOverrides with
> >apache virtualhosts to great success so far.  However, as the system
> >grows with more and more tenants I'm finding it increasingly difficult to
> >see the wood from the trees in the logs if I turn it up for debugging.  I
> >was wondering if there's any simple way to configure the logs to log to
> >separate files based on applicationID?
>
> No. The only routing is via categories, and the application ID isn't part
> of any logging categories. There isn't any way to know that information at
> the time of most logging events, particularly from components that know
> nothing about the SP itself.
>
> Even if it were in the logging diagnostic context, which isn't really
> possible, I don't believe it can log to different appenders based on the
> context.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140715/d6d63d52/attachment.html