Converse agora com nosso suporte
Chat com o suporte

Foglight for Application Operations 5.9.8.5 - 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 Using the SOC for APM triage Creating Custom Drag-and-Drop Dashboards APM Tile and View Reference Appendix: Enabling End User Transactions from FxM and FxV

Creating a map agent for FxM appliance data

To visualize real end user activity from an FxM appliance on the map, you must first configure a map agent. A map agent monitors a single FxM appliance. It must be paired with an existing Foglight Real User Monitoring for web agent to import geographical information into Foglight. You can only deploy one map agent per Foglight Real User Monitoring for web agent instance.

 
* 
NOTE: If you are using Foglight APM Appliances, you do not need to configure a map agent.
To create a map agent:
1
On the navigation panel, under Dashboards, click Application Performance Monitoring > Geographical Perspective.
2
The Geographical Perspective for <TransactionName> dashboard opens in the display area.
3
Select a transaction from the Transactions list located at the bottom of the navigation panel.
Figure 100. A list of Transactions appears at the bottom of the left navigation panel
4
On the Geographical Perspective dashboard, click Create a map agent to import geographic data.
The Map Agent Setup wizard opens.
Figure 101. Map Agent Setup wizard
The map agent requires an existing FxM agent that is active and collecting data from a Foglight Experience Monitor (FxM) Appliance.
 
 
* 
IMPORTANT: If your FxM Appliance is at or near capacity, or if it is experiencing packet drops, it is recommended that you do not deploy the map agent. The map agent causes a small but measurable impact on the appliance.
5
Verify that your FxM Appliance and agent are in a healthy state and click Next.
6
On the Advanced Agent Settings page, specify the agent settings.
Figure 102. Advanced Agent Settings page
a
Select the granularity levels at which you want the map agent to import data. You can select any combination of: Hourly, Daily, Weekly, or Monthly. By default, only Hourly and Daily are selected.
b
Specify the location where the map agent is deployed. By default, this is the same Agent Manager that is hosting the FxM agent. Select an alternate location from the list if necessary.
7
Click Finish.
8
On the Geographical Perspectives for <TransactionName> dashboard, click Import geographical data to import the data for that application from FxM to Foglight.
A message box opens.
Figure 103. Message dialog box
9
Review the health of your FxM Appliance.
 
* 
NOTE: If the load on your FxM Appliance is too high due to other geographic data collections that are currently running, you can deactivate those collections to reduce the load. Click the text link: Click here to deactivate or reactivate geographical data import for other applications.
10
Click OK. The map agent imports the geographical data for the selected application.
The dashboard refreshes, displaying the relevant end user activity.
 
* 
NOTE: This process may take some time, depending on the amount of data being imported. If there is no data available for your selected time period, the aggregation interval and timeslice fields appear empty.

If necessary, you can edit the map agent properties through the Agent Status dashboard. For more information, see Editing Map Agent properties.

Editing Map Agent properties

After you have created a map agent, as described in Creating a map agent for FxM appliance data, you can edit its properties from the Agent Status dashboard. For example, you may want to change the available aggregation granularity, or change the scheduled collection interval.

To edit map agent properties:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
Select the map agent in the list and click Edit Properties.
 
* 
TIP: Map agents have the type MapFxMAgent and, by default, their names begin with Geo@.
3
Click Modify the private properties for this agent.
The settings become editable.
4
Ensure that the settings for the FxM Appliance database IP address and password match those that the FxM agent is using to access the database.
5
The Associated FxM Agent Name must match the name of the FxM agent exactly. If this box is blank, or if the value does not match that of the FxM agent, the map agent cannot access the FxM data to populate the geographical perspectives.
6
The Locations Per Measurement setting determines the number of locations from which real end user activity is collected for display on the Geographical Perspective dashboard. By default, this value is 100.
7
The Maximum SQL Retries setting controls the number of times the map agent tries to reconnect to an appliance that is unreachable before stopping data collection. The default is twelve attempts.
8
The five True/False settings allow you to specify the granularity of the data aggregation. Click True for each of the FxM reporting intervals you want to make available: five minutes, hourly, daily, weekly, or monthly. By default, the five minute, weekly, and monthly intervals are disabled (set to False).
 
* 
IMPORTANT: If you have a large number of application components, using the five minute interval can cause a heavy load on the FxM Appliance, negatively impacting performance.
9
The FxM Application Collection list controls which of the available application components the map agent collects data from.
•
To edit the default list, click Edit. Select or clear the check boxes for the applications and click Save Changes.
or
•
To create a new list without affecting the default list, click Clone.
Type a name for the cloned list and click OK.
To edit the cloned list, click Edit. Select or clear the check boxes for the applications and click Save Changes.
10
The Data Collection Scheduler setting controls how frequently the map agent checks the FxM Appliance for data. By default, the collection interval is fifteen minutes.
 
* 
NOTE: The agent imports all data for the selected granularities up to one hour old, regardless of the collection interval.
To edit the default schedule, click Edit.
To create a new schedule without affecting the default schedule, click Clone.
11
When you are finished setting the agent properties, click Save.

Prerequisites for using the Response Time Explorer dashboard

•
Foglight Management Server, version 5.6.4.2 or later, with the following cartridges installed and configured:
•
Foglight for Application Operations, version 5.7.1 or later
•
Foglight for Java EE Technologies, version 5.8.2 or later or Foglight for Microsoft .NET, version 5.9.1 or later
•
Cartridge for FxM, version 5.6.2 or later
•
Cartridge for FxV, version 5.5.8.1 or later
•
End User Core Cartridge, version 5.6.3 or later
•
Foglight Experience Monitor (FxM) Appliance
•
Foglight Experience Viewer (FxV) Appliance, version 5.6.5 or later

For more information, see Configuring Response Time Breakdown settings.

Associating FxV hitfFilter mappings for response time breakdowns

In order to present a comprehensive view of requests as they relate to end user results, you must create a link from the FxV hit filter to the Java™ request and to the FxM (end user) application result.

For detailed information about configuring FxV hit filters and FxM application results, see the documentation included with the Foglight Experience Viewer and Foglight Experience Monitor Appliances respectively.

The response time breakdown only applies to the specific requests that pass through an instrumented application server. The Front End/Back End time breakdown shown on the Real User (FxM) tile applies to complex multi-hit page objects that match the FxM filter. If there is a substantial difference in displayed response time between the Real User Tile and the response time breakdown, the difference is attributable to non-Java page elements.

By default, if no mapping is provided and an existing hit filter has the exact same name as the transaction, that filter is used. The application result is mapped automatically.

To associate a hit filter to an application result:
1
On the SOC, click the title bar of the Real User (FxM) tile of the application result you want to work with.
The Real User (FxM) Performance detail view opens.
2
Click the Response Time Breakdown tab.
3
Click Associate Hit Filter Mappings.
The Associate Hit Filter Mappings dialog box opens.
Figure 104. Associate Hit Filter Mappings dialog box
4
Click Add.
The Associate FxV Hit Filter Wizard opens.
Figure 105. Associate FxV Hit Filter Wizard
5
Select the hit filter that matches the application result.
6
Optional — click Next to configure proxy objects. For more information about assigning proxy objects, see Assigning proxy objects.
7
Click Finish.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação