Bug 726508 - Can't create alert condition on certain metrics
Summary: Can't create alert condition on certain metrics
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.1
Hardware: All
OS: All
urgent
high vote
Target Milestone: ---
: ---
Assignee: Jay Shaughnessy
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: jon3
TreeView+ depends on / blocked
 
Reported: 2011-07-28 20:57 UTC by Jay Shaughnessy
Modified: 2012-02-07 19:25 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-02-07 19:25:13 UTC


Attachments (Terms of Use)

Description Jay Shaughnessy 2011-07-28 20:57:59 UTC
It seems that we may be doing something bad with substrings or menu values.
I can't create an alert condition for metrics with names that start with
the name of another metric.

Recreate:

1) Import RHQ Agent resource

2) Navigate the the Agent Measurement Subsystem resource 
  (child of the RHQ Agent)

3) Nav to Alert tab and start a New Alert Def

4) try adding an metric baseline condition on 'Failed Collections Per Minute'

Note that the condition actually shows up using 'Failed Collections' as
opposed to 'Failed Collections Per Minute'.

This is wrong.

For fun, try saving the new alert def. It will fail because
'Failed Collections' is trendsup and you can't create a threshold baseline
condition on a trendsup, because it will never get a baseline.

Note that this is dangerous because, unlike the baseline condition, other conditions would have been saved just fine and this would probably get missed.

Comment 1 Jay Shaughnessy 2011-07-29 21:27:12 UTC
git commit c4a82bca1620900e3bb2c7353ca5425a1ee4b354
Author: Jay Shaughnessy <jshaughn@redhat.com>
Date:   Fri Jul 29 17:20:11 2011 -0400

Since metric def names may not be unique, they are duplicated
for the 'Per Minute' version of certain metrics, don't use them
for the value map keys in alert def drop downs.

- Also, some of these metric name lists are long, sort the
  menu entries.

Comment 2 Mike Foley 2011-08-01 13:20:10 UTC
repro'd in 7/28 build.

Comment 3 Mike Foley 2011-08-01 14:11:14 UTC
verified 8/1 build by following the reproduction steps

Comment 4 Mike Foley 2012-02-07 19:25:13 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


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