[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-buglist
Subject:    [Buglist] [JIRA] Updated: (NMS-4364) Interactive JMX data collection configuration UI
From:       jira () opennms ! org (Steve Hillier (JIRA))
Date:       2011-01-22 2:24:50
Message-ID: 1718753771.1455.1295663090267.JavaMail.jira () mail1 ! opennms ! com
[Download RAW message or body]


     [ http://issues.opennms.org/browse/NMS-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Steve Hillier updated NMS-4364:
-------------------------------

    Description: 
Configuring JMX data collection is not user friendly. Currently one must:
Open JConsole, 
  connect to JVM, 
browse mbean server until target for collection is found, 
copy-and-paste the name into the vi editor, 
configure the RRD stuff, 
then restart opennms. 

Really? Does it have to be that cumbersome?

Browsing an mbean server on a discovered JMX server is a trivial task with many \
examples to be found. Re-writing XML files is trivial.
Reading XML files is trivial.
Reconfiguring runtime config data beans with new information
 --- This one is part of my research into parts of the code base I don't normally \
look at. I'm hoping to find some kind of life-cycle management on configuration data \
sources. If not, this could get very interesting....

I think ease of use is key to adoption rates. Making the act of configuring JVM \
performance monitoring a point-and-click operation is likely to make for a compelling \
feature.

Once it's built, it might even be re-usable for SNMP data collection configuration \
(think: SNMP MIB browser).


  was:
Configuring JMX data collection is not user friendly. Currently one must:
Open JConsole, 
  connect to JVM, 
browse mbean server until target for collection is found, 
copy-and-paste the name into the vi editor, 
configure the RRD stuff, 
then restart opennms. 

Really? Does it have to be that cumbersome?

Browsing an mbean server on a discovered JMX server is a trivial task with many \
examples to be found. Re-writing XML files is trivial.
Reading XML files is trivial.
Reconfiguring runtime config data beans with new information -- Not sure how involved \
this might get...

I think ease of use is key to adoption rates. Making the act of configuring JVM \
performance monitoring a point-and-click operation is likely to make for a compelling \
feature.

Once it's built, it might even be re-usable for SNMP data collection configuration \
(think: SNMP MIB browser).



> Interactive JMX data collection configuration UI
> ------------------------------------------------
> 
> Key: NMS-4364
> URL: http://issues.opennms.org/browse/NMS-4364
> Project: OpenNMS
> Issue Type: Enhancement
> Components: Web UI - Admin
> Affects Versions: 1.9.3
> Environment: all
> Reporter: Steve Hillier
> Fix For: Unspecified
> 
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
> 
> Configuring JMX data collection is not user friendly. Currently one must:
> Open JConsole, 
> connect to JVM, 
> browse mbean server until target for collection is found, 
> copy-and-paste the name into the vi editor, 
> configure the RRD stuff, 
> then restart opennms. 
> Really? Does it have to be that cumbersome?
> Browsing an mbean server on a discovered JMX server is a trivial task with many \
> examples to be found. Re-writing XML files is trivial.
> Reading XML files is trivial.
> Reconfiguring runtime config data beans with new information
> --- This one is part of my research into parts of the code base I don't normally \
> look at. I'm hoping to find some kind of life-cycle management on configuration \
> data sources. If not, this could get very interesting.... I think ease of use is \
> key to adoption rates. Making the act of configuring JVM performance monitoring a \
> point-and-click operation is likely to make for a compelling feature. Once it's \
> built, it might even be re-usable for SNMP data collection configuration (think: \
> SNMP MIB browser).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]