Commonly Asked Questions and Troubleshooting Platform Analytics Daily ETL

Background

The Platform Analytics Daily ETL is a process triggered by the Telemetry Store to update/populate specific areas of data that only require updating once per day. The daily ETL process can be configured to execute at any user-defined time using the PAConsumerConfig.yaml configuration file. For steps on how to configure the Daily ETL, see the Configure the Platform Analytics Daily ETL page of the Platform Analytics guide.
The following are frequently asked questions and possible troubleshooting techniques:

How can I determine how long the Platform Analytics daily_etl or hourly_etl procedure took to execute?

The platform-analytics-consumer.log file indicates how long the corresponding periodic ETL took to execute. The ETLs often include more than just executing a stored procedure on the Platform Analytics Repository. Therefore, you can assume that the time spent executing the stored procedures is always less than what is logged in the log files.
For example:

2018-10-02 17:13:28,334 INFO ScheduledETLProcess:192 main - The Init ETL finished in 9823 milliseconds.

...

...

...

2018-10-02 17:13:28,370 INFO ScheduledETLProcess:131 pool-3-thread-2 - The Hourly ETL finished in 4600 milliseconds.

Can I turn-off specific procedures, i.e., the hourly or daily ETL procedures?

No, it is not supported to delete any of the procedures provided during the Platform Analytics installation or upgrade. The procedures are needed for maintaining a healthy Platform Analytics Repository and overall data integrity for the project.
The Telemetry Store is the main process responsible for triggering the procedures on the defined schedule. If a procedure is deleted, then errors and exceptions may occur when the Telemetry Store starts or when it calls the procedure per the corresponding periodic schedule. 
For example, you may see the following error message when the Telemetry Store fails to call the daily_etl procedure at startup:

2018-10-02 17:13:28,224 ERROR ScheduledETLProcess:176 main - Error running initialization ETL:

Likewise, you may see the following error message when the Telemetry Store fails to call the hourly_etl procedure:

2018-10-02 17:13:28,370 ERROR ScheduledETLProcess:128 pool-3-thread-2 - Error running hourly ETL:

Finally, it is possible to see an error message when the Telemetry Store fails to call the view_cutoffs_update procedure at startup:

2018-10-02 17:13:28,229 ERROR ScheduledETLProcess:183 main - Error updating view cutoffs: