Two minor comments to the notes: - The receiving is a "JMX Polling Data Receiver" .. so its an "active" receiver that polls and pumps in messages - For KPIs- for standard MBeans we should have the same level (or better) of OOTB analytics and visualizations that say JConsole has.
Sanjiva. On Wed, Jul 17, 2013 at 8:40 PM, Srinath Perera <[email protected]> wrote: > Participants: Sanjiva, BAM Team, Srinath > > 1. We will write a JMX receiver in BAM, which will pull the JMX > properties periodically from given list of servers. > 2. Each JMX MBean property we interested, we provide a name > 3. We will have few JMX properties enabled by default, users can add > remove these. > 4. Adding a reciver add a Stream definitions > > To use the data, we follow following model > > 1. Users go and add a new KPI > 2. Either through a visual wizard or a input box, we generate or write > a HIVE/CEP queries to calculate the KPIs > 3. Users can also define Gadgets presenting the KPI and can add alerts > while defining a KPIs > > > Toolboxes define KPIs , some of which available by default and others > custom written > > --Srinath > > > > > -- > ============================ > Srinath Perera, Ph.D. > http://people.apache.org/~hemapani/ > http://srinathsview.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
