(Wily introscope)
Purpose:
Scope: (Assumption)
Procedure:
With the help of Wily introscope the following areas in the java system will
be monitored as a part of regular activity.
CPU utilization
File system usage
OS Memory utilization
Java thread monitoring
Java memory utilization
Http sessions monitoring.
Console view: All the systems monitored under Wily introscope will be
displayed in the single window. (Expert usage)
Investigator view: We can monitor each and every individual system in this
view (Beginners usage).
Aravindhan Rajkumar
Pre-requisite: The SAP OS collector should be running to view these values.
Click on any one of the parameters in the investigator tab to view the
graphical representation.
Aravindhan Rajkumar
The CPUs performance can be monitored from the current time to the
custom range based on our purpose.
Click on the required file system and monitor the free usage,
Aravindhan Rajkumar
Operating system memory utilization:
Aravindhan Rajkumar
The parameters such as free memory, free swap should be monitored here.
Click on the parameter and view the graph in the right tab.
Java thread monitoring:
Basics of Threads:
Threads in java will process all the j2ee requests in the java systems.
Thread manager: Supplies the threads required for the core J2EE engine to
operate.
To monitor the threads usage in the wily introscope, please navigate to the
below tabs
Aravindhan Rajkumar
The parameters such as ActiveThreadsCount, CurrentThreadCount,
WaitingTasksCount,WaitingTasksUsageRate, MaxThreadCount should be
monitored.
ActiveThreadsCount: The number of threads from the thread pool, which are
executing a Runnable task pool
CurrentThreadCount: The current number of threads created in the thread
pool.
From the wily introscope we can monitor the thread manager as below,
Aravindhan Rajkumar
Likewise please click on each parameter required mentioned above.
From the above figure we can see the active thread count as 11.
Aravindhan Rajkumar
Java memory utilization:
In java, Java Virtual Machine (JVM) will allocate the memory from the OS
level.
The objects that no longer use the memory must be released. This is taken
care by the a special process called Garbage Collector (GC)
The objects will be first placed in the eden spaces. (i.e.) recently created
objects will be placed in this space.
The objects, which survive some young generation collections, are moved to
old generation.
Permanent generation:
The objects, which are needed permanently for the java system (class
metadata), will be placed here.
1) Minor GC
2) Full GC.
Minor GC: Will clear the objects in the new generation, which are no longer
required.
Full GC: Will clear the objects in both young & old generation.
Aravindhan Rajkumar
The parameters such as Minor GC time (ms), Full GC time (ms), Eden After,
Eden Before, Tenured After, and Tenured Before should be monitored as a
part of regular activity.
Eden Before- Memory space in the young generation before the minor GC
was executed.
Eden After - Memory space in the young generation after the minor GC was
executed.
Tenured before- Memory space in the old generation before the full GC was
executed.
Tenured after- Memory space in the old generation after the full GC was
executed.
We should compare these spaces to check whether the full GC actually
cleared the objects.
Aravindhan Rajkumar
KPI for GC:
GC Heap:
Aravindhan Rajkumar
Http sessions monitoring:
This parameter denotes the number of http requests to the particular server
node and the total response time of the same.
Aravindhan Rajkumar
Appendix:
Once you have familiarised with the above activity, please use the Console
view in the wily introscope to monitor all parameters of the multiple systems
in the same window.(Short span monitoring).
Aravindhan Rajkumar