Deploy QPR ProcessAnalyzer from Container - Revision history

Ollvihe: /* Application settings */

2025-12-15T09:44:16Z

Application settings

← Older revision		Revision as of 09:44, 15 December 2025
Line 20:		Line 20:
	When using environment variables, the variable names for the hierarchical keys in the appsettings.json file are defined using the double underscore as separator, e.g., the ''LogFilePath'' setting in the ''Application'' section is defined as ''Application__LogFilePath'' (see a full example below in the examples section).		When using environment variables, the variable names for the hierarchical keys in the appsettings.json file are defined using the double underscore as separator, e.g., the ''LogFilePath'' setting in the ''Application'' section is defined as ''Application__LogFilePath'' (see a full example below in the examples section).

	It's also possible to override settings in the PA_CONFIGURATION table using the environment variables. ~~Setting names~~ in the [[PA_Configuration_database_table\|PA_CONFIGURATION table]] ~~are converted into environment variable name using~~ the snake case (underscores between words) ~~in uppercase~~ prefixed with '''QPRPA_'''~~, e.g~~., the ''SqlServerConnectionString'' setting is defined as ''QPRPA_SQL_SERVER_CONNECTION_STRING''.		It's also possible to override settings in the PA_CONFIGURATION table using the environment variables. The environment variable name to use is the setting name in the [[PA_Configuration_database_table\|PA_CONFIGURATION table]] in the snake-case (underscores between words) and upper-case prefixed with '''QPRPA_'''. For example, the ''SqlServerConnectionString'' setting is defined as ''QPRPA_SQL_SERVER_CONNECTION_STRING''.

	===Database for configuration data ===		===Database for configuration data ===

Ollvihe: /* Log writing */

2025-11-25T09:32:20Z

Log writing

← Older revision		Revision as of 09:32, 25 November 2025
Line 39:		Line 39:
	===Log writing===		===Log writing===
	QPR ProcessAnalyzer Server writes log which can be stored to following targets:		QPR ProcessAnalyzer Server writes log which can be stored to following targets:
	* Store the log to a file in the container volume. The file can be mapped to any external storage system (see examples below).		* Store the log to a file in the container volume. The file can be mapped to any external storage system (see examples below). To enable this option, a value for the ''LogFilePath'' setting must be set.
	* Write to stdout and stderr streams that can be listened to store the logs.		* Write to stdout and stderr streams that can be listened to store the logs. This option is enabled by default. To disable it, the ''ConsoleAppender'' must be removed from log4net.config file.
	* Push logs to an OpenTelemetry endpoint.		* Push logs to an OpenTelemetry endpoint. This option is disabled by default. To enable it, the ''oltp'' endpoint must be set.

	===Key storage for session cookies encryption===		===Key storage for session cookies encryption===

Ollvihe: /* Log writing */

2025-11-24T10:29:29Z

Log writing

← Older revision		Revision as of 10:29, 24 November 2025
Line 39:		Line 39:
	===Log writing===		===Log writing===
	QPR ProcessAnalyzer Server writes log which can be stored to following targets:		QPR ProcessAnalyzer Server writes log which can be stored to following targets:
	* Store the log to a file in the container volume. The file can be mapped to any external storage system.		* Store the log to a file in the container volume. The file can be mapped to any external storage system (see examples below).
	* Write to stdout and stderr streams that can be listened to store the logs.		* Write to stdout and stderr streams that can be listened to store the logs.
	* Push logs to an OpenTelemetry endpoint.		* Push logs to an OpenTelemetry endpoint.

Ollvihe: /* Log writing */

2025-11-24T10:29:01Z

Log writing

← Older revision		Revision as of 10:29, 24 November 2025
Line 39:		Line 39:
	===Log writing===		===Log writing===
	QPR ProcessAnalyzer Server writes log which can be stored to following targets:		QPR ProcessAnalyzer Server writes log which can be stored to following targets:
	* Store to a file in the container volume. The file can be mapped to any external storage system.		* Store the log to a file in the container volume. The file can be mapped to any external storage system.
	* Write to stdout and stderr streams that can be listened to store the logs.		* Write to stdout and stderr streams that can be listened to store the logs.
	* Push logs to an OpenTelemetry endpoint.		* Push logs to an OpenTelemetry endpoint.

Ollvihe: /* Log writing */

2025-11-24T10:28:38Z

Log writing

← Older revision		Revision as of 10:28, 24 November 2025
Line 39:		Line 39:
	===Log writing===		===Log writing===
	QPR ProcessAnalyzer Server writes log which can be stored to following targets:		QPR ProcessAnalyzer Server writes log which can be stored to following targets:
	* Store to a file in the container ~~disk~~. The file can be mapped to any external storage system.		* Store to a file in the container volume. The file can be mapped to any external storage system.
	* Write to stdout and stderr streams that can be listened to store the logs.		* Write to stdout and stderr streams that can be listened to store the logs.
	* Push logs to an OpenTelemetry endpoint.		* Push logs to an OpenTelemetry endpoint.

Ollvihe: /* HTTPS connection to UI */

2025-11-24T10:28:06Z

HTTPS connection to UI

← Older revision		Revision as of 10:28, 24 November 2025
Line 50:		Line 50:

	===HTTPS connection to UI===		===HTTPS connection to UI===
	HTTPS connections ~~may~~ be terminated e.g., in a load-balancer, ~~but~~ the container image ~~also~~ supports passing ~~the~~ HTTPS traffic ~~all the way~~ to the container. ~~Certificate~~ and key files need to be provided to the container via volume.		HTTPS connections can be terminated before the container (e.g., in a load-balancer). Alternatively, the container image supports passing HTTPS traffic to the container. Then, the certificate and key files need to be provided to the container via volume.

	Following environment variables must be set to configure HTTPS:		Following environment variables must be set to configure HTTPS:

Ollvihe: /* Database for configuration data */

2025-11-24T10:25:46Z

Database for configuration data

← Older revision		Revision as of 10:25, 24 November 2025
Line 31:		Line 31:
	Notes:		Notes:
	* Container image supports only the SQL Server authentication mode.		* Container image supports only the SQL Server authentication mode.
	* To automatically update an existing database user must have the '''~~db-owner~~''' permissions to the database.		* To automatically update an existing database user must have the '''db_owner''' permissions to the database.
	* To automatically create the configuration database, the user must have the '''dbcreator''' server role.		* To automatically create the configuration database, the user must have the '''dbcreator''' server role.

Ollvihe: /* Running in Docker */

2025-11-24T09:41:58Z

Running in Docker

← Older revision		Revision as of 09:41, 24 November 2025
Line 74:		Line 74:
	-e QPRPA_DEFAULT_DATA_SOURCE=SqlServer \		-e QPRPA_DEFAULT_DATA_SOURCE=SqlServer \
	-e QPRPA_SQL_SERVER_CONNECTION_STRING="Server=dbserver.host;DataBase=QPR_PA_DATA;Uid=user;PWD=password" \		-e QPRPA_SQL_SERVER_CONNECTION_STRING="Server=dbserver.host;DataBase=QPR_PA_DATA;Uid=user;PWD=password" \
	-e Application__LogFilePath=/tmp/logs/pa-server.log \		-e Application__LogFilePath=/tmp/logs/pa/pa-server.log \
	-v /pa-logs:/~~var~~/logs/pa \		-v /pa-logs:/tmp/logs/pa \
	azure-repo/pa/server		azure-repo/pa/server
	</pre>		</pre>
Line 83:		Line 83:
	docker run -d -p 5000:5000 --restart unless-stopped \		docker run -d -p 5000:5000 --restart unless-stopped \
	-v /pa/config/appsettings.json:/pa/appsettings.json \		-v /pa/config/appsettings.json:/pa/appsettings.json \
	-v /pa/logs:/~~var~~/logs/pa \		-v /pa/logs:/tmp/logs/pa \
	azure-repo/pa/server		azure-repo/pa/server
	</pre>		</pre>

Ollvihe: /* Running in Docker */

2025-11-24T09:37:43Z

Running in Docker

@@ Line 84: / Line 84: @@
    -v /pa/config/appsettings.json:/pa/appsettings.json \
    -v /pa/logs:/var/logs/pa \
    azure-repo/pa/server
 </pre>

Ollvihe: /* Snowflake private key */

2025-11-24T09:35:34Z

Snowflake private key

← Older revision		Revision as of 09:35, 24 November 2025
Line 34:		Line 34:
	* To automatically create the configuration database, the user must have the '''dbcreator''' server role.		* To automatically create the configuration database, the user must have the '''dbcreator''' server role.

	=== Snowflake private key ===		=== Snowflake user private key ===
	For QPR ProcessAnalyzer to authenticate to Snowflake using the key-pair authentication (https://docs.snowflake.com/en/user-guide/key-pair-auth), the private key file needs to be mapped to the container volume. The mapping can be done for example using a Kubernetes secret. The ~~path~~ of the private key file needs to be speficied in the ''PRIV_KEY_FILE'' parameter in the [[Snowflake_Connection_Configuration#Set_Snowflake_ODBC_connection\|Snowflake connection string]].		For QPR ProcessAnalyzer to authenticate to Snowflake using the key-pair authentication (https://docs.snowflake.com/en/user-guide/key-pair-auth), the private key file needs to be mapped to the container volume. The mapping can be done for example using a Kubernetes secret. The location of the private key file needs to be speficied in the ''PRIV_KEY_FILE'' parameter in the [[Snowflake_Connection_Configuration#Set_Snowflake_ODBC_connection\|Snowflake connection string]].

	===Log writing===		===Log writing===