Performance Metrics of APM Insight

Interpret APM Insight Monitoring Results

Monitoring your applications using Site24x7 APM Insight allows you to track and measure important metrics including apdex score, appserver throughput, response time, exceptions and more from a customizable and unified console. On the right corner you can also decide on the time frame for which you need the metrics. Options to edit, unmanage instance, delete instance, copy web script and export to PDF are also given on the top right hand side of the console. Various parameters and metrics can be obtained by accessing the following tabs:

• Overview
  • Data throughput
  • Events Timeline
• Web Transaction
• Database
• Background
• Traces
  • Filter and Advanced Filter
  • Un-instrumented block of code
• JVM (For Java agents)
• IIS (For .NET agents)
• Exceptions
• RUM Analytics
• Milestone
• Server Metrics
• Outages

Overview:

The basic function of this tab is to give a bird's eye view of all the major parameters from an application's point of view.

Also, you can view details about the fastest and slowest transactions by response time as well as the recent exception traces generated.

Data Throughput:

The size of request and response objects are tracked and shown in data throughput. Request size is captured as bytes in and response size is captured as bytes out.

Data throughput helps you assess the size of the incoming request - gives you an idea as how much data your app server is handling.

For instance, from the above image you can understand that the particular transaction 'arh/trace' has a higher request size in comparison with other requests.

This hels you to assess the general size of the incoming requests and this in turn comes handy when there is a sudden spike in the size of the incoming requests.

Example, in case of DDOS attacks, the incoming requests could be of huge data size and by knowing your average request sizes, you can easily spot anomalies.

Events Timeline:

Events Timeline widget records all the events of your selected Application/Instance for a selected time range. You can identify/decode various events from the past, which includes Down, Critical, Trouble, Maintenance, Anomaly, or Suspended. Each event is color-coded for easy identification. Events can be drilled down to extract maximum data and facilitate easy troubleshooting.

Web Transaction:

The various transactions running in the application are listed here along with the following metrics:

You can sort the available data based on values of each parameters. Also, if you select any specific transaction you will get a graphical view displaying different metrics in the form of graphs.

Database:

This section provides a complete description on the total number of SQL queries that are executed for the application.

Background:

Information on the various background tasks such as maintenance, schedulers, messaging etc is provided here.  

Traces:

The various traces that have been run on various applications and all details pertaining to them are listed in this section.

On selecting any particular trace we can dive into individual metrics for each. The drill down is divided into 3 tabs:

• Summary
• Trace Details
• SQL Statements
• Remote calls
• JVM Metrics
• Server Metrics

Traces - Summary:

Gives an overall summary on the trace selected and the slowest components that it was able to identify.

Traces - Trace Details:

Detailed information on what all commands have been executed by the trace and the time taken by each.

Traces - SQL Statements:

Information on all the SQL queries executed by the trace

Traces - Remote calls:

Lists down all the external remote calls made during the execution of the trace. All the external calls made are identified and listed down under two classifications, and the total count is obtained. The two different types of external calls identified are:

• WEBREQUEST
• WCF

 

Traces - JVM Metrics:

For Java applications, you can navigate to Traces > JVM Metrics to get the graph views of the important JVM metrics such as JVM CPU Usage, JVM Classes Count, Heap Memory, and Non-Heap Memory before and after the trace start time. The red mark on the graph indicates the trace's start time. The user can obtain troubleshooting information by comparing the key metrics before and after the tracing.

For example, in the image below, the search criteria has three conditions—Transaction Name as zylker/settings/, Exception as java.lang.NullPointerException, and Response Time as above 2 seconds.

You can click the  icon to view the performance of that particular transaction.

You can view the whole picture of the required trace by clicking directly on it.

Un-instrumented block of code:

In general, the APM Insight agent captures known frameworks and methods in your applications. Components involved in a transaction, including it’s method calls and functions are listed under the Traces tab.

While inspecting a transaction trace, you may encounter a field called un-instrumented block of code.

You may get this message under two circumstances:

A. When you have used custom methods or functions in your application code.

B. Even in known frameworks, the agent may not be able to track all methods or functions, called between two instrumented methods or functions. In such cases, that particular method or function is marked as un-instrumented block of code. This helps you to identify the exact occurrence of the specific method. By knowing the time stamp and the instance of occurrence, you can deploy custom instrumentation to figure out the issue. 

JVM(Only available for Java agent users):

JVM tab is available only if you are using Java agent. This tab will give us all the necessary data on the JVM instance. Various parameters and metrics can be obtained by accessing the following tabs:

• Summary
• Garbage Collector
• Threads
• Configuration

JVM - Summary:

Gives an overall summary on the JVM instance with information on CPU usage, runtime memory, JIT, classes, heap and non-heap memory etc.

JVM - Garbage Collector:

Detailed information on how runtime memory is being managed in the JVM instance. It lists down all the different garbage collectors that are executed along with the collected objects count and time spent

JVM - Threads:

Data on all the different paths followed in executing transactions in the application.

JVM - Configuration:

Complete description of the JVM instance running and other related information such as:

• Host name and version
• Memory type and how much is available
• Up Time
• Thread Count etc.

IIS(Only available for .NET agent users):

This tab is available only if you have enabled APM Insight in IIS monitor console and only if you are using a .NET agent. To know more about how to enable APM Insight in IIS monitoring, please go through our blog on the same topic. Various parameters and metrics can be obtained by accessing the following tabs:

• Summary
• Application Pools

IIS - Summary:

Gives an overall view on the IIS server and the application accessing the server.

IIS - Application Pools:

Information on all the application pools that are running on the IIS server.

Exceptions:

Description of all the exceptions that have occurred with count of how many times they have taken place.

RUM Analytics:

An interface tab which shows all the important data collected by Site24x7 APM Insight RUM agent.

Milestone Tab:

In general, you can mark milestones to review your application performance before and after a feature update, issue fix or performance enhancements etc.  You can view all such created milestones under the milestone tab. Milestones created for the corresponding application, for the chosen time period is listed here.   

Clicking on a particular milestone displays your application metrics before and after the selected time period. 

The following metrics can be compared using milestone markers:

• Apdex score
• App Server Response Time
• Request Throughput
• Data Throughput
• Error Count
• Exception Count
• HTTP Error Rate
• Web, Background and Database transactions

For example, clicking on the 'APM TEST' milestone, displays the application performance for a selected period, before and after one hour.

Image displaying performance of transactions before and after six hours.

You can also compare and view the performance metrics directly by clicking on the milestone view. 

To view this,

1. Go to Milestone View
2. Click on the Milestone name
3. Select the time range and click Apply.

Server Metrics Tab:

In general, you can see a comprehensive list of all the server monitors mapped to the instances of your application. You can also view the server metrics at the instance level and application level separately.

Application-level metrics

If you choose the application name from the top-left menu, you will get the complete list of the server monitors associated with your application.

You can view the whole picture of performance metrics by clicking on the server monitor.

Instance-level metrics

If you choose the instance name from the top-left menu, you will get a thorough picture of all the major performance metrics of the associated server.

You can click the icon to mark an outage as maintenance, edit comments, or even delete any outages if it is irrelevant.

Mark as Maintenance

You can mark a specific outage period as maintenance using the Mark as Maintenance option. After marking an outage as maintenance, the status icon changes to maintenance and the record is still available under the Outages tab. The maintenance can be reverted to outage if needed.

Edit Comments

During any detected outage, Site24x7 will auto-populate the reason for the outage under the Reason section. Anyone, irrespective of the user role, can edit/delete these system-generated comments using the Edit Comments option.

Delete

You can delete any outage or maintenance that is irrelevant using the Delete option.