-
Notifications
You must be signed in to change notification settings - Fork 152
[Security] [Serverless: Oct 7] Automatic troubleshooting updates #3318
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
base: main
Are you sure you want to change the base?
Conversation
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.
Left a question but looks good to me 🙆♂️.
### Resolve policy issues | ||
After a scan has completed, automatic troubleshooting suggests recommended next steps for each policy issue. These may include adjusting specific {{elastic-defend}} policy settings or reviewing conflicting host configurations. Click **Learn more** to the right of a result to open Elastic documentation, which provides more context and guidance for resolving the issue. |
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.
Since not all policy response failure insights will have a Learn more
link, would it make sense to explicitly mention that so users don't mistake a missing Learn more
as a bug?
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.
LGTM
Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
Resolves #2968.
Previews: