Chat now with support
Chat with Support

Foglight for Java EE Technologies 5.9.13 - Application Servers User Guide

Monitoring Application Servers Monitoring Systems Monitoring Servers Monitoring Deployed Applications Monitoring Requests Managing Traces Using Object Tracking to Locate Memory Leaks Monitoring Methods Application Servers Monitor Views
JVM view Method Groups view Request Types view Entity EJBs view Message Driven EJBs view Stateful Session EJBs view Stateless Session EJBs view Deployed Applications view JSPs/Servlets components view Resource Adapters components view Web Applications components view Web Services components view .NET views JBoss Services views Oracle Services views Tomcat Services views WebLogic Services views WebSphere Services views JMX Administration dashboard JMX Explorer dashboard
Appendix: Regular Expressions

Sampled Breakdowns tab

There are four types of Sampled Breakdowns: Tier, Component Technology, Application, and Server. Click the name of the sampled breakdown type that you want to view to open its graph.

Table 15. An example of the sampled breakdown tab.

The breakdown types:

•
The Sampled Breakdowns > Tier graph shows the distribution of the response time over different tiers, such as the application servers and database. The results are displayed as a stacked graph, with a different colour representing each tier.
•
The Sampled Breakdowns > Component Technology graph shows the execution-time data for the selected request by component technology. The response time is displayed in segments and each segment represents the time spent in each Java EE Component Technology (for example, HTTP, Servlet, EJB, JDBC, JNDI, or Custom Components). This information helps you accurately determine where to focus your application performance-tuning efforts. The results are displayed as a stacked graph, with a different color representing each component technology.
•
The Sampled Breakdowns > Application graph is a stacked graph that shows the response time by the various applications that serviced the request.
•
The Sampled Breakdowns > Server graph is a stacked graph that shows the distribution of response time over different application servers.

These types of breakdowns are important because they show you if your application is spending more time in your application code versus your database. If a request passes between applications, the Sampled Breakdowns > Application graph shows you how much time is spent in each application. For example, if your application calls to another application for credit card validation, both applications are displayed in the Sampled Breakdowns > Application graph.

Incomplete/Exceptional Exits tab

The Incomplete Requests chart displays the count of incomplete service requests that timed out during the interval spanned by the zonar. Foglight considers a request incomplete when the request does not complete processing within the timeout specified in the recording.config property file.

Figure 12. An example of the incomplete/exceptional exits tab.

The Exceptional Exits chart displays the count of requests that completed with an uncaught exception during the interval spanned by the zonar.

 

Managing Traces

With Foglight for Java EE Technologies and Foglight for Microsoft .NET, you can collect traces on requests. If you have enabled trace collection, you can review Single and Aggregated Traces, as well as Sampled Breakdowns and Overall Request Performance from the Traces view.

There are three main methods for collecting traces:

•
Manually collecting single traces
•
Using a rule action to collect single traces
•
Using Groovy to collect single traces.

Related topics:

•
Viewing traces
•
Trace Diagnosis view
•
Selecting a trace to baseline or compare metrics

Manually collecting single traces

Manually collecting single traces

Single traces can be collected manually from the Application Servers Monitor > Requests > Requests table, or from the Actions panel when any of the Application Servers Monitor dashboard views are selected.

 
* 
NOTE: Collecting single traces using the interface is limited to the set time range. You can collect all single traces by updating the Request Response Time Threshold rule, but it is not recommended because collecting all single traces affects performance. Instead, change the time range. For more information, see Using a rule action to collect single traces .
 
* 
IMPORTANT: Users assigned the “Java EE Read-only User” or the “.NET Read-only User” role have limited access to the Application Servers Monitor dashboard. They cannot initiate single trace collection but all other information is available to them. If tracking single traces is required, update the user’s role to “Java EE Administrator” or “.NET Administrator”.For more information on groups, roles, and users, see the Foglight Administration and Configuration Guide.
To collect single traces:
1
On the navigation panel, under Dashboards, click Application Servers > Monitor.
2
On the Application Servers Monitor dashboard, click the Requests tile.
3
In the Request Types table, click Collect Traces. The Collect Traces dialog box opens.
4
If you want to specify the Request Type using regular expressions, select the Use regular expression check box and type a string in the box below.
For more information about writing regular expressions, see Appendix: Regular Expressions .
5
Select the number of traces that you want to collect in the Number of Traces list.
6
Set the time period for which you want to collect the number of traces in the Collection Period box. The default value is 6000 seconds.
7
Select whether you want to collect methods in full detail or component detail using the Collection Level list. The default value is component detail.
•
Full detail — collects single traces at full detail; all methods in the call tree are captured
•
Component detail — collects single traces at component level only; methods from a defined component technology, including custom components, are captured
 
* 
IMPORTANT: If the application has been instrumented at full detail, then the full detail collection level can be used to collect everything. If the application was instrumented at component level (or less), selecting full detail has no impact. For more information, see the Managing Java EE Agent Configurations topic in the Foglight for Java EE Technologies Installation Guide.
8
Use the Collect SQL Parameter list to indicate whether you want to track SQL bind variable values. The default value is Off. For more information, see SQL tab .
9
Click the check box beside Traces that match to limit the trace collection to All or Any.
10
If you select Any, click the add icon to open the Add criteria menu.
Select a criteria from the list.
•
Response Time — the response time of the request is over or under a specified threshold
•
Exceptional Exit — the request exits due to an exception
•
Incomplete — the request is incomplete
•
Trace Parameter — a parameter of the request is set to a specific value
 
* 
TIP: Specifying criteria to collect particular traces helps you diagnose problems faster.
11
Optional — Click the Collect all parameters check box to collect the values for all parameters. This option is enabled by default.
12
From the Servers list, select the servers from which you want to collect single traces.
13
Click Collect Traces.
The number of manual traces appears in the Traces column of the Request Types table.

Related topics:

•
Using a rule action to collect single traces
•
Using Groovy to collect single traces
•
Viewing traces
•
Trace Diagnosis view
•
Selecting a trace to baseline or compare metrics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating