Click to add text © 2012 IBM Corporation 1 Streams Console Application Graph Michael Pfeifer Streams Admin Console

© 2012 IBM Corporation 2 Important Disclaimer THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “ AS IS ”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM ’ S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE. The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.

© 2012 IBM Corporation 3 IBM Streams Console Application Graph Agenda  Graph Launch Points  Initial Graph view  Flyovers  Interacting with the Graph using the toolbar actions  Visualizing Stream’s objects using various layouts  Monitoring application health and performance  Limitations Introduction  New function in Concord  Browser based topology of a Streams Application  ILOG Dojo engine for layouts  Supplants the need to launch the IDE to get a Streams topology  Browser based so the topology is viewable external to the cluster  Used to monitor/inspect/investigate instance Health and/or instance Performance

© 2012 IBM Corporation 4 Graph Launch Points  Graph button on the Instance Status page launches the Application Graph in a new browser tab  Ability to graphically monitor all applications in the instance while using the other console functions

© 2012 IBM Corporation 5 Graph Launch Points  Selecting a job(s) and clicking the Graph toolbar item launches the Application Graph into a new browser tab

© 2012 IBM Corporation 6 Graph Launch Points  Application Graph navigation item launches a page inline for all jobs in the instance

© 2012 IBM Corporation 7 Application Graph  Initial view - PEs contained within Jobs with the background color representing PE health  View provides high level instance monitoring, above example shows all jobs healthy except job 1  High level indicator (thermometer icon) that shows a health problem – useful if zoomed with no focus of an unhealthy item  Unhealthy jobs can be investigated by expanding the job container to show PEs and operators

© 2012 IBM Corporation 8 Application Graph  Flyovers provide health and state reasons  PEs, jobs, and operators have context menus to provide trace

© 2012 IBM Corporation 9 Flyover Object Details  Flyovers on Jobs, PEs, Operators, Ports and Streams

© 2012 IBM Corporation 10 Graph Interaction  Toolbar refresh options: Manual Refresh, Automatic refresh, timestamp showing last refresh  Graph can be manually updated with the first button in the toolbar  Automatic refresh is turned off by default, enabled with the second button.  Timestamp shows the last refresh

© 2012 IBM Corporation 11 Graph Interaction  4 ways provided to show various Streams object containment –PEs in Jobs –PEs – Can be expanded to see operators –Operators –Operators in Jobs  4 ways to color graph to represent application performance –Tuple or Byte rate –Health –Congestion  Current selection is shown next to the toolbar icon

© 2012 IBM Corporation 12 Job/PE Layout colored by Health  Job/PE layout  Three levels of nested expansion to aid in navigating larger graphs  Imported/exported streams represented with a green port color

© 2012 IBM Corporation 13 Job/PE layout colored by a rate metric  Tuple and byte rate application throughput represented by line thickness and PE background color  Low throughput blues, medium throughput purples, high throughput reds, no throughput white

© 2012 IBM Corporation 14 PE layout colored by Health

© 2012 IBM Corporation 15 Operator layout colored by tuple rate metric

© 2012 IBM Corporation 16 PE layout colored by congestion  Line thickness and color represent the congested areas  Congestion shown in the Job/PE and PE only layouts

© 2012 IBM Corporation 17 Graph Interaction  Zoom out, zoom to specific percent, zoom in, zoom to 100%, zoom to fit enable the graph to show more or less detail as needed

© 2012 IBM Corporation 18 Graph Interaction  Schema details and Operator icons are turned off by default to reduce the amount of data flowing to the browser

© 2012 IBM Corporation 19 Limitations  The console application graph is a browser based solution therefore the performance will vary widely depending on the network speed, the available memory, the pc or laptop processor speed, the JavaScript engine performance, etc..  The application graph object load threshold shown above enables a warning message within the application graph when the number of PEs and PE links exceeds the value.  The setting is provided to allow intervention before loading a large graph that may take a long time, or hang the browser window or even crash the browser window.  Filtering by selecting a job(s) from the Jobs navigation item is one way to get around the large graph problem.  After the initial load the refresh time is substantially faster.