-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggest DEBUG level logging instead for SAML #74661
Conversation
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-security (Team:Security) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should link to https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html#configuring-logging-levels to add context about configuring loggers in general too.
---------------- | ||
|
||
See <<configuring-logging-levels,configuring logging levels>> for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DaveCTurner Hope this is the right syntax for proper linking 😄
@elasticmachine update branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a suggestion for wording but I'll leave this up to @lcawl for the final word. I'll also go through our trace logs and see if there is something that makes sense for us to surface in debug level to ease troubleshooting
@@ -698,29 +698,30 @@ 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 | |||
Very detailed debug logging can be enabled specifically for the SAML realm by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very detailed debug logging can be enabled specifically for the SAML realm by | |
If the issue you encounter is not covered in the list above, it might be helpful to enable additional logging for the SAML realm to further troubleshoot the issue. You can enable debug logging by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this suggestion @jkakavas -- I incorporated a version of that text into my changes.
Is someone taking care of getting this PR merged & backported? @lcawl / @lockewritesdocs are either of you able to run with it? |
@elasticmachine update branch |
I'll pick this one up -- thanks for the ping @tvernum! |
@elasticmachine update branch |
@DaveCTurner, does this change also apply to 7.13 and 7.14? If so, I'll add the labels and backport appropriately. |
I think so, but I don't keep on top of changes in this area so would like someone from @elastic/es-security to confirm. |
Yes, let's backport all the way to 7.13 |
* 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]>
* 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]>
* 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]>
* 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]> Co-authored-by: Pius <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Adam Locke <[email protected]>
* 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]> Co-authored-by: Pius <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Adam Locke <[email protected]>
* 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]> Co-authored-by: Pius <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Adam Locke <[email protected]>
Per @DaveCTurner 's discussion with the security team, we believe that DEBUG logging will be sufficient for most cases for SAML troubleshooting. TRACE is only necessary if we believe there's a bug in the implementation. This PR updates the documentation to suggest DEBUG logging instead of TRACE. Thx!