Ticket #61 (assigned enhancement)

Opened 15 months ago

Last modified 4 days ago

Root-cause analysis using Glassbox

Reported by: fcohen Owned by: fcohen
Priority: major Milestone:
Version: 5.3 Keywords: root cause analysis monitor
Cc:

Description

A utility that uses JMX to gather information from a running application to do root cause analysis. The concept is to operate Glassbox while a test runs and integrate the Glassbox results into the results charts in TM.

Glassbox details are at http://www.glassbox.com/glassbox/Home.html

Attachments

monitor.jpg (85.2 kB) - added by fcohen 12 months ago.
Service monitor with Glassbox alerts shown
realtime.jpg (46.9 kB) - added by fcohen 12 months ago.
Load test with Glassbox integration

Change History

Changed 15 months ago by fcohen

  • owner changed from wmartinez@… to fcohen
  • status changed from new to assigned
  • type changed from defect to enhancement
  • summary changed from Enhanced root-cause analysis using Glassbox to Root-cause analysis using Glassbox

Changed 13 months ago by fcohen

  • priority changed from minor to critical

John Heinz of Glassbox wrote:

Hi Frank,

It was good talking with you this afternoon. I think bundling Glassbox with TestMaker would be a great idea. Here my summary of the conversation, please add any details that I forgot while driving. I'll find out what availability Ron has to talk with you about this and get back to you (if he doesn't first.)

* TestMaker is a multi-node SOA/WS/Web application test environment and monitoring system * TestMaker can be paired with the "TestMaker Monitor" that deploys into systems under test * The "Monitor" currently monitors CPU/Thread load and Memory usage * Integrating/Bundling Glassbox with the Monitor is a natural pair * The Glassbox Installer would likely be lifted out into the Monitor installer * JMX would be the likely communication bus between the Monitor and Glassbox * TestMaker 5 is due to be released in a week * Testmaker 5.1 could be released in 4-6 weeks with Glassbox integrated into the Monitor

Thanks, John Heintz

Changed 12 months ago by fcohen

Service monitor with Glassbox alerts shown

Changed 12 months ago by fcohen

Load test with Glassbox integration

Changed 12 months ago by fcohen

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

Changed 11 months ago by fcohen

  • priority changed from critical to major

Changed 10 months ago by fcohen

  • priority changed from major to minor

Changed 7 months ago by fcohen

  • version changed from 5.1 to 5.2

Changed 6 months ago by root

Milestone release deleted

Changed 5 months ago by fcohen

  • version changed from 5.2 to 5.3

Changed 4 days ago by fcohen

  • priority changed from minor to critical

Changed 4 days ago by fcohen

  • priority changed from critical to major
Note: See TracTickets for help on using tickets.