...
uptime.conf Settings Summary
The following are up.time settings and default values that are found and modified in the uptime.conf file. Note that any changes to these parameters requires the up.time Core service to be restarted.
Setting | Definition | Default |
|---|---|---|
| Enables or disables logging of all up.time configuration changes. |
|
| The maximum number of connections that are allowed to the DataStore. |
|
| (c3p0 library) Sets the amount of time a connection can be idle before it is closed. This parameter should only be modified with the assistance of uptime software Customer Support. |
|
| (c3p0 library) Sets the number of helper threads that can improve the performance of slow JDBC operations. This parameter should only be modified with the assistance of uptime software Customer Support. |
|
datastoreHealthCheck.checkinterval | The frequency, in seconds, at which up.time checks that the DataStore database is up (a value of "0" disables this database check). | 5 |
datastoreHealthCheck.timeLimit | The amount of time, in seconds, rechecks will occur before a failed status is confirmed. When the database is determined to be down, the up.time Data Collector service is stopped, and an email is sent to all members of the SysAdmin user group. | 300 |
| The name of the system on which the database is running. |
|
| Properties and values to append to the JDBC database URL. Note that only MySQL and Microsoft SQL Server supports URL properties; this setting will not work if you are using Oracle. | |
| The name of the database. |
|
| The password for the default |
|
| The port on which the database is listening. |
|
| The supported database that is being used ( |
|
| The name of the default database user. |
|
diagnostics.monitorRuntimeSaving.deleteFrequency | The frequency at which service monitor runtime data older than stated in the This parameter should be fine-tuned with an additional suffix: | .minutes=5 |
diagnostics.monitorRuntimeSaving.enabled | Determines whether service monitor performance-analysis data (such as run times and start-up delays) are written to the DataStore. When enabled, this data is included in A real-time summary of this runtime data can also be accessed at This parameter should be enabled when diagnosing up.time performance issues with uptime software Customer Support. | true |
diagnostics.monitorRuntimeSaving.saveDays | The number of days' worth of service monitor runtime data to keep in the up.time DataStore. | 7 |
diagnostics.monitorRuntimeSaving.saveFrequency | The frequency at which service monitor runtime data is written from the cache to the DataStore. This parameter should be fine-tuned with an additional suffix: | .seconds=30 |
| The path up.time uses to search for maintenance scripts and executables such as |
|
| The hostname and port of the up.time server. |
|
| The type and amount of information up.time writes to a log file. |
|
maximumPdfReports | The maximum number of reports that can be generated at the same time. | 2 |
| The directory in which reports are published for external consumption. |
|
reportingInstance | If set to true, indicates whether the up.time installation is functioning only as a remote reporting instance, and not as a Monitoring Station. | |
| The number of threads allocated to service and performance monitor activity. |
|
| A list of IP addresses that represents the systems that are allowed to connect to the up.time core data service. |
|
| For a UI instance: the port through which the instance can communicate with the data-collecting Monitoring Station. |
|
| For a UI instance: the host name or IP address of the up.time Monitoring Station that is performing data collection, and to which this UI instance will connect. |
|