Skip to main content

Ingestion Mode

Ingestion mode is a light Prisme Analytics mode for handling and ingesting events.

It integrates solely with ClickHouse.


Configuration Options

Configuration of your instance is done by setting PRISME_<option name> environment variable.

Web Server

Prisme has 2 logs, an access logs for processed requests and a general logs for everything else.

All logs are structured JSON that follows bunyan format.

You can pipe logs to bunyan CLI to pretty print them.

Access Log

Path to access log file.

Default: PRISME_ACCESS_LOG=/dev/stdout


Web server listening TCP port.

Default: PRISME_PORT=80

Proxy Options

Prisme Analytics can be positioned behind a reverse proxy, and this section provides information on options related to the proxy setup. It's important to note that a misconfigured server can have security implications. Hence, Prisme Analytics prioritizes security by default with carefully chosen default values.

Trust Proxy

Whether X-Forwarded-For, X-Request-Id and other proxy related headers should be trusted. Sets this value to true only if your instance is running behind a proxy.


Proxy Header

HTTP header used to detemine client IP address when Prisme Analytics is placed behind a trusted proxy.

Default: PRISME_PROXY_HEADER=X-Forwarded-For

ClickHouse Options

Secure connection

Use a TLS connection for ClickHouse.


Host And Port

<host>:<port> string pointing to a ClickHouse instance.

Example: PRISME_CLICKHOUSE_HOSTPORT=clickhouse.localhost:9000
This options is mandatory.


ClickHouse database to use.


Origin Registry Options


Comma separated list (without whitespace) of valid origins. Events coming from an invalid source are rejected.


Event Store Options

Event store is responsible of storing events efficiently in ClickHouse.

ClickHouse recommend keeping number of insertions to 1 per seconds max and inserting rows per batch of tens of thousands.

Maximum Batch Size

Maximum size of an events batch before it is sent to ClickHouse. Leave as default unless you have high traffic load.


Maximum Batch Timeout

Maximum duration before current batch is sent to event store.