Elasticsearch
by Elastic
Elasticsearch often stores logs, product catalogs and search events in indices tuned for text search. Its REST API returns documents, search results, aggregations, index metadata and cluster stats. Copying selected indices into the Lake lets that data be joined with customers and transactions, which Elasticsearch is not designed for, and kept beyond index retention.
- Category
- Cloud & Data Platforms
- Type
- Search engine
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- API key, Username and password
02Data
What you can sync.
- Documents
- Search results
- Aggregations
- Indices
- Cluster stats
Load Elasticsearch documents into your Lake and model it in the Warehouse with the rest of your stack.
Need more? Name any other Elasticsearch data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- An API key
- A username and password
Elasticsearch uses an API key or a username and password. You add the credentials once, when the AI asks for them, and it tells you where to create them in Elastic if you need help.
04Questions
Questions you can answer.
Once Elasticsearch data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which customers generated the most error log entries last week, and what plan are they on?
- How do on-site search queries stored in Elasticsearch relate to orders in the following hour?
- Which indices grew more than 10 percent this month, and what share of cluster storage do they use?
- How many documents in the product index are missing prices or categories?
05How it works
How it works in DataMind.
-
Pick Elasticsearch.
Open Lake, pick Elasticsearch in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Elasticsearch API docs.
-
Answer a few questions.
The AI reads the Elasticsearch documentation, then asks which credentials you will use, which data to sync (for example documents and search results), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Elasticsearch data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Elasticsearch.
Sources teams join with Elasticsearch in the Warehouse, each one connected the same way.
