<div dir="ltr">On Fri, Nov 13, 2015 at 12:57 PM, Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi guys,<br>
<br>
in order to keep track of notable events (nodes joining, leaving,<br>
rebalances, availability, task execution) and present them in the<br>
console I was thinking of using specific logging categories. These logs<br>
would be then collected by dedicated appenders on each node. The idea<br>
would then be to have some distexec tasks exposed to the management<br>
interface (console/CLI) which can query and aggregate the data.<br>
Initially I was thinking about using a local cache per-node with a SFCS,<br>
eviction, expiration and indexing and creating a log4j appender which<br>
writes to this cache, but probably a simpler lucene-based appender would<br>
suffice.<br></blockquote><div><br></div><div>I'd favor using an indexed cache instead simple Lucene appenders, since they <br></div><div>take care of querying, indexing and after all they expose the Lucene API if needed.<br><br></div><div>Not sure about local caches, what about log retention when the node dies?</div><div></div><div><br></div><div>Gustavo<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
WDYT ?<br>
<span><font color="#888888"><br>
Tristan<br>
--<br>
Tristan Tarrant<br>
Infinispan Lead<br>
JBoss, a division of Red Hat<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</font></span></blockquote></div><br></div></div>