On 11/20/2018 5:34 PM, Alexandre Rafalovitch wrote:
How much of this controlled by log4j property file and we can include
usecases as commented out things to let people choose?
Because we can set the logging very precisely without recompiling.
If we can control it with log4j config, that would be very nice.
A quick check of the SolrResourceLoader code suggests that if the
logging level for that class were changed to DEBUG, it would nicely
provide the info that I'm after, wouldn't log a huge amount of useless
cruft, and wouldn't even require a code change. Maybe we could put this
config in log4j2.xml, commented out, as an option that the end user
could enable if they wish.
Another solution would be to create a special logger, along the lines of
the ones in SolrCore that log requests and slow requests, and have log4j
config for that special logger. And that's not necessarily a bad idea,
but I think the idea mentioned above is good enough, and a lot easier.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
