> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/data-sources/time-series-databases/elasticsearch-data-source.md).

# Elasticsearch

## Create the Elasticsearch data source

The first step is to create the data source and provide the Elasticsearch cluster URL and optionally provide  the basic auth `login` and `password`.

![Configuring the Elasticsearch data source](/files/D82wmAdxcSnOiplolZWF)

## Writing queries

In the query editor view, select the *Elasticsearch data source* created above. On the left column, click on the refresh <img src="/files/-MEQul15FkfgLR3MdC0b" alt="" data-size="original"> icon to refresh the schemes (indexes). The schemes are expandable and show the schema details.

![Refresh and lookup Elasticsearch indexes](/files/AaSaPmM2nA6zuVcgh7hk)

You can then proceed to the query editor and run the search query. The query uses JSON as passed to the Elasticsearch search API

![Writing a search query against an Elasticsearch index](/files/PeyOcu8kQgqFjSxJtwIl)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apica.io/data-sources/time-series-databases/elasticsearch-data-source.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
