-
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
Changes from 3 commits
51ab2e1
647937f
626ab8e
46d6836
f3edea0
6a6fb71
a73819a
616bbdb
a9df361
bb5900f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
applies_to: | ||
stack: preview 9.1 | ||
serverless: preview | ||
--- | ||
|
||
# Content connectors | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 |
||
|
||
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 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
|
||
|
||
- Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content conectors". | ||
- Click **New Connector**. | ||
- Under **Connector**, select your desired data source. | ||
- Under **Setup**, select your deployment method. | ||
- Under **Configure index & API key**, click **Generate configuration**. After a few seconds, this will create a new connector and a new index for its data, and display their names and IDs. You can click their names to view details about each. | ||
- Click **Next** to continue to the **Configuration** page. This is where you can select details related to your specific data source. For more information about configuring your selected data source, follow the link on the left to the **Connector reference**. | ||
- When configuration is complete, click **Next**. The **Finish up** page appears. Here you can set up recurring connector syncs, run a manual sync, or use queries and dev tools to interact with your data. Each sync updates the data in the connector's {{es}} index. You can also manage the connector. | ||
benironside marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
|
||
## Manage a connector | ||
|
||
To manage an existing connector: | ||
|
||
- Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content connectors". | ||
- Click the connector you want to manage to open its settings page, which has six tabs: | ||
- **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**: 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. |
Uh oh!
There was an error while loading. Please reload this page.