QPR ProcessAnalyzer Native App in Snowflake: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
Line 9: Line 9:


== Manage permissions ==
== Manage permissions ==
QPR ProcessAnalyzer has an own [[Manage_Users_and_Groups|User Management]] which is integrated into Snowflake user management. When a Snowflake user login to QPR ProcessAnalyzer, the user is automatically created to QPR ProcessAnalyzer. New users get by default administrator permissions to QPR ProcessAnalyzer. If you need to restrict user permissions, create the users beforehand to the QPR ProcessAnalyzer and set the permissions as desired.
QPR ProcessAnalyzer has a separate [[Manage_Users_and_Groups|User Management]] which is integrated into Snowflake user management. When a Snowflake user login to QPR ProcessAnalyzer Native App, the user is automatically created to QPR ProcessAnalyzer. New users get by default administrator permissions to QPR ProcessAnalyzer. If you need to restrict user permissions, create the users beforehand to QPR ProcessAnalyzer and set their permissions as desired.


To use the QPR ProcessAnalyzer Native App, Snowflake users need to be given USAGE privilege to the QPR ProcessAnalyzer service. More information: https://docs.snowflake.com/en/developer-guide/snowpark-container-services/working-with-services#granting-the-usage-privilege-on-all-endpoints-using-the-default-service-role
To use the QPR ProcessAnalyzer Native App, Snowflake users need to be given the USAGE privilege to the QPR ProcessAnalyzer service. More information: https://docs.snowflake.com/en/developer-guide/snowpark-container-services/working-with-services#granting-the-usage-privilege-on-all-endpoints-using-the-default-service-role


QPR ProcessAnalyzer Native App need to have access to data in Snowflake that is limited by permissions given to the owner role of the service. Assign permissions to that role for all databases containing eventlog data.
QPR ProcessAnalyzer Native App need to have access to data in Snowflake and it's limited by the permissions given to the owner role of the QPR ProcessAnalyzer service. Give permissions to that role for databases containing eventlog data that will be analyzed in the QPR ProcessAnalyzer Native App. At least following privileges are needed:
* Database: USAGE
* Schema : USAGE
* Table/view: SELECT


== Use virtual warehouses ==
== Use virtual warehouses ==

Revision as of 09:24, 3 October 2024

Get started

Load data

QPR ProcessAnalyzer Native App is initially empty. You can use existing eventlog data in Snowflake or import example eventlogs as follows:

  1. Create project.
  2. Import model. (Sample eventlogs)
  3. Create dashboard.

Manage permissions

QPR ProcessAnalyzer has a separate User Management which is integrated into Snowflake user management. When a Snowflake user login to QPR ProcessAnalyzer Native App, the user is automatically created to QPR ProcessAnalyzer. New users get by default administrator permissions to QPR ProcessAnalyzer. If you need to restrict user permissions, create the users beforehand to QPR ProcessAnalyzer and set their permissions as desired.

To use the QPR ProcessAnalyzer Native App, Snowflake users need to be given the USAGE privilege to the QPR ProcessAnalyzer service. More information: https://docs.snowflake.com/en/developer-guide/snowpark-container-services/working-with-services#granting-the-usage-privilege-on-all-endpoints-using-the-default-service-role

QPR ProcessAnalyzer Native App need to have access to data in Snowflake and it's limited by the permissions given to the owner role of the QPR ProcessAnalyzer service. Give permissions to that role for databases containing eventlog data that will be analyzed in the QPR ProcessAnalyzer Native App. At least following privileges are needed:

  • Database: USAGE
  • Schema : USAGE
  • Table/view: SELECT

Use virtual warehouses

When QPR ProcessAnalyzer Native App installed, XS-size virtual warehouse is created and it's used by default. Different warehouse can be used by changing it with the following command:

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