You could turn the trace mode for everything in the Admin UI (under logs/levels) and see if any of the existing information is sufficient for your needs. If yes, then you change log level in the configuration just for that class/element.
Alternatively, you could do a custom UpdateRequestProcessor in the request handler(s) that deal with update. Or perhaps LogUpdateProcessor (that's in every standard chain) is sufficient: http://www.solr-start.com/javadoc/solr-lucene/org/apache/solr/update/processor/LogUpdateProcessorFactory.html But it is also possible that the audit.log is something that has a specific format that other tools use. So, you could start from asking how that file would be used and then working backwards into Solr. Which would most likely be a custom URP, as I mentioned earlier. Regards, Alex. P.s. Remember that there are full document updates and partial updates. What you want to log about that is your business level decision. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 6 December 2016 at 13:55, Jeff Courtade <courtadej...@gmail.com> wrote: > Hello, > > Could someone point me in the correct direction for this? > > I am being asked to setup an "audit.log" or audit trail for writes and > changes to documents. > > i do not know where to begin something like this. > > I am guessing it is just configuration of log4j but that is about as far as > i can go... > > maybe something to do with logging things through only the update handler > or something? > > Anyone bearing a cluestick is welcome. > > -- > Thanks, > > Jeff Courtade > M: 240.507.6116
