Chat now with support
Chat with Support

Foglight for Application Operations 5.9.8 - User Guide

Introducing Foglight APM Monitoring Transactions Examining Response Times Examining Error Breakdowns Viewing Real User Activity from a Geographical Perspective Using the SOC Transactions Tab Creating Custom Drag-and-Drop Dashboards APM Tile and View Reference Appendix: Enabling End User Transactions from FxM and FxV

Configuring Response Time Breakdown settings

In order to use the Response Time Breakdown tab and Explorer dashboard, and the Error Explorer dashboard, you must configure the integration between Foglight for Application Operations and either Foglight for Java EE Technologies or Foglight for Microsoft .NET, as described in: Configuring request breakdowns.
After you have configured request tracing, you may also want to review Configuring URL transformations.
 
* 
TIP: If you are using FxV as your real user data source, you must also associate hit filter mappings with Java™ requests and real user data, as described in Associating FxV hitfFilter mappings for response time breakdowns.

Configuring request breakdowns

Foglight for Java EE Technologies and Foglight for Microsoft .NET provide the ability to trace requests through application servers. When installed along with Foglight for Application Operations, you can view detailed request information matched to the appropriate end user results on the Response Time Explorer dashboard.
If you are using version 5.9.5 or later:
•
Individual request breakdowns are enabled by default.
If you are using version 5.9.4 through 5.9.0:
•
See Configuring Java EE or .NET request breakdowns in versions 5.9.4 through 5.9.0.
If you are using Foglight for Java EE Technologies versions 5.8.3 or 5.8.3:
•
See Configuring Java EE request breakdowns in versions 5.8.2 or 5.8.3.
Configuring Java EE or .NET request breakdowns in versions 5.9.4 through 5.9.0
In order for the request information to be traced correctly, you must configure the Individual Request Breakdowns option for the Nexus™ that is coordinating the .NET® data. For detailed information about the Nexus and for instructions for configuring recording settings, see the Foglight for Application Servers Administration and Configuration Guide.
To enable Individual Request Breakdowns:
1
On the navigation panel, under Dashboards, click Application Servers Administration.
2
On the Application Servers Administration dashboard, click Nexus Administration.
3
On the Nexus Administration page, click the Recording Settings tab.
4
On the Recording Settings view, click the name of the Nexus™ profile that you want to configure, and select Edit from the menu that opens.
The Configuration Category Editor - nexus/recording.config dialog opens.
5
Click the Collection Details tab.
6
Click Edit beside RequestDetailRules.
7
In the Settings Editor: RequestDetailRules dialog box, click Add .
A new row appears in the table.
8
Select the Regex check box.
9
Click the URL box and type the URL for which you want to enable individual requests.
For example: .*medrec.*
10
Select the Individual check box.
11
Click OK.
12
Select the RequestDetailDefault > Individual Requests check box.
Your configuration should resemble the following:
13
Click Save.
Configuring Java EE request breakdowns in versions 5.8.2 or 5.8.3
If you are using Foglight for Java EE Technologies version 5.8.2 or 5.8.3, you must configure request tracing breakdowns through the Java Agent recording.config property file. For detailed information about configuring request tracing, see the Foglight for Java EE Technologies Installation Guide included with the cartridge.
To enable IndividualRequestBreakdowns:
1
On the navigation panel, click Administration > Agents > Agent Properties.
2
In the Namespace > Type column, expand the JavaEE module (click the + sign).
3
Select recording.config.
4
Locate the section that begins with: # Rules for the collection of details on sampled requests.
5
Configure the request detail rules to include IndividualRequestBreakdowns.
For example:
RequestDetailRules = {
/.*medrec.*/ : ("IndividualRequestBreakdowns"),
};
RequestDetailDefault = ("IndividualRequestBreakdowns");
6
Click Save.
Next Steps:
•
Configuring URL transformations

Configuring URL transformations

Foglight for Java EE Technologies and Foglight for Microsoft .NET (version 5.9.x and later) provide the ability to transform Java™ or .NET® transaction URLs for use with the Foglight APM Transactions dashboard. The APM URL Transformation options control the following:
•
Whether APM breakdown request URL transformation rules are used
•
The transformation rules that determine how Java or .NET request samples are grouped into APM transactions
•
How many transactions are created from the transformed requests per collection
These transformations are controlled through the APM URL Transformation settings available from the Nexus > Recording Settings view.
By default, request URLs are shortened to the third ‘/’.
For more information, see the topics “Setting rules for transforming URLs” and “Configuring APM URL transformation” in the Foglight for Application Servers Administration and Configuration Guide or help. This guide also contains detailed information about how URL transformations are configured and performed in general.
Related Topics:
•
Configuring request breakdowns
•
Mapping datasources
•
Additional configuration options
•
Investigating response time breakdowns

Additional configuration options

There are additional configuration options for exploring response time breakdowns that may be useful in some instances. For example, if your dependency path view contains a datasource that needs to be mapped to a specific component, review the topic Mapping datasources. If you are associating FxV hit filter mappings to a transaction that contains a proxy object, review the topic Assigning proxy objects.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating