[jira] Updated: (GERONIMO-3680) The Monitoring agent should optimize DB activity
[ https://issues.apache.org/jira/browse/GERONIMO-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3680: Affects Version/s: 2.2 2.1.1 Fix Version/s: 2.2 The Monitoring agent should optimize DB activity Key: GERONIMO-3680 URL: https://issues.apache.org/jira/browse/GERONIMO-3680 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Reporter: Anita Kulshreshtha Fix For: 2.2 Attachments: view4.jpg Currently the agent needs to be loaded in the same JVM as the server being monitored. The agent skews the statistics being monitered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3680) The Monitoring agent should optimize DB activity
[ https://issues.apache.org/jira/browse/GERONIMO-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Kulshreshtha updated GERONIMO-3680: - Attachment: view4.jpg This graph was drawn with Monitoring console running locally with portoffset=10. The agent was running in the default instance. The commiitted transaction graph shows Tx committed every interval (5 minutes). There was no other application running on G. The Monitoring agent should optimize DB activity Key: GERONIMO-3680 URL: https://issues.apache.org/jira/browse/GERONIMO-3680 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Environment: All Reporter: Anita Kulshreshtha Attachments: view4.jpg Currently the agent needs to be loaded in the same JVM as the server being monitored. The agent skews the statistics being monitered. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
