Hey Wolf!
Technically it's possible but I'm not sure if we should do this. I think
this is a responsibility of monitoring tools (e.g. Splunk, Kibana or even
Zabbix).
Thanks
Sebastian
On Tue, Jul 26, 2016 at 10:21 AM, Wolf Fink <wfink(a)redhat.com> wrote:
Do we expose historical data for the cluster view. Often it is
important
to see whether there are view changes, rebalancing and unexpected
leave/merge events where nodes are kicked by JGroups.
Having special entries for controlled view change and sudden view changes
might be good
On Tue, Jul 26, 2016 at 10:06 AM, Sebastian Laskawiec <slaskawi(a)redhat.com
> wrote:
> Hey Vojtech!
>
> JMX and CLI integration sounds very interesting. I also like the idea of
> exposing log and exception dump.
>
> Thanks a lot for the input!
> Sebastian
>
> On Tue, Jul 26, 2016 at 9:00 AM, Vojtech Juranek <vjuranek(a)redhat.com>
> wrote:
>
>> On Tuesday 26 July 2016 07:10:16 Sebastian Laskawiec wrote:
>> > I'm currently sketching a design for a REST
>> > health check endpoint for Infinispan
>>
>> if it's not too broad, I'd include also various information about the
>> cluster
>> - e.g. number of machines in the cluster, recent exceptions in the log
>> (or
>> dump of N lines of log) etc. If would be useful at least for testing
>> purposes
>> so that we won't have to gather various information via JMX and CLI
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev