[
https://jira.codehaus.org/browse/MCHRONOS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly moved MOJO-1214 to MCHRONOS-34:
------------------------------------------------
Complexity: (was: Intermediate)
Fix Version/s: (was: chronos-jmeter-maven-plugin-1.1)
(was: chronos-report-maven-plugin-1.1)
Component/s: (was: chronos-jmeter)
(was: chronos-report)
Report plugin
JMeter plugin
Affects Version/s: (was: chronos-maven-plugin-1.0-SNAPSHOT)
Key: MCHRONOS-34 (was: MOJO-1214)
Project: Mojo's Chronos Maven Plugins (was: Mojo)
> Add possibility to monitor metrics through jmx
> ----------------------------------------------
>
> Key: MCHRONOS-34
> URL: https://jira.codehaus.org/browse/MCHRONOS-34
> Project: Mojo's Chronos Maven Plugins
> Issue Type: New Feature
> Components: JMeter plugin, Report plugin
> Reporter: benjamin
> Assignee: Kent Sølvsten
> Priority: Minor
>
> In order to correlate performance graphs with target system behavior, it
> could great to add a jmx support to chronos.
> As it's possible to analyze garbage collection logs, the idea should be to
> collect data from specified jmx queries. With this improvement, it will be
> easy to correlate performance with some specific metrics. For example : jvm
> memory usage, Tomcat active threads, ehcache hit ratio, dbcp pools activity
> and specific MBeans.
> regards,
> Bj
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
