This starts sounding more and more silly the longer I think about it, but is there a way I can utilize the ULS Tracing service programmatically but have it write to another file, not the default
I work with a farm that provides hosting for tenants, and with their custom code many of them like to write trace events to ULS but when digging for platform level errors it becomes a pain to start adding filters to ULS Viewer. I'd also like to separate concerns here so that if any particular tenant needs a log dump it would be easier on my end.
I've been digging into the
SPDiagnosticsServiceBase class and even so far down into beginning to look into the
ULS class itself to see if there was anything I could pick up but so far I'm not seeing much in terms of where I can inject a path and custom naming convention.
Perhaps the issue here is, the tenants shouldn't be writing to the ULS logs. However, I would like to explore the idea of writing out their diagnostic checks in the same format that ULS Viewer can read.
Any ideas or points in the right direction would be greatly appreciated.