[ptt-users] How to monitor JVM?

[Frank Cohen]

Dear Yuriy: The Monitor uses a simple and extensible architecture. We  
designed it to add new functions like the JVM details you mentioned.

The source code for the Monitor is found in tm5/TestMaker/PTTMonitor.  
TestMaker communicates with the Monitor over an XML-RPC snapshot  
mechanism. TestMaker then takes care of displaying the statistics in  
the Controller panel and logging the statistics.

We are in discussion with the Glassbox.com folks about integration  
with TestMaker. Glassbox will give us all that great JVM info in a  
snapshot. See below for a copy of our current plan. If you would like  
to jump in with some coding then we would love your support. Also,  
please feel free to comment, criticize, or make a proposal of your own.

Thanks.

-Frank

---

Dear Ron and John:

Thank you for your time today to discuss the integration of  
PushToTest TestMaker and Glassbox. I found your comments and demo  
very helpful. I am very excited about the opportunity to work together.

Here are the topics and actions we discussed:

1) PushToTest will extend its TestNetwork Snapshot system to  
periodically gather Glassbox statistics and alerts using a JMX API  
and protocol.

2) Glassbox will add a Count_Problem_Operations, Time_Spent_Overall,  
and Time_By_Resource APIs to the JMX interface.

3) PushToTest will establish new element definitions in the  
TestScenario schema to provide users with a way to declare Glassbox  
parameters, including the settings Glassbox uses to identify out-of- 
SLA-compliance operations.

4) PushToTest will offer a Tools menu JMX Console command to open the  
Java Console to give TestMaker users access to the JMX interface to  
Glassbox data.

5) PushToTest TestMaker will add icons indicating Glassbox status to  
load testing and service monitoring control panels. Examples of this  
are at: http://bugs.pushtotest.com/ticket/61. These icons bring users  
to the Glassbox Ajax user interface.

6) PushToTest engineers will start on the integration efforts at the  
end of September.

Please let me know if any of these need restating. Thanks. I am very  
excited!

-Frank






On Sep 13, 2007, at 11:20 AM, Yuriy wrote:

>
> Hi.
>
> Monitor can measure only system's CPU and Memory consumption, but  
> in most cases I need to collect JVM's information (GC, heap,  
> threads, etc).
> Are there any possibility to monitor JVM information mentioned  
> above in the TestMaker?
> How can I extend existing Monitor's functionality?
>
> Thanks.
>
> _______________________________________________
> Users mailing list
> Users at lists.pushtotest.com
> http://lists.pushtotest.com/mailman/listinfo/users



--
Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374 7426
TestMaker: The open-source SOA test automation tool