> 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/olap/druid.md).

# Druid

**Apache** **Druid** is a real-time database to power modern analytics applications. Druid is designed to quickly ingest massive quantities of event data, and provide low-latency queries on top of the data.

**Apica Ascent** can connect to Druid to help you analyze your data.

### Adding Druid Data Source

The first step is to add Druid Data Source to your Apica Ascent. Fill out the below fields while configuring the data source

* **Name**: Name of the data source
* **Scheme (optional)**: HTTP/HTTPS scheme of your Druid instance
* **Host:** Host Endpoint point of your Druid Instance
* **Port:** Port address of your Druid Instance

![Selecting Druid data source](/files/WTIRmnAjf1kAYSBGI8Jt)

![Configuring Druid](/files/FAjJruHQzQmAs55Yfn95)

That's all. Now navigate to the Query editor page and start Querying


---

# 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/olap/druid.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.