From 703e370d5721eb8035d4a094d0628ce8b12d4964 Mon Sep 17 00:00:00 2001 From: emreyigit Date: Mon, 16 Jun 2025 14:23:09 +0300 Subject: [PATCH 1/2] Add dynamic changes. --- docs/modules/maintain-cluster/pages/monitoring.adoc | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/docs/modules/maintain-cluster/pages/monitoring.adoc b/docs/modules/maintain-cluster/pages/monitoring.adoc index 7f0a3dc5c..ceb529814 100644 --- a/docs/modules/maintain-cluster/pages/monitoring.adoc +++ b/docs/modules/maintain-cluster/pages/monitoring.adoc @@ -1251,7 +1251,7 @@ want to specify the port in the monitor Hazelcast offers an extended set of diagnostics plugins for both Hazelcast members and clients. A dedicated log file is used to write the diagnostics content, and a rolling file approach is used to -prevent taking up too much disk space. +prevent taking up too much disk space. Also, the diagnostics can be configured dynamically via Management Center or Operator over cluster if it is not configured statically as shown below. === Enabling Diagnostics Logging @@ -1331,6 +1331,15 @@ java -Dhazelcast.diagnostics.enabled=true JAVA_OPTS="-Dhazelcast.diagnostics.enabled=true -Dhazelcast.diagnostics.metric.level=info -Dhazelcast.diagnostics.invocation.sample.period.seconds=30 -Dhazelcast.diagnostics.pending.invocations.period.seconds=30 -Dhazelcast.diagnostics.slowoperations.period.seconds=30 -Dhazelcast.diagnostics.storeLatency.period.seconds=60" ---- -- +Dynamic Configuration:: ++ +-- +Diagnostics can be enabled dynamically via Management Center or Operator over cluster. In order to configure dynamically, the diagnostics should not be enabled or disabled explicitly via properties. Any configuration made via properties will override dynamic configuration. + +Please refer to Operator or Management Center documentation for more information on how to enable diagnostics dynamically. #TODO: link to Operator and Management Center documentation + +Another improvement in dynamic diagnostics configuration is auto-off. On dynamic configuration, the diagnostics can be turned off automatically after a certain period of time. This can be configured through the Management Center or Operator. +-- ==== On the Java client side, it is enough to set the following properties: @@ -1869,6 +1878,8 @@ It shows statistics including the count of methods for each store (`load`, `load latency distributions for each store. The following is an example output snippet as part of the diagnostics log file for Hazelcast MapStore: +!NOTE: This plugin cannot be enabled dynamically due to its design. + ``` 17-9-2019 13:12:34 MapStoreLatency[ map[ From c6023c4c7bf3bfe5cac64c140009fe202253b045 Mon Sep 17 00:00:00 2001 From: emreyigit Date: Mon, 23 Jun 2025 12:16:18 +0300 Subject: [PATCH 2/2] Improve the docs --- docs/modules/maintain-cluster/pages/monitoring.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/modules/maintain-cluster/pages/monitoring.adoc b/docs/modules/maintain-cluster/pages/monitoring.adoc index ceb529814..543d58605 100644 --- a/docs/modules/maintain-cluster/pages/monitoring.adoc +++ b/docs/modules/maintain-cluster/pages/monitoring.adoc @@ -1336,6 +1336,8 @@ Dynamic Configuration:: -- Diagnostics can be enabled dynamically via Management Center or Operator over cluster. In order to configure dynamically, the diagnostics should not be enabled or disabled explicitly via properties. Any configuration made via properties will override dynamic configuration. +For example, if you set the `hazelcast.diagnostics.enabled` property to `true`, diagnostics cannot be disabled dynamically via Management Center or Operator. Similarly, if you set the `hazelcast.diagnostics.enabled` property to `false`, diagnostics cannot be enabled dynamically via Management Center or Operator. It also applies for other properties. + Please refer to Operator or Management Center documentation for more information on how to enable diagnostics dynamically. #TODO: link to Operator and Management Center documentation Another improvement in dynamic diagnostics configuration is auto-off. On dynamic configuration, the diagnostics can be turned off automatically after a certain period of time. This can be configured through the Management Center or Operator. @@ -1878,7 +1880,7 @@ It shows statistics including the count of methods for each store (`load`, `load latency distributions for each store. The following is an example output snippet as part of the diagnostics log file for Hazelcast MapStore: -!NOTE: This plugin cannot be enabled dynamically due to its design. +!NOTE: This plugin cannot be enabled dynamically due to its design restrictions. ``` 17-9-2019 13:12:34 MapStoreLatency[