Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1058861 - [RFE] Notification service: Add structured information to message headers
Summary: [RFE] Notification service: Add structured information to message headers
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Services.Notifier
Version: ---
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ---
: ---
Assignee: Mooli Tayer
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 16:24 UTC by Petr Spacek
Modified: 2017-06-07 16:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-07 16:08:27 UTC
oVirt Team: Infra
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Petr Spacek 2014-01-28 16:24:45 UTC
Description of problem:
RHEV's e-mail notification service sends plain text messages without meaningful e-mail headers. Information contained in human-readable form should be also in e-mail headers (you can see the same thing in e-mails from Bugzilla).

For example, this e-mail:

Time:2014-01-28 06:32:18.999
Message:Critical, Low disk space. laika-vm1 domain has 5 GB of free space
Severity:2
Data Center Name: IDM_BRQ
Storage Domain Name: laika-vm1

... should have at least following headers:
X-RHEV-severity: 2
X-RHEV-DC: IDM_BRQ
X-RHEV-SD: laika-vm1
X-RHEV-msg-type: some value identifying message type, in this case "low disk space"

I mean that "msg-type" should be a distinct value for each checkbox in https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.2/html-single/Administration_Guide/index.html#Setting_up_event_notifications . It can be anything unique, may be there is some internal representation you can simply re-use, I don't know...

Note: I don't care if the header prefix is X-RHEV or X-Ovirt or X-super-cool-notifier :-)

Version-Release number of selected component (if applicable):
rhevm-notification-service-3.2.5-0.49.el6ev.noarch


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