Reports are typically batched and generated automatically, according to a schedule. You can configure where generated reports are saved, for how long they remain available, and you can also devote more system resources, if they are available, to expedite report generation.
Changing the Published Report Location
When an Uptime Infrastructure Monitor user generates a report, that report is stored in the
/GUI/reportcache directory; when a scheduled report is automatically generated and published, it is stored in the
/GUI/published directory. Both of these directory paths are found in the Uptime Infrastructure Monitor installation directory on the local Monitoring Station file system:
C:\Program Files\uptime software\uptime
Automatically publishing reports to a publicly accessed directory on the network is an ideal way for non-IT staff to view them. (See Saving Reports to the File System for more information.)
The published report location can be modified with the following
If the intended published report directory is on a system other than the Monitoring Station, the provided location should be a full network path to the system in addition to the directory path on that system.
Changing the Number of Days Reports Are Cached
By default, generated reports are cached on the Monitoring Station for 30 days;
You can change a report’s expiry time limit by manually inputting settings in the Uptime Infrastructure Monitor Configuration panel, as outlined in Modifying Uptime Config Panel Settings.
Change the expiry limit through the following parameter (the default value is shown):
Tuning Resource Usage Report Generation
You can manually change the number of concurrently generated images in the Uptime Infrastructure Monitor Configuration panel with the following parameter:
Adjusting Simultaneously Generated Reports
Uptime Infrastructure Monitor limits the number of reports that can be generated at the same time (the default is 2). This is controlled by the following
The report-generation process uses a significant amount of memory. Note that increasing this parameter's value beyond what the Monitoring Station or reporting instance can handle may result in out-of-memory errors.