Thanks very much every one.
They will probably pursue custom code to see if they can get this data and
log it.
J
--
Thanks,
Jeff Courtade
M: 240.507.6116
On Tue, Dec 6, 2016 at 7:07 PM, John Bickerstaff
wrote:
> You know - if I had to build this, I would consider slurping up the
> relevant l
They wanted out of the box solutions.
This is what I found too that it would be custom. i was hoping i just was
not finding something obvious.
Jeff Courtade
M: 240.507.6116
On Dec 6, 2016 7:07 PM, "John Bickerstaff" wrote:
> You know - if I had to build this, I would consider slurping up the
You know - if I had to build this, I would consider slurping up the
relevant log entries (if they exist) and feeding them to Kafka - then your
people who want to analyze what happened can get those entries again and
again (Think of Kafka kind of like a persistent messaging store that can
store log
If you can identify currently-logged messages that give you what you need
(even if you have to modify or process them afterwards) you can easily make
a custom log4j config that grabs ONLY what you want and dumps it into a
separate file...
I'm pretty sure I've seen all the request coming through in
There is also Jetty level access log which shows the requests, though
it may not show the HTTP PUT bodies.
Finally, various online monitoring services probably have agents that
integrate with Solr to show what's happening. Usually costs money
though.
Regards,
Alex.
http://www.solr-start.
Thanks very much the trace idea is a brilliant way to dig into it. Did not
occur to me.
I had another coworker suggest the custom
http://lucene.apache.org/solr/6_3_0/solr-core/org/apache/solr/update/processor/LogUpdateProcessorFactory.html
this is beyond my litmited abilites.
I will see what
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
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...
