Data catalogue

Sources

Create, test, pause, and reconnect the systems Chartizer reads from.

A source is one connected system plus its credentials and runtime. The Sources tab lists every source in the team with its health, runtime, dataset count, and last successful sync.

Add a source

Choose a connector

Click Add data, or pick one from Quick add on the Overview tab.

Choose a runtime

Runtime Where queries execute Use when
Cloud Chartizer Cloud The system is reachable from the internet
Local agent Your machine or network Secrets must stay on your infrastructure

Enter connection details

Field names differ per connector, but the shape is the same: an address, a credential, and a scope (database, index, or file location).

Test and create

Chartizer runs a connection test before saving. A failed test tells you which stage failed — DNS, TCP, TLS, authentication, or permissions.

Never use a superuser

Create a dedicated read-only role for Chartizer. If a connector only ever reads, it should never hold write permission.

Grant the narrowest access that still lets Chartizer introspect the schema.

PostgreSQL read-only role
CREATE ROLE chartizer_reader LOGIN PASSWORD 'use-a-generated-secret';

GRANT CONNECT ON DATABASE analytics TO chartizer_reader;
GRANT USAGE ON SCHEMA public TO chartizer_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO chartizer_reader;

-- keep new tables readable as the schema grows
ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT SELECT ON TABLES TO chartizer_reader;

Source health

Every source is in exactly one state.

State Meaning
Active Connected and syncing on schedule
Syncing A refresh is in progress
Auth error Credentials rejected — reconnect required
Unreachable Network or DNS failure, credentials untested
Paused Deliberately stopped; frees a plan slot

Reconnect a source

When a source shows Authentication expired, click Reconnect from the Needs attention queue or from the source’s detail page.

  • Database connectors (PostgreSQL, MySQL, Neo4j) ask for the new password only — host, port, and database are preserved.
  • Key-based connectors (Elasticsearch, fetched file feeds) ask for the new API key or token.

Reconnecting does not rebuild datasets

Datasets and the charts built on them survive a reconnect. They resume on the next sync.

Pause and delete

Pausing stops scheduled syncs and frees a plan slot. Datasets stay in the catalogue and keep their last synced data; charts continue to render, marked stale.

Deleting removes the source and its datasets. Chartizer lists every affected project before asking you to confirm.

Deletion cascades

Deleting a source with three datasets that feed five charts breaks all five charts. The confirm dialog names them — read it before typing the source name.