Skip to main content
Elasticsearch

Elasticsearch

PROD
In this section, we provide guides and references to use the Elasticsearch connector. Configure and schedule Elasticsearch metadata workflow from the OpenMetadata UI:

​
Requirements

We support Elasticsearch 7.0 and above. We extract Elasticsearch’s metadata by using its API. To run this ingestion, you just need a user with permissions to the ElasticSearch instance.

​
Metadata Ingestion

1

Visit the Services Page

Click `Settings` in the side navigation bar and then `Services`. The first step is to ingest the metadata from your sources. To do that, you first need to create a Service connection first. This Service will be the bridge between OpenMetadata and your source system. Once a Service is created, it can be used to configure your ingestion workflows.Visit Services Page
2

Create a New Service

Click on _Add New Service_ to start the Service creation.Create a new Service
3

Select the Service Type

Select ElasticSearch as the Service type and click _Next_.Select Service
4

Name and Describe your Service

Provide a name and description for your Service.

Service Name

OpenMetadata uniquely identifies Services by their **Service Name**. Provide a name that distinguishes your deployment from other Services, including the other ElasticSearch Services that you might be ingesting metadata from. Note that when the name is set, it cannot be changed.Add New Service
5

Configure the Service Connection

In this step, we will configure the connection settings required for ElasticSearch. Please follow the instructions below to properly configure the Service to read from your sources. You will also find helper documentation on the right-hand side panel in the UI.Configure Service connection

​
Connection Details

1

Connection Details

When using a Hybrid Ingestion Runner, any sensitive credential fields—such as passwords, API keys, or private keys—must reference secrets using the following format:
password: secret:/my/database/password
This applies only to fields marked as secrets in the connection form (these typically mask input and show a visibility toggle icon). For a complete guide on managing secrets in hybrid setups, see the Hybrid Ingestion Runner Secret Management Guide.
  • Host and Port: This parameter specifies the host and port of the Elasticsearch instance. This should be specified as a URI string in the format http://hostname:port or https://hostname:port. For example, you might set it to https://localhost:9200.
  • Authentication Types:
    1. Basic Authentication
    • Username: Username to connect to Elasticsearch required when Basic Authentication is enabled on Elasticsearch.
    • Password: Password of the user account to connect with Elasticsearch.
    1. API Key Authentication
    • API Key: API Key to connect to Elasticsearch required when API Key Authentication is enabled on Elasticsearch.
    • API Key Id: Enter API Key ID In case of API Key Authentication if there is any API Key ID associated with the API Key, otherwise this field can be left blank.
  • SSL Certificates:
    1. SSL Certificates By Path
    • CA Certificate Path: This field specifies the path of CA certificate required for authentication.
    • Client Certificate Path: This field specifies the path of Clint certificate required for authentication.
    • Private Key Path: This field specifies the path of Clint Key/Private Key required for authentication.
    1. SSL Certificates By Value
    • CA Certificate Value: This field specifies the value of CA certificate required for authentication.
    • Client Certificate Value: This field specifies the value of Clint certificate required for authentication.
    • Private Key Value: This field specifies the value of Clint Key/Private Key required for authentication.
    • Staging Directory Path: This field specifies the path to temporary staging directory, where the certificates will be stored temporarily during the ingestion process, which will de deleted once the ingestion job is over.
    • when you are using this approach make sure you are passing the key in a correct format. If your certificate looks like this:
    -----BEGIN CERTIFICATE-----
MII..
MBQ...
CgU..
8Lt..
...
h+4=
-----END CERTIFICATE-----
    You will have to replace new lines with \n and the final value that you need to pass should look like this: 
    -----BEGIN CERTIFICATE-----\nMII..\nMBQ...\nCgU..\n8Lt..\n...\nh+4=\n-----END CERTIFICATE-----\n
  • Connection Timeout in Seconds: Connection timeout configuration for communicating with Elasticsearch APIs.
2

Test the Connection

Once the credentials have been added, click on Test Connection and Save the changes.Test Connection
3

Configure Metadata Ingestion

In this step we will configure the metadata ingestion pipeline, Please follow the instructions belowConfigure Metadata Ingestion

​
Metadata Ingestion Options

  • Name: This field refers to the name of ingestion pipeline, you can customize the name or use the generated name.
  • Search Index Filter Pattern (Optional): Use to search index filter patterns to control whether or not to include search index as part of metadata ingestion.
    • Include: Explicitly include search index by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all search indexes with names matching one or more of the supplied regular expressions. All other schemas will be excluded.
    • Exclude: Explicitly exclude search index by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all search indexes with names matching one or more of the supplied regular expressions. All other schemas will be included.
  • Include Sample Data (toggle): Set the Ingest Sample Data toggle to control whether to ingest sample data as part of metadata ingestion.
  • Sample Size: If include sample data is enabled, 10 records will be ingested by default. Using this field you can customize the size of sample data.
  • Include Index Templates (toggle): Set the Include Index Templates toggle to control whether to include index templates as part of metadata ingestion.
  • Override Metadata: Set the Override Metadata toggle to control whether to override the metadata if it already exists.
  • Enable Debug Log (toggle): Set the Enable Debug Log toggle to set the default log level to debug.
4

Schedule the Ingestion and Deploy

Scheduling can be set up at an hourly, daily, weekly, or manual cadence. The timezone is in UTC. Select a Start Date to schedule for ingestion. It is optional to add an End Date.Review your configuration settings. If they match what you intended, click Deploy to create the service and schedule metadata ingestion.If something doesn’t look right, click the Back button to return to the appropriate step and change the settings as needed.After configuring the workflow, you can click on Deploy to create the pipeline.Schedule the Workflow
5

View the Ingestion Pipeline

Once the workflow has been successfully deployed, you can view the Ingestion Pipeline running from the Service Page.View Ingestion Pipeline
If AutoPilot is enabled, workflows like usage tracking, data lineage, and similar tasks will be handled automatically. Users don’t need to set up or manage them - AutoPilot takes care of everything in the system.