good point.. then I keep it like it is and take it out of the logfiles...
But maybe something like jvm ok/nok is possible?
By default Dhazelcast.health.monitoring.level is set to "silence" and
information will be logged as warning, if a given threshold is reached.
Maybe this could trigger a "jvm:
Hello Peter,
IMO this might be sensitive information
Are you sure this should be available without authorization?
On Fri, 7 Feb 2020 at 16:18, Peter Dähn wrote:
> Hi Maxim,
>
> during my little research I used the information of hazelcast
> HealthMonitor...
>
> 07-Feb-2020 09:27:17.941 INFORMAT
Hi Maxim,
during my little research I used the information of hazelcast
HealthMonitor...
07-Feb-2020 09:27:17.941 INFORMATION [hz.server-1.HealthMonitor]
com.hazelcast.internal.diagnostics.HealthMonitor.null [dev] [3.12.5]
processors=4, physical.memory.total=0, physical.memory.free=0,
swap.space.