New Java Processes and Application Servers Will Use Settings From Http Analyser
Java Runtime Monitors
Java Runtime Monitoring - Overview
Java Runtime Monitor provides out-of-the-box remote monitoring and management on the Java platform and of applications that run on it. It monitors performance metrics like Memory (JVM), Garbage Collection (GC) and Thread Statistics. Thresholds can be associated and alarms generated. Further, operations such as Automated Thread dump, Heap dump and PerformGC for management are also supported. The different JVM vendors supported by Applications Manager are Sun JVM, IBM JVM and Oracle JRockit JVM.
In this help document, you will learn how to get started with Java monitoring along with the list of parameters that are monitored using Applications Manager.
Creating a new Java Runtime monitor
Prerequisites for Java Runtime Monitor: Know more about the JVM arguments to add to your application for Java Runtime Monitoring
Using the REST API to add a new Java Runtine monitor: Click here
- Click New Monitor. Choose Java Runtime.
- Enter the IP Address or hostname of the host in which the Monitor is running.
- Enter the SubNetMask of the network.
- Provide the port number in which JDK is running (default: 1099). Also, you can provide multiple ports separated by commas.
- You can enter your own credential details or select preconfigured credentials details in Credentials Manager. If you wish to enter your own credentials, specify username and password details for this monitor.
- Enter the JNDI name. For example, /jmxrmi.
- To enable customized JMX URL, check the Enable JMX URL checkbox and enter the JMX URL. (The URL should be of the format service:jmx:rmi:///jndi/rmi://HOST:PORT/jmxrmi. For example, a jboss customized jmx URL can be - service:jmx:remoting-jmx://HOST:PORT/ and a websphere customized jmx URL - service:jmx:wsrmi://HOST:PORT/)
- If Authentication is enabled, enter the username and password.
- Enter the polling interval time in minutes.
- If you are adding a new monitor from an Admin Server, select a Managed Server.
- Choose the Monitor Group, to which you want to associate the Monitor (optional). You can choose multiple groups to associate your monitor.
- Click Add Monitor(s). This discovers the Monitors from the network and starts monitoring them.
Note:
- Support is available for JRE1.5 and above for Java Runtime. Support for Heap dump operation is available if HotSpotDiagnostic MBean is present in the JVM.
- Support given for JDK 1.8 : When monitoring with JDK 1.8 MetaSpace, Applications Manager monitors and displays new memory space called MetaSpace and Compressed Class Space instead of the former Permanent Generation (Non-Heap).
- In case you are unable to add the monitor even after enabling JMX, try providing the below argument:
-Djava.rmi.server.hostname=[YOUR_IP]
Monitored Parameters
- Availability tab gives the availability history for the past 24 hours or 30 days.
- Performance tab gives the health status and events for the past 24 hours or 30 days.
- List view enables you to perform bulk admin configurations.
Java Runtime Monitor checks theavailability, response time, connection time(time taken by the Applications Manager to look up the JMX agent on the remote JVM) of the monitor, along with many other parameters listed below.
- Overview
- Garbage Collection
- Threads
- Configuration
Overview
| Parameter | Description |
|---|---|
| Monitor Information | |
| Name | Name of the JavaRuntime monitor. |
| Health | Specifies the health (Clear, Warning, Critical) of the JavaRuntime monitor |
| Type | Specifies the type you are monitoring. |
| Host Name | Specifies the host at which the Java virtual machine is running. |
| Port | Specifies the port number at which the Java virtual machine is running. |
| Host OS | Specifies the OS of the host where the JavaRuntime monitor is running. |
| JVM | Specifies the Java virtual machine name and version. |
| Vendor | Specifies the Java virtual machine Vendor Name. |
| Processor Count | Specifies the number of processors available to the Java virtual machine. |
| Last Polled at | Specifies the time at which the last poll was performed. |
| Next Poll at | Specifies the time at which the next poll is scheduled. |
| Availability | Shows the current status of the JavaRuntime monitor - available or not available. |
| Connection Time | Time taken to connect to the Java virtual machine. |
| Memory Pool | |
| Eden Space (Heap Memory) | The pool from which memory is initially allocated for most objects. |
| Survivor Space (Heap Memory) | Pool containing objects that have survived GC of eden space. |
| Tenured Generation (Heap Memory) | Pool containing objects that have existed for some time in the survivor space. |
| Java Heap | Space where the JVM stores the objects. |
| Permanent Generation (Non-Heap)(for versions older than JDK 1.8) | Holds all the reflective data of the virtual machine itself, such as class and method objects. With JVMs that use class data sharing, this generation is divided into read-only and read-write areas. |
| MetaSpace(for JDK 1.8) | The Native memory space for the representation of class metadata is called Metaspace. MetaSpace use native memory to store meta-data and that grows automatically. |
| Compressed Class Space(for JDK 1.8) | Compressed Class Space contains only class metadata. |
| Code Cache (Non-Heap) | Memory used for compilation and storage of native code. |
| JIT Code Cache | Memory that is converted to assembler and stored for running at higher speed. |
| Nursery | Separate space for newly allocated objects. |
| Class Loading | |
| Classes loaded | Number of classes loaded |
| Classes Unloaded | Number of classes unloaded |
| JVM Statistics | |
| CPU Load | Specifies the percentage of load on the machine caused by the JVM. 0 indicates no load is created and 100 indicates all load is created by the JVM |
| CPU Usage | This indicates the CPU usage of the JVM on the server. |
| Max file descriptor | Maximum permissible open file descriptor. Available only for UNIX. |
| Host Memory | |
| Total Physical Memory | Total amount of physical memory in Megabytes. |
| Free Physical Memory | The amount of free physical memory in Megabytes. |
| Total Swap Space | Total amount of swap space in Megabytes. |
| Committed Virtual Memory | The amount of virtual memory that is guaranteed to be available to the running process in Megabytes. |
Garbage Collection
| Parameter | Description |
|---|---|
| Garbage Collector | |
| Time Spent/Min | Approximate collection elapsed time in milliseconds. |
| Collections/Min | Total number of collections that have occurred. |
| Thread Count | Number of threads used for Garbage Collector. |
| Last Start Time | Start time of this GC. |
| Last End Time | End time of this GC. |
| Memory usage before GC | Memory usage of all memory pools at the beginning of this GC. |
| Memory usage after GC | Memory usage of all memory pools at the end of this GC. |
| GC time | Time taken to perform garbage collection. |
| Compile time | Time spent in just-in-time (JIT) compilation. |
Threads
| Parameter | Description |
|---|---|
| Thread Parameters | |
| Total threads started | Total number of threads created and also started since the Java virtual machine started. |
| Peak Threads | Peak live thread count since the Java virtual machine started or peak was reset. |
| Live Threads | Number of live threads currently running. |
| Daemon Threads | Number of daemon threads currently running. |
| Runnable Threads | A thread executing in the Java virtual machine is in this state. |
| Blocked Threads | A thread that is blocked waiting for a monitor lock is in this state. |
| Waiting Threads | A thread that is waiting indefinitely for another thread to perform a particular action is in this state. |
| Timed waiting Threads | A thread that is waiting for another thread to perform an action, for up to a specified waiting time is in this state. |
| Deadlocked | Number of threads that are in deadlock waiting to acquire object monitors. |
Configuration
| Parameter | Description |
|---|---|
| Configuration Information | |
| Uptime | The uptime of the Java virtual machine. |
| Java Virtual Machine | The Java virtual machine implementation name. |
| Vendor | The Java virtual machine implementation vendor. |
| Process ID | The process identifier is a number used by some operating system kernels to uniquely identify a process. |
| Name | The name representing the running Java virtual machine. |
| VM arguments | The input arguments passed to the Java virtual machine which does not include the arguments to the main method. |
| Class path | The Java class path that is used by the system class loader to search for class files. |
| Library path | The Java library path. |
| Boot class path | The boot class path that is used by the bootstrap class loader to search for class files. |
| JIT compiler | The name of the Just-in-time (JIT) compiler |
| Objects Pending for finalization | The approximate number of objects for which finalization is pending. |
| Operating System | The name of the operating system. |
| Architecture | The operating system architecture. |
| Processors | The number of processors available to the Java virtual machine. |
| Max Metaspace | The maximum metaspace containing all other large class metadata including methods, bytecode ,constant pool etc. |
| Max non-heap | Max Non Heap = Commit Non Heap + free Physical Memory. Note: In case of Virtual Memory also, we consider only Free Physical Memory to calculate Max Metaspace value. |
The table below lists the different JVM vendors supported by Applications Manager and the major parameters monitored by them.
| Parameters Monitored | Sun JVM | IBM JVM | JRockit JVM |
|---|---|---|---|
| Connection Time |  | | |
| Memory Usage | | | |
| CPU Usage | | | |
| CPU Load | | ||
| System Memory | | | |
| Process Memory | | | |
| Heap Memory | | | |
| Non Heap Memory | | | |
| VM Statistics | | | |
| Total Physical Memory | | | |
| Free Physical Memory | | | |
| Total Swap Space | | ||
| Free Swap Space | | ||
| Committed Virtual Memory | | ||
| Garbage Collector- Summary | | | |
| Garbage Collector - View impact for specific collector | | ||
| Total Threads Started | | | |
| Peak Threads | | | |
| Live Threads | | | |
| Runnable Threads | | | |
| Blocked Threads | | | |
| Waiting Threads | | | |
| Timed Waiting Threads | | | |
| Daemon Threads | | | |
| Deadlocked | | | |
| Configuration Details | | | |
| JVM Actions | | | |
View Thread Dump
There is an option to view the thread dump history under 'Threads' tab. Click the 'View Thread Dump' link in the threads tab. TheThread Dump screen will open up in a new window and you will be able to view the current thread dump details. Once you close this window, the thread dump details will be moved under theThread Historysection. You can view this information any time you want from this section.
Reports
We provide the option to view both realtime and historical data of any of the attributes present in the 'Configuration Information' section in theConfiguration tab. Click on any attribute under the Configuration tab. This will open up a new window named 'History Data' that provides more information about these attributes.
There are two tabs in theHistory Data window - History Report and Global View
History Report: This tab provides historical reports of the attribute selected based on time period chosen. You can also use theSelect Attribute drop-down box and view reports for other attributes.
Global View: This tab displays the current values of the attribute selected, across multiple monitors. To view information about other attributes present in the monitor, use theSelect Attribute drop-down box and change the attribute.
If you want to view data of multiple attributes, click theCustomize Columns link present at the top left corner of the window. This will take you to theEdit Global Viewscreen. In this screen, you can change the monitor type using theFilter by Monitor Type drop-down box, select the metrics to be displayed, and show monitors on a monitor basis or a monitor group basis. After you select your options, click theShow Report button to view those information in theGlobal View tab.
Note: If jmx connection is not being established in the machine where Applications Manager is installed, use this key and restart your application:
-Djava.rmi.server.hostname=YOUR_IP
Help Links for Reference
- Tuning Garbage Collection with the JVM
- FAQ About the Java HotSpot VM
- FAQ about Garbage Collection in the Hotspot JVM
- Java Performance Documentation
New Java Processes and Application Servers Will Use Settings From Http Analyser
Source: https://www.manageengine.com/products/applications_manager/help/java-runtime-monitors.html
0 Response to "New Java Processes and Application Servers Will Use Settings From Http Analyser"
Post a Comment