Application Settings

  • Updated

You can make modifications to application settings in the Settings section on the left panel.

App settings

Application Settings​

To make changes to application settings,

  1. Navigate to Settings and then to Application.
  2. The first step is to set Defaults that get applied to various behavioral analytics templates. For example, User Datasets  is used as the default "Actor" dataset in a funnel and Event Stream - is used for events inside of the funnel and retention charts.
  3. Followed by this, you can configure the timezone for your application using the drop-down.
  4. The Schema section contains application-level settings related to data warehouse and query schema. Here, you can configure shorter join paths and allow Analytics to guess the intended join path based on the number of edges. Enable the Schema setting with care as it can generate unexpected SQL queries.
  5. The next section is Sampling. Here, you can configure chart settings like faster response and higher precision using the slider.
  6. The next step is to configure Materialization. When materialization is enabled, Analytics creates materialized tables within the data warehouse which contain intermediate results for improving performance. The following are fields under Materialization:
    • Database - the name of the database in the data warehouse where the materialized tables will be created.
    • Schema - the name of the schema within the database where the materialized tables will be created.
    • Refresh Cron Schedule - the refresh periodicity of the materialized tables using the Cron syntax.

For BigQuery, the Database and Schema fields to specify in materialization correspond to the BigQuery project name and the BigQuery dataset name respectively.

  1. Then, configure Rules for your application. These rules describe the criteria that must be met to trigger alerts. Enable the toggle under Rules. Then, set the Refresh Cron Schedule. Rules are executed periodically based on the provided cron expression.

Rules in Analytics is a feature that is not available by default. If you would like to enable the optional rules feature in Analytics, please contact support@netspring.io.

  1. The next configuration is Audience. An audience is a cohort that is published to the warehouse. You can enable this feature for your app using the toggle. The following are fields under Audience:

    1. Database - the name of the database in the data warehouse.
    2. Schema - the name of the schema within the database.

To do a periodic refresh of the Audience, enable the Enabled Periodic Refresh toggle.

  1. Under the Feature Flags section, you can enable/disable the following features using the corresponding toggles:

    • Using updated exploration templates
    • Enabling drafts
    • Enabling the Universal Exploration template
    • Casting all timestamps
app-new-settings-887d1098b22ba61dceb7ad49a966ac9e.gif
 

What are cron jobs?

Cron jobs are processes scheduled at recurring intervals and are specified using a format based on Spring Cron Expression. Using cron jobs, you can schedule your job so that it runs at specified times or at specific dates.

Cron job format
Cron jobs are defined using the Spring Cron Expression format (* * * * * * ). This is a set of six fields in a line, each field indicating when the job should be executed. Here are what each of the fields in the string denote:

FIELD DESCRIPTION VALUES
Field 1 Second 0-59
Field 2 Minute 0-59
Field 3 Hour 0-23
Field 4 Day of the month 1-31
Field 5 Month 1-12 or JAN-DEC
Field 6 Day of the week 0-7, here 0 or 7 will be Monday or MON-SUN