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

Mapping datasources

By default, datasources appear on the Response Time Breakdown tab with limited information. If you know the proper type of a datasource (for example, if it is an Oracle® database), you can map the datasource to a specific application component. A correct mapping provides access to drill down information, such as host or database metrics.

To map a datasource:
1
From the Transactions tab of the SOC, or the Transactions dashboard, open a Real User (APM) Performance detail view, or a Real User (FxM) Performance detail view.
2
Click the Response Time Breakdown tab.
3
Click the icon for the unmapped datasource.
Figure 13. Example - icon of an unmapped datasource
A detail view opens.
Figure 14. Example of a detail view
4
Click Map to Application Component.
The Assign Resolver Wizard opens.
Figure 15. Assign Resolver Wizard
Select whether to map the object to a host, to an application component, or to unassign the current mapping so that you can select a new host or component mapping.
To assign a host object:
1
Select Hosts and click Next.
2
Select a host from the list and click Next.
3
Click Finish.
Now when you click the object’s icon, the Host View opens.
To assign an application component object:
1
Select Application Components and click Next.
2
Select an application component from the list.
For example, to map a datasource to an Oracle® database instance, select DBO_Instance.
Figure 16. Example - mapping a datasource to an Oracle database instance
 
* 
TIP: If you are uncertain of the correct application component topology object name, see Topology object name reference table.
3
Click Next.
4
Click Finish.
Now when you click the object’s icon, the database view opens.
To unassign the current mapping:
1
Select Unassign Current Mapping.
2
Click Next.
3
Click Finish.
The mapping for the object is removed. To assign a different mapping, click Map to Application Component and select a new mapping.

 

 

Examining Error Breakdowns

The Error Breakdown Explorer dashboard displays all sampled requests that have an error in at least one of the components of the transaction workflow. Use this dashboard to quickly see where in the workflow errors have occurred. If an error trace is available, you can drill down for more details.

For an overview of how to use this dashboard, see Investigating error breakdowns.

Requirements for using the Error Breakdown Explorer dashboard
•
Foglight for Java EE Technologies, version 5.9.2 or later
or
•
Foglight for Microsoft .NET, version 5.9.1 or later

For more information, see Configuring Response Time Breakdown settings.

Investigating error breakdowns

To view the Error Breakdown Explorer:
•
On the navigation panel, under Dashboards, click APM > Error Explorer.

The Error Breakdown Explorer dashboard opens.

Figure 17. Error Breakdown Explorer dashboard

This dashboard displays the top sampled requests with errors for a selected transaction during a selected timeslice. The table lists the top twenty-five requests with the most errors for a selected end user session during the selected timeslice. The requests are sorted by number of errors. If an error trace is available, you can drill down for more details.

The timeslice is the collection period during which the currently selected request took place. It is highlighted in the graph on the right, and displayed in the lower left corner of the dashboard.

To view the error counts for a different transaction:
•
Open the navigation panel and select a transaction from the Breakdown for Transactions list.
Figure 18. An example of the transaction list in the navigation panel

For more information, see the following topics:

•
Requests with errors in the selected timeslice
•
Next steps

Requests with errors in the selected timeslice

The Error Explorer Breakdown dashboard is divided into two sections: a list of the sampled requests with the most errors, and a dependency path view that allows you to trace the request through the components. Select a request from the list to update the dependency path view on the Error Breakdown tab.

In the dependency path view:

•
Blue arrows mark the path of the currently selected request.
•
Dark grey arrows indicate the path taken by at least one request in the current timeslice (for example, between 9:45 and 10:00 AM).
•
Light grey arrows indicate the path taken by at least one request in the time range selected by the zonar (for example, in the last four hours).
•
Yellow exclamation marks indicate where errors occurred in the currently selected breakdown.

On the Errors tab, you can see what the error was. For example:

Figure 19. Errors tab

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação