Configuration - Analytics Data Processing v2.6.0
(Last updated: 2026-10-12, Created: 2026-09-29)
Analytics Data Processing is configured with environment variables, set in .env.data_processing with Docker, or in .env with the Windows installation (see Installation).
Legend: Required must be set. Recommended has a default, but most installations should set it.
Databases
Analytics Data Processing reads from the EWA database (source) and writes to the Analytics database (target).
The same settings exist for both, with the prefix SOURCE__DATABASE__ for the EWA database and TARGET__DATABASE__ for the Analytics database.
| Setting (after the prefix) | Required | Default | Description |
|---|---|---|---|
TYPE | Required | (none) | Database type. Use mssql. |
HOST | Required | (none) | Host name or IP address of the database server. |
PORT | Required | (none) | Port of the database server, usually 1433. |
NAME | Required | (none) | Name of the database. |
USERNAME | Required | (none) | Database user. The source user only needs read access. The target user must be able to create and change tables. |
PASSWORD | Required | (none) | Password for the user. |
ENCRYPT | yes | Encrypt the connection: yes or no. Keep yes. | |
TRUST_SERVER_CERTIFICATE | yes | Accept the server certificate without validating it: yes or no. Set to no if the database server has a certificate your server trusts. | |
ALLOW_SNAPSHOT_ISOLATION | false | Source only. Set to true to read from the EWA database without blocking it. The EWA database must have snapshot isolation turned on. |
Schedule
| Setting | Required | Default | Description |
|---|---|---|---|
BLIKSUND_RUN_SCHEDULED | true | true: runs twice at start, then on a schedule, see First run. false: runs once and stops. With Docker, restart: unless-stopped then starts it again right away, so keep true. | |
BLIKSUND_RUN_SCHEDULED_FREQUENCY_MIN | 60 | Minutes between runs. A new run never starts before the previous one has finished. | |
BLIKSUND_RUN_TAG | false | A short text, for example test, added in front of every schema name: test_raw, test_ewa_clean and test_ewa_core. Use it to build a separate copy of the data in the same Analytics database, without overwriting the existing data. Analytics API always reads the schemas without a tag. false uses no tag. |
Load
| Setting | Required | Default | Description |
|---|---|---|---|
BLIKSUND_LOAD_BATCH_SIZE | Recommended | 10000 | Rows read from the EWA database in each batch. We recommend 50000. Lower it if the EWA database is under heavy load. |
BLIKSUND_LOAD_BATCH_WAIT_TIME | 1 | Seconds to wait between batches, to spread the load on the EWA database. | |
BLIKSUND_LOAD_FULL_ON_START | false | true loads all data again from the EWA database when the service starts. Only use it when the release notes or Bliksund ask for it. | |
BLIKSUND_LOAD_FULL_ON_SCHEDULE | false | true loads all data again on every scheduled run. Not recommended. | |
BLIKSUND_LOAD_REPAIR_JSON | false | true repairs unescaped quotes in JSON text from the EWA database before it is loaded. Only use it if Bliksund asks for it. |
Transform
| Setting | Required | Default | Description |
|---|---|---|---|
BLIKSUND_TRANSFORM_FULL_ON_START | false | true rebuilds all Clean and Core tables in the first run after the service starts. Use it for the first run after an upgrade, and set it back to false when the service has started, see Upgrading. | |
BLIKSUND_TRANSFORM_FULL_ON_SCHEDULE | false | true rebuilds all Clean and Core tables on every scheduled run. Not recommended. |
Logging
Logs are written to the console (see them with docker compose logs) and to files in /app/logs in the container. With the Docker installation, that folder is logs next to the compose file. The Windows installation uses the same settings, with a different default folder, see Windows Installation.
| Setting | Required | Default | Description |
|---|---|---|---|
LOG__LEVEL | INFO | DEBUG, INFO, WARNING, ERROR or CRITICAL. | |
LOG__CONSOLE__ENABLED | true | Write logs to the console. | |
LOG__CONSOLE__FORMAT | plain | plain or json. Use json if you collect logs with a log system. | |
LOG__FILE__ENABLED | true | Write logs to files in LOG__PATH. | |
LOG__PATH | /app/logs | Folder for log files in the container. On Windows, see Logging. | |
LOG__FILE__FILENAME | service.log | Name of the log file. | |
LOG__FILE__MAX_SIZE | 10485760 | Maximum size of a log file in bytes (10 MB) before a new file is started. | |
LOG__FILE__MAX_FILES | 15 | Number of log files kept. | |
OTEL_METRICS_EXPORTER | otlp | none turns off metrics export. Set it to none unless you collect metrics with an OpenTelemetry collector, otherwise the logs repeat OTLP telemetry endpoint unreachable. |