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 up.time 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 up.time installation directory on the local Monitoring Station file system:

  • Linux: /usr/local/uptime/
  • Windows: 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 uptime.conf parameter:

publishedReportRoot=<location>

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.

Topics on this page

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 up.time Configuration panel, as outlined in Modifying up.time Config Panel Settings.

Change the expiry limit through the following parameter (the default value is shown):

reportCacheExpiryDays=30

 

Tuning Resource Usage Report Generation

Due to the large number of options available for the Resource Usage report, generating an extensive report for a large group of Elements can take several minutes. If exhaustive report generation is necessary, but taking too long, you can increase the number of report images (the default being 10) that up.time concurrently generates for this type of report.
Note that the default number is optimal in most cases; increasing the amount may improve performance, but the law of diminishing returns applies, as too many concurrent threads can tax the PDF generation process overall.

You can manually change the number of concurrently generated images in the up.time Configuration panel with the following parameter:

reporting.prefetch.images.threads=10

Adjusting Simultaneously Generated Reports

up.time limits the number of reports that can be generated at the same time (the default is 2). This is controlled by the following uptime.conf parameter:

maximumPdfReports=2

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.

  • No labels