Host listing screen should have a "uptime" column available (as Vm listings screen). This can be useful for many reasons, including quickly detecting recently rebooted hosts (following server crashes) and be aware of hosts running for "to long without rebooting". Reason: Better overview.
Shirly, do we / can we report host uptime via collectd (https://collectd.org/wiki/index.php/Plugin:Uptime )?
(In reply to Yaniv Kaul from comment #1) > Shirly, do we / can we report host uptime via collectd > (https://collectd.org/wiki/index.php/Plugin:Uptime )? We can add it. Should this be moved to metrics then?
(In reply to Shirly Radco from comment #2) > (In reply to Yaniv Kaul from comment #1) > > Shirly, do we / can we report host uptime via collectd > > (https://collectd.org/wiki/index.php/Plugin:Uptime )? > > We can add it. Should this be moved to metrics then? Yes. We can later re-think if we want it elsewhere as well.
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
We will add the uptime collectd plugin to the new metrics store. See: http://www.ovirt.org/develop/release-management/features/engine/metrics-store/ http://www.ovirt.org/develop/release-management/features/engine/metrics-store-collected-metrics
plugin is loaded on engine and hosts /etc/collectd.d/20-builtins-conf-for-ovirt-engine.conf:LoadPlugin uptime however stats are not included in samples as per BZ#1494190 tested in ovirt-engine-metrics-1.1.1-0.0.master.20170919065728.el7.centos.noarch
data reported and searchable by query: collectd_plugin = uptime verified in ovirt-engine-metrics-1.1.1-0.0.master.20171001113530.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.