What is Java App Trace monitoring?
Java programming language is an object oriented language originally developed at Sun Microsystems (acquired by Oracle Corporation). It is one of the world's most used enterprise programming language and powers every Android smartphone inside the Android SDK.
Java applications typically rely on Java Virtual Machines (JVM), classes (applet, servlet, jsp...) and provide garbage collection mechanisms. The most popular Java application servers are Apache Tomcat, JBoss, Weblogic, WebSphere....
The Java app has its own best practices and tools for assessing performance while development phase, but unlike development, java production application monitoring differs. Doing code level profiling has an inevitable cost and performance tradeoff. Plus, production engineers do not always have hands on each production application code with a dedicated development team on demand, which is why the ServicePilot application instrumentation happens without modifying or touching the existing codebase.
ServicePilot provides a production application monitoring package which aims at being the first step to any application improvement and operational performance reporting.
ServicePilot standard Java production application monitoring is the monitoring of real user experience, every single business transaction, application usage metrics, regardless of its application code.
In order to provide a real full-stack performance visibility over your Java application, several packages can be added to fill in application topology map, testing or application dependencies monitoring: Web Servers, JVM, Databases, logs, HTTP(S) web tests and scenario and many more.
Java Application Trace monitoring
This package monitors HTTP(S) transaction traces from Java web applications.
This package uses a ServicePilot Agent in combination with a Java Agent to instrument Java web applications to automatically collect their web transactions statistics.
This allows to gather summarized statistics (min,max,avg...) per Java application such as:
- Requests per minute
- HTTP return codes and methods
- Number of transactions in each response time range
- Established transactions
In order to provide deep Java application insights, details collected per transaction include:
- URL and web page path
- IP client and HTTP host
- Real User Response time
- HTTP Return code and method