...
If this issue affected you, please contact Support for more information about restoring lost service monitors.
Displayed Database version
In Uptime Infrastructure Monitor 7.7.3, the About Uptime Controller field on the About Uptime page displays Database Version 7.7.2 instead of version 7.7.3. This issue does not affect any functions within Uptime and there were no changes to the controller in Uptime Infrastructure Monitor 7.7.3.
Other known issues
| UT-17068 | Uptime creates a high number of database threads every other Sunday night. |
| UT-17065 | Disk Performance Stats are unavailable with MS SQL datastore. |
| UT-17063 | Upgrades to 7.7.x from UT 7.6.1 fail with errors on Oracle 11G. |
| UT-17050 | The Resource Hot Spot report does not work with MS SQL and Oracle datastores. |
| UT-16441 | When editing a Service Monitor, the defaults are populated even when other settings were previously saved. |
| UT-16440 | The Linux Agent daemon doesn't auto-start when rebooting systemd environments |
| UT-16416 | Users receive a Database Unavailable error after upgrading to Uptime 7.7 and adding a network device. |
| UT-16365 | Issues exist when users create and edit an Action Profile in Uptime 7.6.1. |
| UT-16288 | Adding vCenter before adding WMI/Agentless servers prevents the Auto-Discovery Wizard from adding services. |
| UT-15880 | When converting VMs as part of a vCenter upgrade or migration, VMs recreated in Uptime with new UUIDs properly discover the Agent, but are not properly converted from VM-basic to VM+Agent. |
...
IDERA, Inc. considers information included in this documentation to be proprietary. Your use of this information is subject to the terms and conditions of the applicable license agreement.