Wily Java Pro Filer (1)

8/2/2019 Wily Java Pro Filer (1)

1/16

22 April 2012

Wily

TCS


2/16

22 April 2012 1

Components

Introscope overview

Introscope uses ProbeBuilder to add probes to applications. Probes measurespecific information about an application without changing the applicationsbusiness logic. AutoProbe dynamically adds probes to each application when itstarts. After the probes are installed in an applications bytecode, the application

is called Introscope-enabled.As an Introscope-enabled application runs, probes relay collected data to theAgent, which is installed on the same machine as the Introscope-enabledapplication. The Agent collects and summarizes the data and sends it to theEnterprise Manager, so that one or more Workstations can access the data.


3/16

22 April 2012 2

WILY ARCHITECTURE

This illustration shows the Introscope components and how they

cooperate and communicate with one another:


4/16

22 April 2012 3

Why Wily

Reactive Vs. Proactive: Reduces Mean Time to Resolution (MTTR)


5/16

22 April 2012 4

Why Wily

Monitor critical web applications 24 x 7

Monitor service levels to the end-user

Ensure applications are available and high performing

Rapidly diagnose slowdowns and failures

Establish ongoing control of these critical web applications


6/16

22 April 2012 5

Installation

Download workstation installable from Wily site. You must have proper rights to use

wily workstation.


7/16

22 April 2012 6

Login To Introscope Workstation

Below window is Wily Client login screen

Click OK button.


8/16

22 April 2012 7

Investigator

The Investigator contains two main panes:

Investigator TreeThe left side of the Investigator is a tree structure that organizes metric data reported by the Agents that

report to the Enterprise Manager you are logged into. Metrics are organized hierarchically by host, process, Agent, and Resource

type. Selecting items in the tree causes predefined views to be presented in the Viewer pane. Inactive metrics appear grayed out

in the tree.

ViewerThe Viewer pane on the right side of the Investigator presents details, often graphical, for the resource or metric

currently selected in the tree. Depending on the item selected in the tree, tabs at the top of the Viewer pane allow you to select

one or more views, including the General, Overview, Errors, Traces, and Search views. For some views, options might be available

in the bottom section of the Viewer pane that control the data displayed in the Viewer.


9/16

22 April 2012 8

Management Module Editor

You use the Management Module Editor to create or edit a Management Module, which contains a set of Introscope monitoring

configuration information. Management Modules are listed for each Domain, and contain Elements..Elements are objects that contain and organize data with monitoring logic elements are Alerts, Actions, and Dashboards.


10/16

22 April 2012 9

Workstation Console

The Workstation Console displays metric information in dashboards.

Dashboards are pre-configured windows that present graphical views of current or historical performance and availability metrics.

When you open the Console, it shows live performance and availability data


11/16

22 April 2012 10

Transaction Tracer

Workstation users with appropriate permissions use Introscope Transaction

Tracer to trace the activity of transactions as they flow through a Java Virtual

Machine, or a Common Language Runtime (CLR) in a .NET environment


12/16

22 April 2012 11

Leak Hunter

Introscope LeakHunter is an add-on component designed to help locate the source of potential memory leaks, by watching for

collection instances that appear to be increasing in size over timethat is, if the number of objects stored in the collection

increases over time. Memory leaks that occur in programs that run for short periods (minutes or hours) might not present a major issue. However, for

applications that are running 24 hours a day (like a web site), a small memory leak can soon escalate into a big problem.

Introscope LeakHunter is designed to track information about a noticed memory leak by being turned on, then turned off after

information is gathered. This method of using LeakHunter creates only a small, temporary amount of overhead.


13/16

22 April 2012 12

Analysis

GC Heap Graph: It is clear from the graph that jvms are using

maximum allocated memory and still need more. As morememory is not available JVM crashed.


14/16

22 April 2012 13

Analysis

High JVM CPU utilization: Go and look into your application

architecture and check your code.


15/16

22 April 2012 14

Analysis

Connection Wait Time: Connection wait time should be almost

zero if it is high, check the connection pool settings


16/16

22 April 2012 15

Contacts

For more information contact

Ashish Sheth

Documents

Wily Java Pro Filer (1)