The Activity Log records all major activity in your user account across all of your applications. Each data set also has its own Activity Log. It logs events in an application, such as creation, deletion, and major changes, as well as sending or receiving applications.
Qrvey is built with multiple AWS services. Here is a list of the main components to give you an idea of what you can expect in your AWS bill. Many have a free tier or upfront pricing depending on your account.
For very large or long-running queries in Postgres, processing may take several minutes to start. To expedite this process, you can enable the "Export Data to S3 to Support Larger Data Loads" option. When selected, the query output is sent to S3, from where Qrvey retrieves the data. This option is available when the Host URL points to an AWS RDS Postgres instance located in the same AWS region as Qrvey.
The steps below detail how to configure Qrvey to access Redshift clusters for the purpose of loading data into Qrvey for data analysis.
The steps below detail the required configuration to access Snowflake clusters for loading data into Qrvey for data analysis.
This document explains the steps you need to take if you want to securely access your AWS RDS instance to load data into the Qrvey Business Analytics platform.
A Connection is a link established between Qrvey and an external data source.
This document will help you customize a Qrvey Instance for different configurations like Composer URL, “From” email address, etc.
Introduction
Deleting a deployment will remove all the metadata and data stored in Qrvey Platform. And the only way to recover the data would be from a backup but the application URLs and API keys will change as you would be restoring the backup in a new instance.
This document outlines the process for deploying a Qrvey Platform instance in AWS GovCloud with FIPS enabled.
In July of 2023, AWS enabled Lambda recursive loop detection to identify and prevent excessive recursive loops in any Lambda functions. The Qrvey platform uses recursive loops for some long-running tasks with appropriate safeguards to prevent excessive invocations. You must disable Lambda recursive loop detection to avoid an interruption of service.
Introduction
The Infrastructure page of the Qrvey Admin Center enables you to view, monitor, and manage the configuration of your Elasticsearch cluster.
This article contains frequently asked questions organized by user persona.
Before Creators can use the OpenID provider to log in, you must set up your OpenID provider account in order to obtain the OAuth 2.0 credentials: clientid, Client Secret, Realm; set a redirect URL (Return URL); and optionally, customize the branding information that creators will see on the user-consent screen.
The Health Dashboard in Qrvey Admin Center provides an easy-to-read status of the health of the Elasticsearch cluster in this instance of the Qrvey platform.
The following steps will walk you through installing the Qrvey platform in your AWS account using a CloudFormation template. Before starting these steps, please confirm your AWS Account ID has been enabled for deployment from Qrvey’s side.
As you prepare to install Qrvey within your current or a new AWS environment, there are a few items to be aware of prior to installation.
Introduction
Qrvey platform supports internationalization and localization for end users in a comprehensive manner. Multi-lingual support is offered for both “static” and “dynamic” text, as well as formatting of numbers and dates based on regions and cultures.
The Qrvey platform is an all-in-one analytics solution that enables SaaS providers to put cutting-edge analytics into the hands of their users. This article contains essential information required to understand how to work with the Qrvey platform.
The Qrvey platform is deployed to an AWS environment. This section of the Qrvey Partner Portal provides CloudOps Engineers with the information they need to manage the deployment. Articles include:
Datasets with joins have their data copied in S3 so that it may be joined using Athena. When there are frequent data syncs, the S3 folder accumulates an excess number of small files. In addition, when data syncs update existing records with matching IDs, the old records remain in S3. Both of these situations degrade join performance and, in extreme cases, may even lead to errors.
<!--
The Qrvey platform uses AWS Elasticsearch service to store all Analytics data and runs queries on this cluster to show Charts and Metrics in UI. This document explains how to monitor and Resize an AWS Elasticsearch cluster based on your needs and requirements.
This video discusses multi-tenancy architecture of the Qrvey platform for SaaS organizations. Includes a demonstration of a parent application that embeds a Qrvey application in a multi-tenant environment. Topics covered include:
Before Creators can use the OpenID provider to log in, you must set up your OpenID provider account in order to obtain the OAuth 2.0 credentials: clientid, Client Secret, Realm; set a redirect URL (Return URL); and optionally, customize the branding information that creators will see on the user-consent screen.
Qrvey will deploy to your AWS account using a CloudFormation template. CloudFormation templates enable you to automate the deployment process of the AWS services required to run the Qrvey system. The following steps will walk you through the deployment process.
Upgrade Note: If you are planning to upgrade to a new version of Qrvey, please read through the Upgrade and release notes on all prior versions, as they may contain platform changes that must be accounted for in the development process. You can follow the steps outlined in Upgrading to a New Version and use the upgrade link for the desired version, provided in the relevant section below. If you have multiple Qrvey instances in the same AWS account AND region or if you deployed the instances in all private subnets (with VPN access) you would have to use the Advanced template to upgrade, please contact the Qrvey support team to get the Advanced upgrade link and necessary instructions for the upgrade.
The Qrvey platform enables end users to display dates and times in their local time zone. The Qrvey platform stores data in UTC/GMT+0 and adjusts the time displayed to the end user based on their preferred settings. The default time zone setting is specified in Qrvey Admin Center, but it can be overridden programmatically. The possible settings are:
Here are some common scenarios where a deployment could result in failure.
To install a new version of Qrvey to update your deployment, follow these steps:
This article applies to all customers upgrading to version 8.4 or later of the Qrvey platform and are using a custom domain URL for Qrvey Composer.