Bug 1795684 - [RFE] Drop support for hystrix monitoring integration
Summary: [RFE] Drop support for hystrix monitoring integration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ovirt-4.4.0
: ---
Assignee: Martin Perina
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-28 16:13 UTC by Martin Perina
Modified: 2021-11-25 14:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Removed functionality
Doc Text:
Hystrix monitoring integration has been removed from ovirt-engine due to limited adoption and difficulty to maintain.
Clone Of:
Environment:
Last Closed: 2020-05-20 20:02:59 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
pelauter: planning_ack+
mperina: devel_ack+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44086 0 None None None 2021-11-25 14:56:16 UTC
oVirt gerrit 106616 0 master MERGED core: Remove hystrix monitoring support 2020-04-26 21:09:51 UTC

Description Martin Perina 2020-01-28 16:13:35 UTC 
Hystrix monitoring integration has been introduced in oVirt 4.1 BZ1347628, but it was not widely adopted/used. Recently most of packages with required dependencies has been orphaned and we don't have enough resources to maintain them. So we need to remove hystrix integration completely
Comment 1 Peter Lauterbach 2020-02-06 14:51:44 UTC 
as we are removing this, is there an alternative feature or method to use to get similar metrics?
Comment 3 Lucie Leistnerova 2020-03-30 08:41:20 UTC 
Verified in ovirt-engine-4.4.0-0.26.master.el8ev.noarch
Comment 4 Sandro Bonazzola 2020-05-20 20:02:59 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.