[Security Solution] [AI assistant] Docs for AI assistant esql generation with self healing #6934
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
|
/ci |
|
run docs-build |
KDKHD
changed the title
KDKHD
changed the title
benironside
reviewed
Jul 22, 2025
|
|
||
| Elastic AI Assistant allows you to take full advantage of the {elastic-sec} platform to improve your security operations. It can help you write an {esql} query for a particular use case, or answer general questions about how to use the platform. Its ability to assist you depends on the specificity and detail of your questions. The more context and detail you provide, the more tailored and useful its responses will be. | ||
|
|
||
| NOTE: The agent has access to index names and field metadata from your cluster. This contextual information helps improve ES|QL generation, though it may slightly increase response times. |
There was a problem hiding this comment.
Suggested change
| NOTE: The agent has access to index names and field metadata from your cluster. This contextual information helps improve ES|QL generation, though it may slightly increase response times. | |
| NOTE: AI Assistant has access to index names and field metadata from your cluster. This contextual information helps improve {{esql}} generation, however it may slightly increase response times. |
How would the user control whether this metadata is included?
There was a problem hiding this comment.
They can't control this currently. I will speak with the team to see what they think about giving the user control over this.
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
KDKHD
commented
Aug 4, 2025
benironside
approved these changes
Aug 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: https://github.com/elastic/docs-content-internal/issues/102
Update Security documentation to reflect changes to how the Security AI assistant generates ES|Ql.
9.1 PR: elastic/docs-content#2168