Real-Time Coherence Monitoring in Integrated Environments

transcript

Correlating Coherence Monitoring Metrics with Infrastructure, Database, and Application Server Metrics

5 December 2013 - London, UK

Everett Williams

Senior Director of Technology

SL Corporation

Tom Lubinski

Chief Technology Officer

SL Corporation

Disclaimer

The following is intended to outline our general product direction. It is

intended for information purposes only, and may not be incorporated

into any contract. It is not a commitment to deliver any material, code,

or functionality, and should not be relied upon in making purchasing

decisions. The development, release, and timing of any features or

functionality described for SL’s products remains at the sole discretion

of SL.

Agenda

• Customer quotes/Problem Statement

• Data Collected

• Current Tools/Analysis capabilities

• Architecture

• Demo

• Expanding to App Servers

• Challenges

Customer Questions/Comments

• Nodes, Caches, and Services are nice. But we are server people. –

Online Major Retailer

• How do I know if hardware/network are causing my coherence

problem – Major Apparel Company

• Does blade configuration #1 or blade configuration #2 run my

application better? – Major Retailer

• We spend a great deal of time “poking around” looking for system

metrics – Investment Bank.

Assumptions

• 100-500 JVMS

• 10-50 of Hosts

• 100s of caches

• Analysis over time

• Overlapping Data set (more than outlier analysis)

Data Collected and Aggregated

• Coherence Information

– Cache

– Service

– Node

– Storage Manager

• Host Information

– Host CPU/Memory

– Host Network

– Host Process CPU Memory

• Coherence information aggregated to the host level.

What makes Coherence “unique”

• Single task spread across multiple processes and servers.

• Impact of Network and latency

Server view of data

• Single Server

• Single state

• No Context

• Doesn’t scale visually

• Single Server

• Single state

• No Context

Top/NMon

• Single Server

• Single state

• No Context

Taskmon Graphs

• Single Server

• No Context

• Time Series not aligned

Stacked Graphs

• Doesn’t visually scale

• Top N Servers don’t re-sort

Single Graph with Multiple Trends

• Good for Outlier analysis

• Not good for overlapping trends.

• Single Server

• No Context

RTView Enterprise Solution

Collect, Analyze, Correlate, and Visualize data from multiple disparate sources

RTView

Enterprise System RTView

Developer

Generic

VMware Oracle

WebLogic

Oracle

Coherence

… and many more

Oracle

Database

Custom

Package

Connector System

Metrics

Target Systems

DataServers

RTView Enterprise Solution

EM Central Server(s)

ALERTDEFS

Configuration

Management

Aggregation