QPR ProcessAnalyzer Native App in Snowflake

QPR ProcessAnalyzer can run as Snowflake Native App which allows process mining analyses for data in Snowflake Data Cloud. First, QPR ProcessAnalyzer application needs to be installed by following these Snowflake instructions: https://other-docs.snowflake.com/en/native-apps/consumer-installing-container#install-an-application-from-a-snowflake-marketplace-listing.

Get started

QPR ProcessAnalyzer Native App requires eventlog data extracted from source systems. Data in Snowflake need to be converted into the suitable eventlog format.

To get started, you can also import example eventlogs as follows:

1. Create project in the Workspace.
2. Go to the project and import model from sample eventlog files.
3. Double-click the model to start Process Discovery or create dashboard.

User access to application

You can give access to the QPR ProcessAnalyzer Native App by clicking the Manage access button in the app page and add roles to the app users. The app users can use the QPR ProcessAnalyzer Native App and access Snowflake data through the application.

QPR ProcessAnalyzer has a separate User Management which is integrated into Snowflake user management. When QPR ProcessAnalyzer is installed, the Snowflake user who installed the application, is automatically created to QPR ProcessAnalyzer user management as system administrator. This user needs to open QPR ProcessAnalyzer, go to the User Management, and create other users. If you see the QPR ProcessAnalyzer login page when trying to access the QPR ProcessAnalyzer Native App, there is no user available in the QPR ProcessAnalyzer user management corresponding to your Snowflake user name.

QPR ProcessAnalyzer user management can be used to control access for different users.

Application access to data

QPR ProcessAnalyzer Native App needs an access to data in Snowflake tables, limited by permissions given to the QPR ProcessAnalyzer Native App. For example, following SQL commands grant permission to read a specific table in Snowflake:

GRANT USAGE ON DATABASE <database> TO APPLICATION QPR_PROCESSANALYZER;
GRANT USAGE ON SCHEMA <database>.<schema> TO APPLICATION QPR_PROCESSANALYZER;
GRANT SELECT ON TABLE <database>.<schema>.<table> TO APPLICATION QPR_PROCESSANALYZER;

Following example grants access to all tables in a specific schema:

GRANT SELECT ON ALL TABLES IN SCHEMA <database>.<schema> TO APPLICATION QPR_PROCESSANALYZER;

Manage warehouse

QPR ProcessAnalyzer Native App includes an XS-size virtual warehouse by default named QPR_PROCESSANALYZER_WAREHOUSE. Its size and other settings can be changed in Snowsight (Admin -> Warehouses), like for any other warehouse.

It's also possible use another warehouse, by changing it using the following command:

ALTER SERVICE <service_name> SET QUERY_WAREHOUSE = <warehouse_name>;

Notes

QPR ProcessAnalyzer (running in the Snowpark Container Services) automatically starts up when a user logs in. QPR ProcessAnalyzer container doesn't stop automatically, but it can be stopped manually if desired (ALTER SERVICE <name> SUSPEND). When the QPR ProcessAnalyzer container is not running, the compute pool will stop automatically after an hour. Also the compute pool will startup automatically when QPR ProcessAnalyzer container needs to run.

Snowflake has a one minute timeout for http requests, so long running operations may reach this timeout and fail. For example, importing large model from pacm or json file may encounter this situation. However, CSV data import doesn't have this issue.

Queries done by QPR ProcessAnalyzer appear in the Snowsight Query History as user QPRPA_SERVER. The SQL text is not shown in the Query History for queries originating from the native app.

QPR ProcessAnalyzer requires following account level privileges: BIND SERVER ENDPOINT, CREATE COMPUTE POOL, CREATE WAREHOUSE. These privileges are need to be granted during the application installation.

Uninstall

QPR ProcessAnalyzer Native App can be uninstalled like any other app. Note that if QPR ProcessAnalyzer is uninstalled, the configuration data, such as projects, models, dashboards and scripts, are lost. However, the eventlog data residing in Snowflake tables are preserved.