> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt > Use this file to discover all available pages before exploring further. # QuestDB Connector > Connect QuestDB to Collate with our comprehensive connector guide. Set up metadata ingestion and view lineage extraction in minutes. export const ConnectorDetailsHeader = ({name, icon, stage, availableFeatures, unavailableFeatures = [], availableFeaturesCollate = []}) => { const showSubHeading = availableFeatures?.length > 0 || unavailableFeatures?.length > 0 || availableFeaturesCollate?.length > 0; const totalAvailableFeatures = [...availableFeatures || [], ...availableFeaturesCollate || []]; return

{icon &&

}

{name}

{stage}

{showSubHeading &&

Feature List

{totalAvailableFeatures.map(feature =>

✓ {feature}

)} {unavailableFeatures.map(feature =>

✕ {feature}

)}

}

; }; This section provides guides and references to use the QuestDB connector. Configure and schedule QuestDB metadata and lineage workflows from the Collate UI: * [Requirements](#requirements) * [Metadata Ingestion](#metadata-ingestion) * [Troubleshooting](/ai-2-0/connectors/database/questdb/troubleshooting) ## Requirements QuestDB exposes metadata through its built-in table functions (`tables()`, `views()`, `materialized_views()`, and `table_columns()`). Any authenticated user can call these functions — no additional database grants are required beyond valid credentials and network access to the QuestDB PostgreSQL wire protocol port (default: **8812**). **Note**: On QuestDB Enterprise, role-based access control (RBAC) is enforced at the connection endpoint. In addition to valid credentials, the service account must be granted PGWIRE endpoint access, or the connection is refused even though authentication succeeds: ```sql theme={null} GRANT PGWIRE TO ''; ``` ## Metadata Ingestion To ingest metadata from QuestDB, you need to create a service connection. The service connects QuestDB with Collate. Once you create a service, Collate automatically starts ingesting metadata. ### Step 1: Add New Service 1. In the left navigation, click **Connections**. 2. On the **Connections** page, click **Add New Service**.

### Step 2: Select a Service and Connector From the service type dropdown, select **Database Services**, then click the **QuestDB** connector tile. Select Service

### Step 3: Add Service Name and Description * Enter a unique, descriptive **Service Name**. Collate identifies services by their service name. Enter a name that distinguishes this deployment from other QuestDB services you are ingesting metadata from. * Optional: Enter a **Description** for the service. Add New Service Name

**Note**: The service name cannot be changed after it is set. ### Step 4: Configure Connection Options Specify where ingestion runs, provide your source credentials, and verify the connection. #### Select Ingestion Runner Select an **Ingestion Runner**: the runner where the ingestion pipeline will execute. Add Name and Select Ingestion Runner

#### Enter Connection Details Enter the connection details for QuestDB. The right-hand panel in the UI displays inline help for each field. Configure Service Connection

* **Username**: Username to connect to QuestDB. Ensure you have enough privileges to read all the metadata. * **Password**: Password for the QuestDB user. * **Host and Port**: Host and port of the QuestDB service. QuestDB exposes the PostgreSQL wire protocol on port **8812** by default (for example, `localhost:8812`). * **Connection Options** (optional): Additional connection options to pass to the database during connection as Key-Value pairs. * **Connection Arguments** (optional): Additional connection arguments such as security or protocol configs as Key-Value pairs. #### Test Connection Once the credentials have been added, click on **Test Connection** and **Save** the changes.

### Step 5: Configure Ingestion Options In the **What to Ingest** step, use filter patterns to control which assets Collate ingests from your database service. Filter patterns use regular expressions applied to asset names. #### How Filter Patterns Work * **Include**: Add one or more comma-separated regular expressions. Collate ingests only assets whose names match at least one expression. Leave blank to include all assets. * **Exclude**: Add one or more comma-separated regular expressions. Collate skips any asset whose name matches an expression. Leave blank to exclude nothing. Rules match asset names using one of five expressions: * **contains**: matches any name containing the value. For example, `sales` matches `my_sales_data` and `sales_2024`. * **starts with**: matches names beginning with the value. For example, `prod_` matches `prod_db` and `prod_schema`. * **ends with**: matches names ending with the value. For example, `_raw` matches `events_raw` and `logs_raw`. * **is exactly**: matches the exact name only. For example, `analytics` matches only `analytics`. * **matches regex**: matches names using a regular expression. For example, `^prod_.*_v\d+$` matches `prod_events_v1`. When both Include and Exclude are set, Exclude takes priority. **Tip**: Leave all filter patterns empty to ingest all databases, schemas, and tables available in the source. **Filter Options** The Database, Schema, and Table sections each include the following filter options: * **Database**: Controls which databases Collate ingests from the source. * **Schema**: Controls which schemas within the ingested databases are included. * **Table**: Controls which tables and views within the ingested schemas are included. Each section provides the following controls: * **Scan Mode**: Choose between **Scan all** (default) or **Only specific** to enable include rules. * **Always exclude**: Add permanent exclusion rules. Assets matching these rules are never ingested, regardless of include rules. * **Preview**: Shows a real-time summary of what will be in scope based on your current rules. * **Include rules** *(available only in **Only specific** mode)*: Click **+ Add** to define a rule. **Tip**: If [AutoPilot](/ai-2-0/admin-guide/applications/autopilot) is enabled, usage tracking, data lineage, and other downstream workflows start automatically after the first metadata ingestion completes. ### Step 6: Create & Deploy Click **Create & Deploy** to deploy the agent and start the first metadata ingestion run. Collate saves the service configuration and immediately begins pulling metadata from the source. To monitor ingestion progress or view the service you just added, go to **Connections** in the left navigation and select your service. ## Configure Metadata Agent and Schedule Ingestion The **Metadata Agent** extracts schemas, tables, columns, and other structural metadata from your source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets. When you click **Create & Deploy**, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the **Agents** tab on the service detail page. To configure the additional Metadata Agent and schedule ingestion, follow these steps: 1. In the left navigation, click **Connections** and select your service. 2. Click the **Agents** tab. 3. Click **Add Agent** and select **Metadata** from the dropdown. Add Metadata Agent

For some services, the dropdown is not available and clicking **Add Agent** takes you directly to the agent configuration page. 4. On the **Configure Ingestion** page, do the following and click **Next**. * **Name this Ingestion**: Enter a unique recognizable name for this ingestion pipeline.

* **Agent Setup**: Configure core parameters for metadata extraction. The following fields are available: | Field | Default | Description | | ------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------ | | Default Owner | — | Owner applied to all entities when no specific level owner is configured. Accepts a user or team name/email. | | Service Owner | — | Owner assigned to the service entity. | | Database Owner | — | Owner assigned to all ingested databases. Accepts a single owner or a per-database name mapping. | | Database Schema Owner | — | Owner assigned to all ingested schemas. Accepts a single owner or a per-schema name mapping. | | Table Owner | — | Owner assigned to all ingested tables. Accepts a single owner or a per-table name mapping. | | Enable Inheritance | On | When on, child entities inherit the owner from their parent when they have no owner configured. | | Query Log Duration | 1 | Number of days to look back in query logs when processing stored procedure results. | | Query Parsing Timeout Limit | 300 | Timeout in seconds for parsing a single query. | | Number of Threads | 1 | Number of threads to use for parallel table ingestion. | | Incremental Extraction | Off | When enabled, subsequent runs only extract entities changed since the last successful run. | | Successful Pipeline Run Lookback Days | 7 | Number of days to search back for a prior successful run to use as a baseline for incremental extraction. | | Safety Margin Days | 1 | Additional days added to the baseline timestamp as a buffer for incremental extraction. | | JSON Schema Sample Size | 10 | Number of rows sampled to infer JSON column schema. Only applies when Extract JSON Schema is enabled in Advanced Config. | Agent Setup

* **Filter Patterns**: Apply include or exclude rules to scope which databases, schemas, tables, and stored procedures this agent ingests. For more information about various filter options, see **Step 5: Configure Ingestion Options**.

* **Scope & Behaviour**: Control how the agent handles metadata during ingestion. Toggle each option on or off based on your needs: | Toggle | Default | Description | | ------------------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Include Tables | On | Ingest table metadata from the source. Turn off to skip tables entirely. | | Include Tags | On | Ingest tags from the source. | | Include Stored Procedures | On | Ingest stored procedure metadata. | | Include DDL Statements | Off | Ingest DDL statements alongside table metadata. | | Include Owners | Off | Assign owners to ingested entities when the source owner's email matches a user in Collate. Does not overwrite an existing owner. | | Include Custom Properties | Off | Ingest connector-specific custom properties onto entities. | | Mark Deleted Tables | On | Soft-delete tables in Collate when they are removed from the source. Applies only within the currently ingested schema. | | Mark Deleted Stored Procedures | On | Soft-delete stored procedures in Collate when they are removed from the source. | | Mark Deleted Schemas | Off | Soft-delete schemas and all their child assets when removed from the source. | | Mark Deleted Databases | Off | Soft-delete databases and all their child assets when removed from the source. | | Override Metadata | Off | When on, source values overwrite existing descriptions, tags, owners, and display names in Collate. When off, Collate only updates fields that have no existing value. | | Enable Debug Log | Off | Sets the ingestion log level to DEBUG. Useful for troubleshooting. | **Note**: Available toggles vary by connector. Stored procedure options only appear for connectors that support stored procedures. Scope & Behaviour

* **Advanced Config**: Optional connector-specific settings such as Include Views and Extract JSON Schema.

5. On the **Schedule Interval** page, set when the agent runs: * **Schedule**: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression. * **On-Demand**: No automatic schedule; trigger the agent manually when needed.

6. Click **Add** to deploy the agent. ## Troubleshooting Learn more about how to troubleshoot common QuestDB connector issues and resolve configuration or ingestion errors.