Bug 1319824

Summary: [RFE] Engine and vdsm healthcheck
Product: [oVirt] ovirt-engine Reporter: Piotr Kliczewski <pkliczew>
Component: RFEsAssignee: Oved Ourfali <oourfali>
Status: CLOSED DEFERRED QA Contact: Gil Klein <gklein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, oourfali
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: oourfali: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-07 18:51:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Piotr Kliczewski 2016-03-21 15:35:48 UTC 
We have no way to expose information that any of the components are broken. When people monitor ovirt based solutions they check whether a host on which engine or vdsm is running is reachable and whether the services are up and running. There is no way to check whether hosts are connected from the engine perspective or storage or other parts works fine from vdsm perspective. We are missing information about any "logical" failures.

We need to have a api like healthcheck functionality which would tell monitoring systems or sysadmins whether solution is healthy or not so automated alerts could be triggered.
Comment 1 Yaniv Kaul 2017-06-07 18:51:42 UTC 
We could do it via collectd, but I don't see yet a demand for it. Closing for the time being.