Telemetry storage

Connect one organization-scoped ClickHouse deployment, verify connectivity and required tables, and plan schema updates safely.

The Telemetry page connects an organization to a customer-managed ClickHouse deployment used by Noveum’s telemetry services. This is infrastructure configuration, not the SDK endpoint your application sends traces to.

Current limits and access

The current dashboard supports:

• ClickHouse only;
• one telemetry plugin per organization;
• development, staging, or production as the plugin environment;
• enabled/disabled and default flags.

API authorization evaluates organization-scoped telemetry_plugins:read, telemetry_plugins:write, and telemetry_plugins:delete permissions. The built-in Admin and Developer roles can manage plugins; AI Engineer has read access. See Roles and permissions before delegating this infrastructure action.

Add a connection

Open Telemetry → Add plugin and enter:

Field	Meaning
Name	A recognizable label for the deployment
Host	ClickHouse hostname or service address reachable from Noveum. Enter credentials only in their dedicated fields.
Port	ClickHouse HTTP interface port. The form starts at 8123; use the port your deployment exposes for HTTP or HTTPS. Secure HTTP commonly uses 8443.
Database	Database containing the Noveum telemetry tables; defaults to default
Username	ClickHouse user; defaults to default
Password	Optional credential for that user
SSL	Uses HTTPS for the configured port. The switch does not change Port, so set both values to match the deployment.
Environment	Deployment label for the plugin
Enabled	Makes the saved plugin available to telemetry services
Default	Marks it as the organization’s default telemetry plugin

Store credentials in the form only. Do not copy the password into tickets, source files, screenshots, or documentation.

Because only one plugin is allowed, add is unavailable after a connection exists. Edit or delete the existing plugin when the deployment changes.

Test the connection

Select Test connection after saving. The dashboard runs five stages in order:

1. Checking Connection - reaches the configured HTTP or HTTPS endpoint.
2. Checking User Access - runs a basic SELECT 1 query.
3. Checking Tables - opens each required table name and records which are missing.
4. Creating Tables - runs the declared table and index DDL for each missing table when permitted.
5. Verification - confirms that every required table name can be opened after the create step.

The modal reports each stage, individual table substeps, durations, and any returned error. It does not compare the current migration stamp, prove that the columns and indexes on an existing table match the current release, or perform a write/read round trip. A green result means the endpoint and required table names are usable; it is not confirmation that every schema migration is current.

Schema lifecycle after setup

An enabled customer-managed connection is not treated as read-only. Noveum retains lazy schema initialization for these plugin clusters, and platform migration tooling can apply the current ordered schema plan to enabled connections. The plan is limited to Noveum-owned tables, but it can create tables and add, modify, materialize, or remove Noveum-owned columns and indexes as the product schema evolves.

Customer-managed clusters are checked separately from Noveum’s in-house deployment gate. A stale or unreachable customer cluster does not block the in-house rollout, so a successful platform release is not proof that your cluster has the current migration stamp.

If your policy does not allow runtime DDL, coordinate an operator-managed migration and validation process with Noveum before enabling the connection or adopting a release that needs a schema change. Do not reduce the ClickHouse user to read/write-only access solely because Test connection is green.

Change or remove the plugin

Editing updates the same organization-scoped plugin. Test again after changing host, port, database, user, password, SSL, environment, or enabled/default state, then validate migration readiness separately.

Deleting the plugin removes Noveum’s saved connection configuration. It does not document or guarantee deletion of the remote ClickHouse database itself. Confirm retention and cleanup directly in ClickHouse before or after removal, according to your policy.

Troubleshooting

Stage	Check first
Connection	Host, the actual HTTP or HTTPS port, SSL mode, DNS, firewall, and network allowlists
User access	Username, password, database selection, and permission to run a basic query
Tables	Correct database and permission to open every required table
Creating tables	CREATE TABLE/ALTER TABLE permission and any cluster-specific DDL policy
Verification	Access to every required table name and stable connectivity
Schema evolution	Migration readiness for existing columns and indexes; the dashboard test does not check the migration stamp

If a test fails after a configuration change, preserve the previous values outside the browser only in an approved secret store, restore the known-good connection, and test again before removing the old deployment.

Related

• Workspace administration
• Quick setup
• Projects
• Analytics