Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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.

2
Click the Response Time Breakdown tab.
4
Click Map to Application Component.
1
Select Hosts and click Next.
3
Click Finish.
1
Select Application Components and click Next.
For example, to map a datasource to an Oracle® database instance, select DBO_Instance.
3
Click Next.
4
Click Finish.
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.

For more information, see Configuring Response Time Breakdown settings.

Investigating error breakdowns

The Error Breakdown Explorer dashboard opens.

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.

For more information, see the following topics:

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:

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

Figure 19. Errors tab

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation