Bug 1347628 - [RFE] hystrix monitoring integration
Summary: [RFE] hystrix monitoring integration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0
Assignee: Roman Mohr
QA Contact: Aleksei Slaikovskii
URL:
Whiteboard:
Depends On:
Blocks: 1381608
TreeView+ depends on / blocked
 
Reported: 2016-06-17 09:38 UTC by Michal Skrivanek
Modified: 2017-02-01 14:39 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 14:39:57 UTC
oVirt Team: Infra
Embargoed:
michal.skrivanek: ovirt-4.1?
lsvaty: testing_plan_complete+
michal.skrivanek: planning_ack?
dfediuck: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 46890 0 master MERGED core: Monitor action executions with hystrix 2020-01-28 16:08:53 UTC
oVirt gerrit 46909 0 master MERGED core: Monitor query executions with hystrix 2020-01-28 16:08:53 UTC
oVirt gerrit 46913 0 master MERGED broker: Monitor broker commands with hystrix 2020-01-28 16:08:53 UTC
oVirt gerrit 59935 0 None MERGED core: Fix sorting and whitespace errors 2020-01-28 16:08:53 UTC

Description Michal Skrivanek 2016-06-17 09:38:08 UTC 
As announced in http://lists.ovirt.org/pipermail/devel/2015-October/011444.html please provide a hystrix monitoring integration so the code can be profiled and backend bottlenecks identified
Comment 3 Red Hat Bugzilla Rules Engine 2016-07-03 10:23:57 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 4 Sandro Bonazzola 2016-12-12 13:58:42 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Note You need to log in before you can comment on or make changes to this bug.