Suggest DEBUG level logging instead for SAML (elastic#74661)

* Suggest DEBUG level logging instead for SAML * Update troubleshooting.asciidoc * Incorporate reviewer feedback Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Adam Locke <[email protected]>
elasticsearchmachine · Jul 30, 2021 · 796e1b1 · 796e1b1
1 parent d086452
commit 796e1b1
Showing 1 changed file with 11 additions and 8 deletions.
diff --git a/x-pack/docs/en/security/troubleshooting.asciidoc b/x-pack/docs/en/security/troubleshooting.asciidoc
@@ -682,29 +682,32 @@ the `basic` `authProvider` in {kib}. The process is documented in the
 
 *Logging:*
 
-Very detailed trace logging can be enabled specifically for the SAML realm by
-setting the following transient setting:
+If the previous resolutions do not solve your issue, enable additional
+logging for the SAML realm to troubleshoot further. You can enable debug
+logging by configuring the following transient setting:
 
-[source, shell]
------------------------------------------------
+[source, console]
+----
 PUT /_cluster/settings
 {
   "transient": {
-    "logger.org.elasticsearch.xpack.security.authc.saml": "trace"
+    "logger.org.elasticsearch.xpack.security.authc.saml": "debug"
   }
 }
------------------------------------------------
-
+----
 
 Alternatively, you can add the following lines to the end of the
 `log4j2.properties` configuration file in the `ES_PATH_CONF`:
 
 [source,properties]
 ----------------
 logger.saml.name = org.elasticsearch.xpack.security.authc.saml
-logger.saml.level = TRACE
+logger.saml.level = DEBUG
 ----------------
 
+Refer to <<configuring-logging-levels,configuring logging levels>> for more
+information.
+
 [[trb-security-internalserver]]
 === Internal Server Error in Kibana