Browse Source

[doc] update deprecation logging (#83723)

more details on how to disable deprecation logging
Przemyslaw Gomulka 3 years ago
parent
commit
8bdfd6ea04
1 changed files with 15 additions and 1 deletions
  1. 15 1
      docs/reference/setup/logging-config.asciidoc

+ 15 - 1
docs/reference/setup/logging-config.asciidoc

@@ -208,12 +208,26 @@ critical feature was used, it won't be removed in next major version, but might
 be removed in the future.
 be removed in the future.
 
 
 To stop writing deprecation log messages, set `logger.deprecation.level`
 To stop writing deprecation log messages, set `logger.deprecation.level`
-to `OFF`:
+to `OFF` in `log4j2.properties` :
 
 
 [source,properties]
 [source,properties]
 ----
 ----
 logger.deprecation.level = OFF
 logger.deprecation.level = OFF
 ----
 ----
+Alternatively, you can change the logging level dynamically: 
+
+[source,console]
+----
+PUT /_cluster/settings
+{
+  "persistent": {
+    "logger.org.elasticsearch.deprecation": "OFF"
+  }
+}
+----
+
+Refer to <<configuring-logging-levels,Configuring logging levels>>.
+
 
 
 You can identify what is triggering deprecated functionality if `X-Opaque-Id` was used as an HTTP header.
 You can identify what is triggering deprecated functionality if `X-Opaque-Id` was used as an HTTP header.
 The user ID is included in the `X-Opaque-ID` field in deprecation JSON logs.
 The user ID is included in the `X-Opaque-ID` field in deprecation JSON logs.