By default, analytics.sh does not generate a log file. With this in mind, it can be difficult to determine if analytics is running/when it completed/etc... without logging in to the YARN Resource Manager UI.
To address this, you can redirect the output from analytics.sh to a log file by using a command similar to the following:
bin/analytics.sh conf/interset.conf > /tmp/analytics-`date +%Y-%m-%d`.log 2>&1
This will generate a file in /tmp/ called analaytics.log which will provide you with both real time and historical information on the analytics execution each day.
Note that the actual location specified is entirely configurable as long as the spark user has write access to the location.
Note that in Interset 5.2 and newer, the "analytics.log" is created by default however it does not contain a timestamp. The same format above can be used to modify the cron (crontab -e) entry managing the analytics executions.