Skip to content

Commit 4bb6119

Browse files
authored
[doc] update deprecation logging (#83723) (#86856)
more details on how to disable deprecation logging
1 parent 9ffe08b commit 4bb6119

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

docs/reference/setup/logging-config.asciidoc

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -210,12 +210,26 @@ critical feature was used, it won't be removed in next major version, but might
210210
be removed in the future.
211211

212212
To stop writing deprecation log messages, set `logger.deprecation.level`
213-
to `OFF`:
213+
to `OFF` in `log4j2.properties` :
214214

215215
[source,properties]
216216
----
217217
logger.deprecation.level = OFF
218218
----
219+
Alternatively, you can change the logging level dynamically:
220+
221+
[source,console]
222+
----
223+
PUT /_cluster/settings
224+
{
225+
"persistent": {
226+
"logger.org.elasticsearch.deprecation": "OFF"
227+
}
228+
}
229+
----
230+
231+
Refer to <<configuring-logging-levels,Configuring logging levels>>.
232+
219233

220234
You can identify what is triggering deprecated functionality if `X-Opaque-Id` was used as an HTTP header.
221235
The user ID is included in the `X-Opaque-ID` field in deprecation JSON logs.

0 commit comments

Comments
 (0)