New pages
Jump to navigation
Jump to search
- 15:41, 22 November 2025 Server settings in log4net.config (hist | edit) [3,756 bytes] Ollvihe (talk | contribs) (Created page with "QPR ProcessAnalyzer uses the log4net component (https://logging.apache.org/log4net/) for logging, allowing to flexibly define what is logged and where the logs are stored. For example, the following settings can be set in the '''log4net.config''' file (located in the '''bin''' folder in the server application files): * log4net > appender > '''maximumFileSize''': Maximum size of the log file. When the maximum size is reached, the log writing continues in a new file, and t...")
- 15:18, 22 November 2025 Server settings in appsettings.json (hist | edit) [5,563 bytes] Ollvihe (talk | contribs) (Created page with "The appsettings.json file is the main settings file for the QPR ProcessAnalyzer Server application. Go through the settings in the table below to set suitable values to the appsettings.json. <div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;"> The appsettings.json needs to be a correctly formatted json file, and thus the backslashes and quotation marks in string values need to be escaped as follows: \ →...")
- 00:50, 22 November 2025 Deploy QPR ProcessAnalyzer from Container (hist | edit) [9,084 bytes] Ollvihe (talk | contribs) (Created page with " == Container Image == 1. For deploying in containerized platforms ProcessAnalyzer distributed as container image. 1. Image contains ProcessAnalyzer server build for linux-x64 platform. 1. Following additional components are included: 1. ODBC 18 drivers 1. Snowflake drivers 1. SAP libraries are not included. 1. Container does not require superuser permissions and runs under user account `pa`. 1. To run container image con...") originally created as "Deploy QPR ProcessAnalyzer Server using Container"
- 12:33, 11 November 2025 AI Root Causes (hist | edit) [7,569 bytes] TeeHiet (talk | contribs) (TK-61818)
- 12:34, 4 November 2025 Range Filter (hist | edit) [3,434 bytes] TeeHiet (talk | contribs) (TK-61734)
- 21:03, 28 September 2025 Change Native App Compute Pool Size (hist | edit) [2,155 bytes] Ollvihe (talk | contribs) (Created page with "By default, QPR ProcessAnalyzer Native App uses the CPU_X64_S size compute pool. The compute pool size can be changed (for example to CPU_X64_XS) using the following instructions. The instructions use procedure '''public.set_compute_pool''' which is part of the Native App and it recreates application service in a specified compute pool. Application role ADMINISTRATOR is required to run the procedure. The procedure will drop and recreate the application service. Data in...") originally created as "Change Native App Compute Pool"
- 22:57, 24 September 2025 Decide Case ID Data Type (hist | edit) [2,733 bytes] Ollvihe (talk | contribs) (Created page with "QPR ProcessAnalyzer supports both textual (string) and whole number (integer) as the case ID data type. This article discusses which data type should be used for the case ID. This discussion applies both for Snowflake and in-memory calculation.")
- 22:26, 17 September 2025 Embed to Website (hist | edit) [3,783 bytes] Ollvihe (talk | contribs) (Created page with "QPR ProcessAnalyzer can be embedded to another website, such as Microsoft Sharepoint. The embedding is based on the ''iframe'' html element. By default, QPR ProcessAnalyzer only allowes to be embedded by a website in the same origin that is restricted by the Content-Security-Policy HTTL header. More information how to change the CSP setting in Security Hardening. == Change CSP frame-ancestors setting == By...") originally created as "Website Embedding"