How to see the the reload history of an app?

Modified on Mon, 15 Aug, 2022 at 10:32 AM

The reload history of an app can be found in the 'Reloads Monitor' app found in the 'Monitoring apps' stream as seen in the image below. 




Inside the Dashboard sheet in the Reloads Monitor app you can select the app you wish to look at the reloads for using the filter panel found in the top right.



This will then allow you to see various statistics on the reloads of those apps, including total reloads, reloads per day and the average reload duration. The chart in the top right will show the reloads grouped by task and split by reload result (such as success, fail or reset). The bottom graphs detail the reloads over time, either by hour the reload started or over time (defaulting to months).


The next sheet details the tasks related to the reloading of the app that you have selected.



The top left chart shows a heatmap of the reloads by time of day and day of the week. The bottom left chart shows the tasks associated with the reload of that app and the details of that such as failure rate. The charts on the right side of the sheet show the reload duration and failure rate grouped either by day of the week or by hour of the day.


The following sheet details the reloads that have occurred.



The top chart shows an overall view of the reloads of that have occurred broken down by task while the bottom chart details individual reloads of the selected app.


Two sheets after this (the following sheet does not provide much information that will help with your app reloads) details the log reports of the selected app, these are the logs produced as the reload script runs.



This can be a useful sheet in finding out why reloads may be failing allowing you to resolve these issues.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article