Bug 1319824 - [RFE] Engine and vdsm healthcheck
Summary: [RFE] Engine and vdsm healthcheck
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Oved Ourfali
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 15:35 UTC by Piotr Kliczewski
Modified: 2017-06-07 18:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-07 18:51:42 UTC
oVirt Team: Infra
oourfali: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.