Bug 1298147 - Missing "Event Detection" option from the drop down list when trying to create an alert using alert template
Missing "Event Detection" option from the drop down list when trying to creat...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
4.12
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks: 1298144
  Show dependency treegraph
 
Reported: 2016-01-13 05:42 EST by bkramer
Modified: 2016-01-13 05:42 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bkramer 2016-01-13 05:42:12 EST
Description of problem:
When trying to create an alert using alert template, "Event Detection" option is not listed in the drop down list "Condition Type". 

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

How reproducible:
Always

Steps to Reproduce:
1. Install and start RHQ environment 
2. Navigate to RHQ UI -> Administration -> Alert Definition Templates -> Linux -> click on the pencil icon to add new alert definition template
3. Click on "New" button, give it a name and navigate to "Conditions" tab
4. Click on "Add" button and navigate to "Condition Type" drop down list;


Actual results:
Presented list does not show "Event Detection" option.

Expected results:
Presented list contains "Event Detection" option.

Additional info:
To enable this option, user needs to navigate to the resource in the RHQ UI -> Inventory and then to repeat above steps. However, when RHQ Server is restarted, "Event Detection" will be disabled again and user will have again to navigate to the resource for which resource type they want to create an alert.

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