Bug 535432 (RHQ-2128) - Indicate the results of inidividual conditions in the alert notification email
Summary: Indicate the results of inidividual conditions in the alert notification email
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: RHQ-2128
Product: RHQ Project
Classification: Other
Component: Alerts
Version: unspecified
Hardware: All
OS: All
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-04 13:36 UTC by Lukas Krejci
Modified: 2010-08-12 16:45 UTC (History)
3 users (show)

Fixed In Version: 2.4
Clone Of:
Environment:
Last Closed: 2010-08-12 16:45:52 UTC
Embargoed:

Attachments (Terms of Use)

Description Lukas Krejci 2009-06-04 13:36:00 UTC 
If we have an alert with the conditions ORed together, it is not clear from the email notification what caused the alert to trigger.

This feature was indicated as useful in the IT case 301647.
Comment 1 Joseph Marques 2009-06-04 21:19:51 UTC 
i believe this is a bug, not a feature.  we do attempt to show the actual values that triggered the alert in the email, but for some reason are not properly propagating the values when the condition is availability-based.
Comment 2 Joseph Marques 2009-06-04 21:21:19 UTC 
Here is what the missing availability values look like:

- Conditions: 
  - Condition 1: null Availability goes DOWN
  - Date/Time: 2009/06/04 08:31:59 EDT
  - Details: DOWN

  - Condition 2: null Availability goes UP
  - Date/Time: 2009/06/04 08:33:00 EDT
  - Details: UP

Notice the "null".
Comment 3 Red Hat Bugzilla 2009-11-10 20:58:23 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2128
Comment 4 Heiko W. Rupp 2010-02-25 16:12:31 UTC 
Nulls are now suppressed 
Version f3d2b48
Comment 5 Steve Salevan 2010-03-09 21:39:21 UTC 
VERIFIED on 4/9 master branch git pull.
Comment 6 Corey Welton 2010-08-12 16:45:52 UTC 
Mass-closure of verified bugs against JON.
Note You need to log in before you can comment on or make changes to this bug.