Adds web crawler example to Knowledge Base doc #6176
Merged
Conversation
This file contains 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. |
acorretti
force-pushed
the
6157-knowledge-base-update
branch
from
4f74405 to
356789b
Compare
|
This pull request is now in conflicts. Could you fix it @benironside? 🙏 |
benironside
force-pushed
the
6157-knowledge-base-update
branch
from
356789b to
5fad163
Compare
| @@ -57,15 +57,15 @@ When Knowledge Base is enabled, AI Assistant receives `open` or `acknowledged` a | |||
| To enable Knowledge Base for alerts: | |||
|
|
|||
| . Ensure that knowledge base is <<enable-knowledge-base, enabled>>. | |||
| . Use the slider on the Security AI settings' Knowledge Base tab to select the number of alerts to send to AI Assistant. Click **Save**. | |||
| . Use the slider on the **Security AI settings** page's Knowledge Base tab to select the number of alerts to send to AI Assistant. Click **Save**. | |||
There was a problem hiding this comment.
I think that establishing the page first (instead of the slider on the tab) makes this a bit clearer.
Suggested change
| . Use the slider on the **Security AI settings** page's Knowledge Base tab to select the number of alerts to send to AI Assistant. Click **Save**. | |
| . On the **Security AI settings** page, go to the **Knowledge Base** tab and use the slider to select the number of alerts to send to AI Assistant. Click **Save**. |
| . Go to the **Manage Domains** tab. Select the domain associated with your new web crawler, then go the its **Crawl rules** tab and click **Add crawl rule**. For more information, refer to {enterprise-search-ref}/crawler-extraction-rules.html[Web crawler content extraction rules]. | ||
| .. Under **Policy**, select `Allow`. Under **Rule**, select `Contains`. Under **Path pattern**, enter your path pattern, for example `threat-intelligence`. Click **Save**. | ||
| .. Click **Add crawl rule** again. Under **Policy**, select `Disallow`. Under **Rule**, select `Regex`. Under **Path pattern**, enter `.*`. Click **Save**. Make sure this rule appears below the rule created in the previous step on the list. | ||
| .. Click **Crawl**, then **Crawl all domains on this index**. A message appears that says "Successfully scheduled a sync, waiting for a connector to pick it up". |
There was a problem hiding this comment.
This is slightly easier to maintain because you don't have to update the text if/when the copy changes.
Suggested change
| .. Click **Crawl**, then **Crawl all domains on this index**. A message appears that says "Successfully scheduled a sync, waiting for a connector to pick it up". | |
| .. Click **Crawl**, then **Crawl all domains on this index**. A success message appears. |
| .. Under **Policy**, select `Allow`. Under **Rule**, select `Contains`. Under **Path pattern**, enter your path pattern, for example `threat-intelligence`. Click **Save**. | ||
| .. Click **Add crawl rule** again. Under **Policy**, select `Disallow`. Under **Rule**, select `Regex`. Under **Path pattern**, enter `.*`. Click **Save**. Make sure this rule appears below the rule created in the previous step on the list. | ||
| .. Click **Crawl**, then **Crawl all domains on this index**. A message appears that says "Successfully scheduled a sync, waiting for a connector to pick it up". | ||
| . The crawl process will take longer for larger data sources. Once it finishes, your new web crawler's index will contain documents provided by the crawler. |
There was a problem hiding this comment.
This seems to be the result of an action, not so much a new step. Maybe add this to the end of step 5c, or at the end of step 5?
nastasha-solomon
approved these changes
Nov 20, 2024
mergify bot
pushed a commit
that referenced
this pull request
Nov 20, 2024
* Adds web crawler example to Knowledge Base doc * various minor edits * fixes note bug * incorporates James feedback * incorporates Charles' review * incorporates review (cherry picked from commit c5b5f65)
mergify bot
pushed a commit
that referenced
this pull request
Nov 20, 2024
* Adds web crawler example to Knowledge Base doc * various minor edits * fixes note bug * incorporates James feedback * incorporates Charles' review * incorporates review (cherry picked from commit c5b5f65)
benironside
added a commit
that referenced
this pull request
Nov 20, 2024
* Adds web crawler example to Knowledge Base doc * various minor edits * fixes note bug * incorporates James feedback * incorporates Charles' review * incorporates review (cherry picked from commit c5b5f65) Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
benironside
added a commit
that referenced
this pull request
Nov 20, 2024
* Adds web crawler example to Knowledge Base doc * various minor edits * fixes note bug * incorporates James feedback * incorporates Charles' review * incorporates review (cherry picked from commit c5b5f65) Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #6157 — Adds a new section to the ESS Knowledge Base doc that shows how to add a threat intelligence feed to Knowledge Base using an Elasticsearch web crawler.
Preview: Knowledge Base (new section is at the bottom)