As part of the initial install of Uptime Infrastructure Monitor, the Monitoring Station itself is setup as an element within Uptime Infrastructure Monitor. This sample element is initially setup to use
localhost as it's hostname, along with some sample Service Monitors to test the functionality of Uptime Infrastructure Monitor itself.
One of these sample Service Monitors is the 'Default up.time data store' which tests Uptime Infrastructure Monitor's ability to connect to its MySQL database using the
[email protected] database user. The Uptime Infrastructure Monitor database user is created with limited permissions that only allow it to connect from
If the 'Default up.time data store' Monitor starts failing with an error,
Could not connect to database, check monitor settings, the solution is to edit the Service Monitor, and change the account used to connect to the
reports user instead, which has permissions to connect to the database from anywhere.
The credentials for the
reports user are:
After updating the Service Monitor to use the
reports account, it should now start succeeding again. If you are interested in why adding your vCenter into Uptime Infrastructure Monitor would cause this seemingly unrelated service monitor to start failing, here's the general chain of events that happens:
localhostelement will be updated with the hostname assigned to it by the vCenter. As a result the 'Default up.time data store' will now be trying to connect with the
[email protected]instead of the
[email protected]as explained above.