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:

@natasha-moore-elastic natasha-moore-elastic self-assigned this Oct 3, 2025
@github-actions
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
@natasha-moore-elastic natasha-moore-elastic marked this pull request as ready for review October 6, 2025 09:22
@natasha-moore-elastic natasha-moore-elastic requested a review from a team as a code owner October 6, 2025 09:22
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

@natasha-moore-elastic natasha-moore-elastic merged commit 383d9c4 into main Oct 8, 2025
7 checks passed
@natasha-moore-elastic natasha-moore-elastic deleted the issue-2968-a-t branch October 8, 2025 15:05
rhr323 pushed a commit to rhr323/docs-content that referenced this pull request Oct 27, 2025
…stic#3318)

Resolves elastic#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:
* [Automatic
troubleshooting](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3318/solutions/security/manage-elastic-defend/automatic-troubleshooting)
* [AI use cases > Other AI-powered
tools](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3318/solutions/security/ai/use-cases#other-ai-powered-tools)

---------

Co-authored-by: florent-leborgne <[email protected]>
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

4 participants