m (moved Summer Coding 2010 idea - RHQ to Summer Coding 2010 ideas - RHQ: Plural to make it like the category, easier to remember, and shows the inclusive/plurality.) |
(turning my comment in to a comment not leaving it in the page content :)) |
||
| Line 1: | Line 1: | ||
{{:Summer Coding 2010 idea - RHQ - shortinfo}} | {{:Summer Coding 2010 idea - RHQ - shortinfo}} | ||
== More information == | == More information == | ||
<!-- This section is filled with a longer version of whatever the idea-creator wants to say. The header for this page is another page transcluded here and at the main page. --> | |||
The main page for [[Summer Coding 2010]] ideas is [[:Category:Summer Coding 2010 ideas]]. | The main page for [[Summer Coding 2010]] ideas is [[:Category:Summer Coding 2010 ideas]]. | ||
Latest revision as of 01:46, 6 April 2010
The main page for this idea is Summer Coding 2010 ideas - RHQ.
Status: Proposed
Summary of idea: Various ideas related to RHQ: http://rhq-project.org
Contacts: Heiko W. Rupp <hwr @ redhat.com >, pilhuhn on irc.freenode.net/#rhq
Mentor(s): Heiko W. Rupp
Notes: Ideas are e.g. better visual representation of the inventory (graphical forests), new graphing code for metrics (as DOM+CSS+JS versions), allowing different availability check interval for 'important' resources, separating agent heart beat from availability messages or combining data from different resources and types to trigger alerts on this combined data ("Correlation units"). Other ideas are very welcome. Also check the Ideas wiki page at http://rhq-project.org/display/RHQ/Ideas
More information
The main page for Summer Coding 2010 ideas is Category:Summer Coding 2010 ideas.
Status: Proposed
Summary of idea: Various ideas related to RHQ: http://rhq-project.org
Contacts: Heiko W. Rupp <hwr @ redhat.com >, pilhuhn on irc.freenode.net/#rhq
Mentor(s): Heiko W. Rupp
Notes: Ideas are e.g. better visual representation of the inventory (graphical forests), new graphing code for metrics (as DOM+CSS+JS versions), allowing different availability check interval for 'important' resources, separating agent heart beat from availability messages or combining data from different resources and types to trigger alerts on this combined data ("Correlation units"). Other ideas are very welcome. Also check the Ideas wiki page at http://rhq-project.org/display/RHQ/Ideas