Converse agora com nosso suporte
Chat com o suporte

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

Aggregated Traces table

The Aggregated Traces table, on the top right side of the view, lists a series of aggregate traces over the time period for the selected requests. Aggregate traces are created using the aggregate time interval, which is set to one (1) hour by default. They contain information about all the traces collected within the aggregate time interval, and are useful for investigating a group of single traces all at the same time. Aggregate traces are identified by the start time of the aggregation. There is only one aggregate per interval.

Time

Start time of the aggregation.

End Time

End time of the aggregation.

Length

Total time of all requests within the aggregation to complete.

Traces Included

Total number of single traces included in the aggregate trace.

Execution Time (s)

Avg, Max, and Total

Average, maximum, and total time taken by the request to complete.

Exceptional Exit Count

Number of requests which exited with an exception.

Incomplete Count

Number of requests which have timed out.

Avg Execution Time by Component Technology (s)

Average execution time spent using the specified technology.

For more information, see Viewing breakdowns.

Avg Execution Time by Tier (s)

Average execution time spent in the specified tier, in seconds.

For more information, see Viewing breakdowns.

Single Traces table

The bottom right side of the Traces view contains data related to the single trace selected in the Traces table. This table is the list of individual single traces. Clicking a time listed in this table displays the Single Trace view.

Time

Start time.

Origin (Server)

Where the single trace started collecting.

Request URL

The URL of the traced request, truncated according to the URL transformation rules that are in use (default or custom).

For more information about URL transformations, see the topic Setting Rules for Transforming URLs in the Foglight for Application Servers Administration and Configuration Guide or help.

Execution Time (s)

The time the trace took to run.

Response Time (s)

The amount of time, in seconds, that the trace took to complete.

Exceptional Exit

Whether this trace exited with an exception.

Incomplete

Whether this trace timed out.

HTTP Parameters

HTTP parameters are defined in the recording.config property file. If the single trace is using the specified parameters, information is displayed in the table. Click the HTTP parameter value to view more details in the FxV interface. For more information, see Viewing Request Data in FxV in the Foglight for Application Servers Administration and Configuration Guide.

Avg Execution Time by Component Technology (s)

Average execution time spent using the specified technology.

For more information, see Viewing breakdowns.

Avg Execution Time by Tier (s)

Average execution time spent in the specified tier.

For more information, see Viewing breakdowns.

Related Alarms

The number of alarms related to this single trace.

Actions

Shows or hide s the Actions icon.

Performance charts

The Charts area contains graphs of the execution time and performance data for the selected single trace over the selected time period.

The graph displays the Execution Time spent in each component technology (for example, Servlet, RMI Outgoing, HTTP, .NET Method, or ADO) for the aggregated traces.

There are three types of breakdowns:

Viewing breakdowns

Breaking down the execution time by component technology and/or tier allows you to visualize the relative performance and breakdowns of all traces in a set. You can show the amount of time spent in each component of the application server for every trace in a set (aligned by time), and which servers each trace crossed. This is helpful when you have defined custom components to track a set of packages and classes.

Selecting any number of these custom components and tiers displays the average execution time in the Aggregated Traces table and the total execution time for a component technology and tier in the Single Traces table. You can also see breakdowns in chart form for a given request type.

1
In the Traces view, click the customizer icon beside the table you want to modify (either Aggregated Traces or Single Traces). The Show columns menu opens.
3
Click Apply.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação