MicroStrategy ONE

Modify the Amount of Data Returned In-Memory for the Platform Analytics Cube

Platform Analytics currently stores telemetry for all time in the Platform Analytics Repository. As the repository grows in size, you may want to limit the amount of data that is stored in-memory when publishing the Platform Analytics super cube.

To reduce the data volume stored in-memory on the MicroStrategy Intelligence Server, warehouse views are created on top of large fact and look up tables. By default, the Platform Analytics views are configured to limit the data to a rolling 14 days. However, the number of days in each view can be modified by simply changing a value in the Platform Analytics configuration file and restarting the Platform Analytics consumer.

Increasing the number of days means the size of the cache stored in-memory on the Intelligence Server increases.

Many of the out-of-the-box dashboards utilize the Platform Analytics Cube as the dataset for analysis. Changing the number of days will be reflected in the analysis of the dependent dashboards.

To see all dashboards and reports that are dependents of the Platform Analytics Cube, right-click a cube and select Find Dependents.

Tables

To limit the amount of data returned in-memory after republishing the Platform Analytics Cube, warehouse views have been created on top of large lookup tables and on all fact tables. These tables are used in the local schema cube definition but do not apply to the Platform Analytics project schema. Any application object (report, dashboard, document, OLAP Cube) created based on the project schema returns data for all days in the Platform Analytics Repository.

The following tables have a view applied:

  • fact_prompt_answers_view
  • fact_action_security_filter_view
  • fact_sql_stats_view
  • fact_step_sequence_view
  • fact_performance_monitor_view
  • fact_action_cube_cache_view
  • fact_access_transactions_view
  • lu_session_view
  • lu_history_list_message_view

Steps to Modify the View Date Range

  1. Open Windows Services, right-click MicroStrategy Platform Analytics Consumer and select Stop.
  2. In the Platform Analytics directory, located at C:\Program Files (x86)\MicroStrategy\Platform Analytics, open the conf folder.
  3. Open the PAConsumerConfig.yaml file and update the viewCutoffRangeInDays field to the desired number of days.

    The value should be a natural positive number.

    For example:

    viewCutoffRangeInDays: 14

  4. Save the file.
  5. Open Windows Services, right-click MicroStrategy Platform Analytics Consumer and select Start.
  6. To verify the change, run the query below in the Platform Analytics Repository:
    Copy
    SELECT cutoff_range_in_days FROM platform_analytics_wh.etl_lu_view_cutoffs ORDER BY cutoff_id desc limit 1;
  1. In the Platform Analytics directory, located at /opt/MicroStrategy/PlatformAnalytics, open the bin folder and run the following command:
    Copy
    ./platform-analytics-consumer.sh stop
  2. Still in the Platform Analytics directory, open the conf folder.
  3. Open the PAConsumerConfig.yaml file and update the viewCutoffRangeInDays field to the desired number of days.

    The value should be a natural positive number.

    For example:

    viewCutoffRangeInDays: 14

  4. Save the file.
  5. In the Platform Analytics directory, open the bin folder and run the following command:

    Copy
    ./platform-analytics-consumer.sh start
  6. To verify the change, run the query below in the Platform Analytics Repository:
    Copy
    SELECT cutoff_range_in_days FROM platform_analytics_wh.etl_lu_view_cutoffs ORDER BY cutoff_id desc limit 1;