Bug 1070243 (JON3-31) - Add "Recent Events" portlet into JON Dashboard
Summary: Add "Recent Events" portlet into JON Dashboard
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: JON3-31
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR01
: JON 3.3.0
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-26 13:34 UTC by Heiko W. Rupp
Modified: 2014-12-11 13:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-11 13:59:33 UTC
Type: Task
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JON3-31 0 Major Verified Add "Recent Events" portlet into JON Dashboard [PRODMGT-284] 2015-09-29 20:31:27 UTC

Description Heiko W. Rupp 2014-02-26 13:34:33 UTC
We need a recent events portlet on the dashboard.
That portlet must allow to filter by resource / event source / severity / regexp(?) to limit the events shown

Comment 1 Jirka Kremser 2014-03-26 18:07:00 UTC
It's waiting in master.

branch:  master
link:    https://github.com/rhq-project/rhq/commit/ce4e2505c
time:    2014-03-26 19:03:27 +0100
commit:  ce4e2505c0907544d83cd2d27df8cc9dfeda8af3
author:  Jirka Kremser - jkremser
message: [BZ 1070243] - (JON3-31) Add "Recent Events" portlet into JON Dashboard

         To make the filtering (based on resource name) working, I had
         to add also the new method to the EventCriteria class.

         To sum it up, it is possible to filter by:
         * time ("from, to" or "last n mins/hours/days")
         * resource name - only for global Recent Alerts portlet; it
           accepts also a substring (sqlwise: "like %x%") of a name
         * event source path - it accepts also a substring of a path
         * severity (almost the same as alert priority filtering)
         * result counts (5 is default)

         Having that said, the performance shouldn't be an issue,
         because the filters may be set to fetch only a few records.

Comment 2 Jirka Kremser 2014-04-15 11:19:44 UTC
branch:  master
link:    https://github.com/rhq-project/rhq/commit/d78179e41
time:    2014-04-15 13:17:21 +0200
commit:  d78179e419a07eec4c3cd9ae9d0c2337b34c7c3e
author:  Jirka Kremser - jkremser
message: [BZ 1070243 & BZ 1069688] - Adding a button for resetting the {event
         source|resource} filters. Also the "Filter by time" component
         is now more intuitive that it is has been turned on/off.

Comment 3 JBoss JIRA Server 2014-04-22 13:21:49 UTC
Heiko Rupp <hrupp> updated the status of jira JON3-31 to Resolved

Comment 5 Jirka Kremser 2014-04-28 10:41:16 UTC
It can go to ON_QA, because 3.3.0 will be based on master

Comment 6 Simeon Pinder 2014-07-31 15:51:43 UTC
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993


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