Bug 1071197 - [RFE] Notification events only for selected objects - eg. specific VMs, tags...
Summary: [RFE] Notification events only for selected objects - eg. specific VMs, tags...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-notificiations
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Mooli Tayer
QA Contact: Jiri Belka
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-28 09:02 UTC by Jiri Belka
Modified: 2016-02-10 19:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-29 09:05:39 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)

Description Jiri Belka 2014-02-28 09:02:25 UTC
Description of problem:
One could be not interested if a VM called 'uselessVM01' (thus totally useless VM) stops, fails... but one would be very very interested if a very important VM with high SLA stops or fails, like 'important-sla1-DB01'.

Thus we would need to have more fine-grained notification events subscription settings.

We would need to have an option to assing some events for specific VMs, tags (which can simulate virtual folders/grouping - sla1 VMs, sla2 VMs...), storage (some storage can be faster than other or could have metro-mirror thus more important than other ones...) etc...


Version-Release number of selected component (if applicable):
beta3

How reproducible:


Steps to Reproduce:
1. are you able to assing notification for a specific VM?
2.
3.

Actual results:
no, you are not right now

Expected results:
yes

Additional info:
not sure if this should be managed on one place, maybe yes... but if this can be also managed on specific object it would be easier for 'quick' event assignment because the view already would know to what objects notifications are going to be attached.

Comment 1 Itamar Heim 2014-03-02 05:42:38 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-04 09:18:58 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Mooli Tayer 2014-04-06 08:05:57 UTC
While we do not support this feature now,
snmp notification provide a way to do this, as each object from audit_log
is provided in an snmp field. One could define a filter on object in an snmp manager.

Comment 4 Jiri Belka 2014-08-06 12:22:46 UTC
We live in 21st century, it should be doable in UI ;)

Comment 5 Jiri Belka 2014-08-06 12:26:11 UTC
Please take into account also my complain in BZ1119280. Thanks you!

Comment 6 Itamar Heim 2015-03-29 09:05:39 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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