Data sources
A connector is one data source quanthea reads: a PostgreSQL database, a Prometheus server, a Loki instance, an HTTP API. Admins add and tune them in Connectors. Each connector says how much of its data the model may see, which columns it never sees, and how far a query may go.

Add a connector
- Connectors → Add a connector, and pick the kind. Plugins add more kinds; see Connectors and plugins.
- Name it: lowercase letters, digits and dashes. Dashboards refer to the connector by this name.
- Fill in the connection. The credentials are sealed with quanthea’s secret key and never shown again. A URL or a host must not hold a username or password: use the authentication fields.
- Save connection. quanthea tests it and reads the schema.
Give quanthea a read-only account. Queries always run read-only, and each kind refuses what isn’t a read (writes in SQL, scripts in a search, JavaScript in MongoDB, write commands in Valkey), but a role with read grants only is the hard guarantee. quanthea warns when a connection can write.
TimescaleDB
TimescaleDB is a PostgreSQL extension, so quanthea reads it with the PostgreSQL connector: its tile says “and TimescaleDB”, and searching for “timescale” finds it.
- The connection test names the extension’s version, such as “PostgreSQL 18.1 with TimescaleDB 2.30”.
- The schema lists hypertables, each with its time column and estimated row count, and continuous aggregates, each with the hypertable it summarises. Row counts come from TimescaleDB’s chunk statistics, not from reading the data.
- The agent buckets time with
time_bucketand fills empty buckets withtime_bucket_gapfill. Over a long range it reads a continuous aggregate rather than its hypertable, since it is already bucketed.
Access levels
The access level decides what the model sees of the source while it builds, answers and explains. It never limits what a dashboard shows: panels run their saved queries with no model.
| Level | The model sees |
|---|---|
| Schema only | Tables, columns, types. Nothing else. |
| Schema + metadata | Also row counts, the values of small columns, and the shape of a test run. |
| Aggregates | Also summaries of results: min, max, spikes, top values, and when. |
| Full access | Also result rows, capped at the row limit. |
Schema + metadata is the default. It is enough to build dashboards. Ask about this reads numbers only from sources at Aggregates or Full access; below that, answers can only explain. Alert replays in a conversation need Aggregates too.
Each thread shows the access of its sources under the question box.
A connector’s page

Hidden columns
Hide these columns from the model, by name: list columns such as customers.email, or a bare
name such as phone. They are removed from the schema and from every result before the model sees
it. Names match in any case. A hidden object, such as logs.user, hides every field under it.
A field that holds a hidden one is removed whole: hiding logs.user.email also removes a user
column that holds an array of user objects, and the schema marks user as holding a hidden field.
A column that ends with a hidden name, such as c.email, is removed too.
A query that renames a column gets past the name: its top values show at the aggregates level, its rows at full access. For data that must never leave, use a database role or a view that cannot read it.
Restricting access later
Lowering the access level or hiding a column applies to new tool calls. Data the model already read stays in its threads, and continuing a thread sends its conversation, that data included, to the model provider again.
Before such a change is saved, the page counts the threads that hold data it restricts and asks you to confirm. If the count fails, the page says why and still lets you save or cancel. Those threads are then marked Restricted data in the past threads list, and each shows a notice above the question box. Start a new thread to leave that data out.
The count and the mark follow the model’s tool calls. The model also gets a short list of field values with each question, read at the access in force then. An earlier answer that quoted one of those values, with no tool call, is not counted or marked.
Guardrails
| Guardrail | Default | What it does |
|---|---|---|
| Query timeout (seconds) | 10 | A query stops after this long. |
| Max rows per query | 50,000 | A result is cut at this many rows. |
| Max time range (days) | 90 | A panel can’t ask for a longer range. |
They apply to everything that runs a query: panels, alerts, report runs, snapshots and the model.
The schema and descriptions
The page lists the tables or metrics the model sees, as it sees them at this level. Write a description for a table or a column when its name doesn’t say enough: the model reads yours in place of the source’s.
Health
The list shows each connector’s last test. A failing source shows on its panels as a safe error, and alerts on it say they cannot be checked.
In the configuration file
Connectors can be declared in the configuration file, with their credentials as references to environment variables or files. Their settings are then read-only here; descriptions stay editable unless the file declares them. See the configuration file.