Skip to content

Conversation

natasha-moore-elastic
Copy link
Contributor

@natasha-moore-elastic natasha-moore-elastic commented Oct 3, 2025

Resolves #2968.

  • Updates applies_to tags to reflect that automatic troubleshooting is going GA.
  • Adds new functionality (policy issues troubleshooting) to the automatic troubleshooting feature. The existing page (Identify antivirus software on your hosts) has been renamed to Automatic troubleshooting and expanded to include the new functionality (new sections: Automatic troubleshooting and Troubleshoot policy issues)

Previews:

Copy link

github-actions bot commented Oct 3, 2025

@natasha-moore-elastic natasha-moore-elastic marked this pull request as ready for review October 3, 2025 15:28
@natasha-moore-elastic natasha-moore-elastic requested review from a team as code owners October 3, 2025 15:28
@natasha-moore-elastic natasha-moore-elastic marked this pull request as draft October 3, 2025 15:28
@natasha-moore-elastic natasha-moore-elastic changed the title [Security] Automatic troubleshooting updates [Security] [Serverless: Oct 7] Automatic troubleshooting updates Oct 3, 2025
Copy link
Member

@joeypoon joeypoon left a 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.
Copy link
Member

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?

Copy link
Contributor

@florent-leborgne florent-leborgne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Internal]: Doc updates/additions for automatic troubleshooting GA
3 participants