-
Notifications
You must be signed in to change notification settings - Fork 163
Creates content connectors page in security docs #2113
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
51ab2e1
Creates content connectors page in security docs
benironside 647937f
fixes broken attribute
benironside 626ab8e
Apply suggestions from code review
benironside 46d6836
Merge branch 'main' into 34-Elastic-Connectors-in-Security
benironside f3edea0
Update solutions/security/get-started/content-connectors.md
benironside 6a6fb71
Merge branch 'main' into 34-Elastic-Connectors-in-Security
colleenmcginnis a73819a
Update content-connectors.md
benironside 616bbdb
Merge branch 'main' into 34-Elastic-Connectors-in-Security
benironside a9df361
Apply suggestions from code review
benironside bb5900f
Merge branch 'main' into 34-Elastic-Connectors-in-Security
benironside File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,10 +6,10 @@ | |
|
||
# Content connectors | ||
|
||
Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, PagerDuty, Jira, OpsGenie, Teams, Google Drive, Slack, email, and more. To see a complete list of the available connectors, follow the setup instructions below. | ||
Elastic's content connectors allow you to extract, transform, index, and sync data from third-party applications including Github, PagerDuty, Jira, Teams, Google Drive, Slack, email, and more. [View all available connectors](elasticsearch://reference/search-connectors/index.md) | ||
|
||
## Setup | ||
{{stack}} supports two deployment methods: Elastic managed, and self-managed. {{sec-serverless}} only supports Elastic managed deployments. Self-managed deployments require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed deployments use agentless technology and do not allow customization. | ||
{{stack}} supports two deployment methods for your connectors: Elastic managed, and self-managed. {{sec-serverless}} only supports Elastic managed connectors. Self-managed connectors require you to manage the {{elastic-agent}} that forwards data to Elastic and allow you to customize the connector's code, whereas Elastic managed connectors use agentless technology and do not allow customization. | ||
|
||
To learn about set up for self-managed connectors, refer to [Self managed connectors](elasticsearch://reference/search-connectors/self-managed-connectors.md). To set up an Elastic managed connector: | ||
benironside marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
|
@@ -31,6 +31,6 @@ | |
- **Overview**: View general information such as the connector's name, ID, status, pipeline, and content sync history. Manage the connector's pipeline and attached index. | ||
- **Documents**: View data from the connector. | ||
- **Mappings**: Update index mappings for the connector's data. | ||
- **Sync rules**: Use EQL to select which documents from the connector you wish to save. By default, all documents are saved. | ||
- **Sync rules**: Manage basic and advanced [sync rules](elasticsearch://reference/elasticsearch/search-connectors/es-sync-rule.md) to control which documents are synced from your third-party data source. | ||
Check failure on line 34 in solutions/security/get-started/content-connectors.md
|
||
benironside marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
- **Scheduling**: Define when data from this connector gets synced, and set up document level security. A `Full content sync` deletes existing data in your index before fetching from your data source again. An `Incremental content sync` fetches updated data only, without deleting existing data. | ||
- **Configuration**: Edit the connector's data source-specific configuration. |
Oops, something went wrong.
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.
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.
General remark, I haven't seen the new security UI, so consider adding a screenshot to this page if it would be helpful here, especially if it differs from previous generation of connector UIs