Managed

The configuration above assumes an Nginx-style schema with a `time_local` column used as the timestamp. This should be, where possible, the timestamp column declared in the primary key. **This column is mandatory**.

We also recommend updating the `Default SELECT` to explicitly define which columns are returned in the logs view. If additional fields are available, such as service name, log level, or a body column, these can also be configured. The timestamp display column can also be overridden if it differs from the column used in the table's primary key and configured above.

In the example above, a `Body` column doesn't exist in the data. Instead, it is defined using a SQL expression that reconstructs an Nginx log line from the available fields.

For other possible options, see the [configuration reference](/docs/use-cases/observability/clickstack/config#hyperdx).

Once the source is configured, click "Save" and begin exploring your data.

## Additional tasks[​](#additional-tasks "Direct link to Additional tasks")

### Granting access to Managed ClickStack[​](#configure-access "Direct link to Granting access to Managed ClickStack")

1. Navigate to your service in the ClickHouse Cloud console
2. Go to **Settings** → **SQL Console Access**
3. Set the appropriate permission level for each user:
   - **Service Admin → Full Access** - Required for enabling alerts
   - **Service Read Only → Read Only** - Can view observability data and create dashboards
   - **No access** - Can't access HyperDX

Alerts require admin access

To enable alerts, at least one user with **Service Admin** permissions (mapped to **Full Access** in the SQL Console Access dropdown) must log into HyperDX at least once. This provisions a dedicated user in the database that runs alert queries.

### Using ClickStack with read-only compute[​](#clickstack-read-only-compute "Direct link to Using ClickStack with read-only compute")

The ClickStack UI can run entirely on a read-only ClickHouse Cloud service. This is the recommended setup when you want to isolate ingestion and query workloads.

#### How ClickStack selects compute[​](#how-clickstack-selects-compute "Direct link to How ClickStack selects compute")

ClickStack UI always connects to the ClickHouse service from where it is launched in the ClickHouse Cloud console.

This means:

- If you open ClickStack from a read-only service, all queries issued by ClickStack UI will run on that read-only compute.
- If you open ClickStack from a read-write service, ClickStack will use that compute instead.

No additional configuration inside ClickStack is required to enforce read-only behavior.

#### Recommended setup[​](#recommended-setup "Direct link to Recommended setup")

To run ClickStack on read-only compute:

1. Create or identify a ClickHouse Cloud service in the warehouse configured as read-only.
2. In the ClickHouse Cloud console, select the read-only service.
3. Launch ClickStack from the left navigation menu.

Once launched, ClickStack UI will automatically bind to this read-only service.

### Adding more data sources[​](#adding-data-sources "Direct link to Adding more data sources")

ClickStack is OpenTelemetry native but not OpenTelemetry exclusive - you can use your own table schemas if desired.

The following describes how users can add additional data sources beyond those that are configured automatically.

#### Using OpenTelemetry schemas[​](#using-otel-schemas "Direct link to Using OpenTelemetry schemas")

If you're using an OTel collector to create the database and tables within ClickHouse, retain all default values within the create source model, completing the `Table` field with the value `otel_logs` - to create a logs source. All other settings should be auto-detected, allowing you to click `Save New Source`.

To create sources for traces and OTel metrics, you can select `Create New Source` from the top menu.

From here, select the required source type followed by the appropriate table e.g. for traces, select the table `otel_traces`. All settings should be auto-detected.

Correlating sources

Note that different data sources in ClickStack—such as logs and traces—can be correlated with each other. To enable this, additional configuration is required on each source. For example, in the logs source, you can specify a corresponding trace source, and vice versa in the traces source. See ["Correlated sources"](/docs/use-cases/observability/clickstack/config#correlated-sources) for further details.

#### Using custom schemas[​](#using-custom-schemas "Direct link to Using custom schemas")

Users looking to connect ClickStack to an existing service with data can complete the database and table settings as required. Settings will be auto-detected if tables conform to the OpenTelemetry schemas for ClickHouse.

If using your own schema, we recommend creating a Logs source ensuring the required fields are specified - see ["Log source settings"](/docs/use-cases/observability/clickstack/config#logs) for further details.

## JSON type support[​](#json-type-support "Direct link to JSON type support")

Beta feature. [Learn more.](/docs/beta-and-experimental-features#beta-features)

Beta Feature - not production ready

JSON type support in **ClickStack** is a **beta feature**. While the JSON type itself is production-ready in ClickHouse 25.3+, its integration within ClickStack is still under active development and may have limitations, change in the future, or contain bugs.

ClickStack has beta support for the [JSON type](/docs/interfaces/formats/JSON) from version `2.0.4`.

For the benefits of this type see [Benefits of the JSON type](/docs/use-cases/observability/clickstack/ingesting-data/otel-collector#benefits-json-type).

In order to enable support for the JSON type you must set the following environment variables:

- `OTEL_AGENT_FEATURE_GATE_ARG='--feature-gates=clickhouse.json'` - enables support in the OTel collector, ensuring schemas are created using the JSON type.
- `BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true` (ClickStack Open Source only) - enables support in the ClickStack UI application, allowing JSON data to be queried.

Additionally, you should contact [[email protected]](/cdn-cgi/l/email-protection#3f4c4a4f4f504d4b7f5c53565c5457504a4c5a115c5052) to ensure JSON is enabled on your ClickHouse Cloud service.

- [Setup steps](#setup-steps)- [Additional tasks](#additional-tasks)- [JSON type support](#json-type-support)

Was this page helpful?