> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/databases/druid.md).

# Druid

An overview of the Druid integration with Secoda

## Getting Started with Druid

There are 3 steps to get started using Druid with Secoda:

1. Retrieve Druid Host and Port.
2. Retrieve Username and Password
3. Connect Druid to Secoda

### **Retrieve Druid Host and Port** <a href="#h_b3f5c96bd0" id="h_b3f5c96bd0"></a>

Identify the host domain and **port** used to access your Druid instance. These can be derived from the URL you use to access Druid in your browser:

* Format: `http://<host-domain>:<port>/`
* Default port: `8888`.

### **Retrieve Username and Password**

Druid **requires authentication** to connect. Ensure you have the correct **username** and **password** that you use to log in to your Druid instance.

### **Connect Druid to Secoda**

After retrieving all necessary credentials, the next step is to connect to Secoda.

1. In the Secoda App, select ‘Add Integration’ on the Integrations tab
2. Search for and select Druid
3. Enter your Druid credentials (host domain, port + username, password if applicable)
4. Click 'Connect'


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/databases/druid.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.