Funny/coincidence you mentioned that..
I'm looking at a production case right now, for a customer of hornetQ
where network is slow (some switch broken.. I don't know exactly..
that's part of the investigation)... they need to find when that is
happening and colocated with other logs.
On Thu, A
nice, I think there is value in just logging this information and not
halting of stopping.
In this way the feature can be used to determine usage patterns and spikes
etc and it would be possible to determine what the critical levels are.
This would allow a separation between getting information and
Thanks Clebert have left my feedback directly on the PR.
Cheers
Mike
Sent from my iPhone
> On 5 Aug 2017, at 06:03, Clebert Suconic wrote:
>
> PR Sent.. i would appreciate reviews.
>
> thanks
>
> On Fri, Aug 4, 2017 at 1:02 PM, Clebert Suconic
> wrote:
>> I'm adding some logic to detect cas
PR Sent.. i would appreciate reviews.
thanks
On Fri, Aug 4, 2017 at 1:02 PM, Clebert Suconic
wrote:
> I'm adding some logic to detect cases where the broker may become
> irresponsive.
>
> I'm adding a component called CriticalAnalyzer, which will inspect
> response times of certain operations a
