You set up the feature by configuring a connection to the database you'll be using to store the collected data, specifying whether to purge old data, and selecting activity you want to store data for. Note that only Oracle and PostgreSQL are supported as DBMSes for analytics data.
CREATE LANGUAGE plpgsql
Reporting > Settings > Analytics
| Setting | Description |
|---|---|
| Database Driver Presets | Select your DBMS (Oracle or PostgreSQL) to automatically populate a JDBC driver class name and database URL template. Be sure to edit the database URL so that you have a valid connection the database. |
| JDBC Driver Class | This fully-qualified name of the database driver class is entered for you when you select a database driver preset. |
| Database URL | The URL for connecting to the database is entered for you when you select a preset. |
| Username | A username that's valid for connecting to the database. |
| Password | A password that goes with the username. |
| Min Connections | The minimum number of connections that the application can make to the database. |
| Maximum Connections | The maximum number of connections that the application can make. |
| Connection Timeout | The amount of time after which an unused connection will be dropped. |
With the analytics feature enabled, the application will automatically extract and transform data from the application database into the analytics database each morning at 2 a.m., system time (you can't currently set the extraction time). At other times, you can begin extraction on this page.
To control database size, you can have data purged from the analytics database when it has passed a certain age.
| Setting | Description |
|---|---|
| Purge Old Activity | Click Enabled to have data purged according to the age limit you set. |
| Older than (months) | Select the highest number of months that each piece of activity data should be stored before it's purged. |
| Run ETL Now | Click Run to begin copying data to the analytics database. |