|
| 1 | +--- |
| 2 | +applies_to: |
| 3 | + stack: preview 9.1 |
| 4 | + serverless: preview |
| 5 | +--- |
| 6 | + |
| 7 | +# Content connectors |
| 8 | + |
| 9 | +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. |
| 10 | + |
| 11 | +## Setup |
| 12 | +{{stack}} supports two deployment methods: Elastic managed, and self-managed. {{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. |
| 13 | + |
| 14 | +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: |
| 15 | + |
| 16 | +- Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content conectors". |
| 17 | +- Click **New Connector**. |
| 18 | +- Under **Connector**, select your desired data source. |
| 19 | +- Under **Setup**, select your deployment method. |
| 20 | +- 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. |
| 21 | +- 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**. |
| 22 | +- 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. |
| 23 | + |
| 24 | + |
| 25 | +## Manage a connector |
| 26 | + |
| 27 | +To manage an existing connector: |
| 28 | + |
| 29 | +- Use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find "Content connectors". |
| 30 | +- Click the connector you want to manage to open its settings page, which has six tabs: |
| 31 | + - **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. |
| 32 | + - **Documents**: View data from the connector. |
| 33 | + - **Mappings**: Update index mappings for the connector's data. |
| 34 | + - **Sync rules**: Use EQL to select which documents from the connector you wish to save. By default, all documents are saved. |
| 35 | + - **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. |
| 36 | + - **Configuration**: Edit the connector's data source-specific configuration. |
0 commit comments