Skip to main content

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)RequiredDefaultDescription
TYPERequired(none)Database type. Use mssql.
HOSTRequired(none)Host name or IP address of the database server.
PORTRequired(none)Port of the database server, usually 1433.
NAMERequired(none)Name of the database.
USERNAMERequired(none)Database user. The source user only needs read access. The target user must be able to create and change tables.
PASSWORDRequired(none)Password for the user.
ENCRYPTyesEncrypt the connection: yes or no. Keep yes.
TRUST_SERVER_CERTIFICATEyesAccept the server certificate without validating it: yes or no. Set to no if the database server has a certificate your server trusts.
ALLOW_SNAPSHOT_ISOLATIONfalseSource only. Set to true to read from the EWA database without blocking it. The EWA database must have snapshot isolation turned on.

Schedule​

SettingRequiredDefaultDescription
BLIKSUND_RUN_SCHEDULEDtruetrue: 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_MIN60Minutes between runs. A new run never starts before the previous one has finished.
BLIKSUND_RUN_TAGfalseA 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​

SettingRequiredDefaultDescription
BLIKSUND_LOAD_BATCH_SIZERecommended10000Rows 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_TIME1Seconds to wait between batches, to spread the load on the EWA database.
BLIKSUND_LOAD_FULL_ON_STARTfalsetrue 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_SCHEDULEfalsetrue loads all data again on every scheduled run. Not recommended.
BLIKSUND_LOAD_REPAIR_JSONfalsetrue repairs unescaped quotes in JSON text from the EWA database before it is loaded. Only use it if Bliksund asks for it.

Transform​

SettingRequiredDefaultDescription
BLIKSUND_TRANSFORM_FULL_ON_STARTfalsetrue 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_SCHEDULEfalsetrue 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.

SettingRequiredDefaultDescription
LOG__LEVELINFODEBUG, INFO, WARNING, ERROR or CRITICAL.
LOG__CONSOLE__ENABLEDtrueWrite logs to the console.
LOG__CONSOLE__FORMATplainplain or json. Use json if you collect logs with a log system.
LOG__FILE__ENABLEDtrueWrite logs to files in LOG__PATH.
LOG__PATH/app/logsFolder for log files in the container. On Windows, see Logging.
LOG__FILE__FILENAMEservice.logName of the log file.
LOG__FILE__MAX_SIZE10485760Maximum size of a log file in bytes (10 MB) before a new file is started.
LOG__FILE__MAX_FILES15Number of log files kept.
OTEL_METRICS_EXPORTERotlpnone turns off metrics export. Set it to none unless you collect metrics with an OpenTelemetry collector, otherwise the logs repeat OTLP telemetry endpoint unreachable.