Skip to main content
Telara

Integrations / Elasticsearch

Elasticsearch logo

Elasticsearch

Elasticsearch is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases

API key
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

An Elasticsearch or Elastic Cloud cluster Telara can reach.
A user who can open Kibana Stack Management (or Elasticsearch security) and create API keys.

Vendor setup

Get the credential

1
Open Stack Management
In Kibana, go to Stack Management → Security → API Keys (wording is API keys under Management on Elastic Cloud).
2
Create an API key
Click Create API key. Name it for Telara. Restrict it to the cluster (and indexes) Telara should see. Copy the encoded key immediately.
3
Paste in Telara
Settings → Integrations → Elasticsearch. Enter the Elasticsearch API URL (not the Kibana URL) and the key. Username and password are a fallback if your cluster still uses native realm users.

In Telara

Connect in Telara

API key

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • Base Url
  • API key
Basic auth

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Base Url
  • Username
  • Password

Knowledge

What gets indexed

ResourceCoverage
Index schemaPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
Index schemaUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Index schema.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

The URL must be the Elasticsearch API host (often :9200 or *.es.amazonaws.com), not the Kibana UI host.
A key that can authenticate but cannot list indexes produces an empty view, not an auth error.