サポートと今すぐチャット
サポートとのチャット

Foglight for Infrastructure 6.3.0 - Foglight for Web Monitor User and Reference Guide

Monitoring Web transactions Exploring your collection of monitored Web sites Investigating the performance of Web transactions and monitoring locations Exploring Web Monitor services Generating reports Configuring Web Monitor agent properties View reference
Web Monitor Performance Browser views Web Monitor Transaction Management views Web Monitor Service Operation Console and Foglight for APM Transactions views

Table 30. Transactions view

The Web Monitor Environment view displays a high-level overview of your monitored environment. The view has two tiles, each representing the monitored objects of interest Transactions and Locations.

Each tile shows how many of the corresponding object instances there are in your monitored infrastructure, as well as the count of objects of that type in each of the alarm states Normal , Warning , Critical , or Fatal ). For example, the following image shows six transactions: none in the Fatal or Critical states, one in Warning, and one the Normal state.

You can move the tiles by dragging and dropping until you achieve the desired layout. To hide one or more tiles, on the tool bar on the right, click , and in the popup that appears, click a tile that you want to hide.

Clicking the object type icon, the object type name, or the object count, shows summary information for that object type in the Quick View. Clicking an alarm state (for example, Warning) on a tile displays summary information in the Quick View for the objects of that type that are in the selected alarm state. If an alarm state has a count of zero, then you can not drill down on the alarm state.

This view appears in the upper part of the Performance Browser, just above the Quick View.

This view is made up of the following embedded views:

Table 29. Locations view

Shows the number of locations in your environment from which Web sites are monitored, and total alarm counts associated with those locations.

Alarm counts. The total counts of alarms generated against the existing monitoring locations, broken down by alarm types (Normal, Warning, Critical, Fatal).
Location count. The number of locations in your environment.

Drill down on:

Alarm counts. Lists the locations associated with the alarms in the Locations view, appearing in the Quick View.
Location count. Displays location-related combination of views in the Quick View.

Shows the number of monitored Web sites in your environment and total alarm counts associated with them.

Alarm counts. The total counts of alarms associated with the monitored transactions, broken down by alarm types (Normal, Warning, Critical, Fatal).
Transaction count. The number of monitored Web sites in your environment.

Drill down on:

Alarm counts. Lists the Web sites associated with the alarms in the Transactions view, appearing in the Quick View.
Transaction count. Displays transaction-related combination of views in the Quick View.

Web Monitor Transaction Management views

The Transaction Management dashboard contains the following views:

Transaction Detail view

The Transaction Detail view provides details about the selected transaction. Use it to find out the URL of the monitored Web site, the type of monitored content, the locations from which this Web site is monitored, and to review and adjust some advanced settings, if needed.

1
On the Administration Home page, click Manage Web Monitor Transactions.
The Transaction Detail view appears in the display area.

This view is made up of the following embedded views:

Shows the URL of the monitored Web site. It also indicates whether the agent should retrieve the page header only, and the expected content.

Expected Content: If content validation is enabled for the agent instance that monitors this URL, and the expected content type is HTML-based, this is indicated in this column. Also, a text string could be used such as “laptop” and type laptop into this column. In case the monitoring agent detects binary content or the text string at this address, the validation fails and the agent logs an error message. If this column is empty, that means the agent is not required to perform content validation.
Content validation can be enabled using the URL List secondary agent properties. For more information, see Settings.
Unexpected Content: If unexpected content validation is enabled for the agent instance that monitors this URL, and the unexpected content type is HTML-based, this is indicated in this column. Also, a text string could be used such as “laptop” and type laptop into this column. In case the monitoring agent detects binary content or the text string at this address, the validation fails and the agent logs an error message. If this column is empty, that means the agent is not required to perform unexpected content validation.
Unexpected Content validation can be enabled using the URL List secondary agent properties. For more information, see Settings.
Get Page Header Only. Indicates whether the monitoring agents collect only the page header.
Display Name. The display name of the transaction.
URL. The URL of the monitored Web site.

Lists one or more hosts on which the monitoring Web Monitor Agent and Foglight Agent Manager are installed.

Agent Name. The name of the Web Monitor Agent instance that gathers information about this transaction.
Location (FglAM). The name of the host on which the Agent Manager is installed.

Displays thresholds for alarm generation and any authentication settings, if they exist.

Authentication and proxy settings. These settings specify user authentication and proxy connection settings that may be required to monitor some transactions. For additional details about these settings and instructions on how to edit them, see Viewing and editing individual Web transaction details.
Response time alarm firing conditions. These settings control alarm generation. The default values are set in the Foglight registry:
Synthetic_Transaction_MET_Warning: Controls the global default value of the threshold for generating Warning alarms.
WebMonitor_Transaction_Response_Time_Critical: Controls the global default value of the threshold for generating Critical alarms.
WebMonitor_Transaction_Response_Time_Fatal: Controls the global default value of the threshold for generating Fatal alarms.

For additional details about these settings and instructions on how to edit them, see Viewing and editing individual Web transaction details.

Table 31. Basic Information view

The Transaction Detail view provides details about the selected transaction. Use it to find out the URL of the monitored Web site, the type of monitored content, the locations from which this Web site is monitored, and to review and adjust some advanced settings, if needed.

1
On the Administration Home page, click Manage Web Monitor Transactions.
The Transaction Detail view appears in the display area.

This view is made up of the following embedded views:

Shows the URL of the monitored Web site. It also indicates whether the agent should retrieve the page header only, and the expected content.

Expected Content: If content validation is enabled for the agent instance that monitors this URL, and the expected content type is HTML-based, this is indicated in this column. Also, a text string could be used such as “laptop” and type laptop into this column. In case the monitoring agent detects binary content or the text string at this address, the validation fails and the agent logs an error message. If this column is empty, that means the agent is not required to perform content validation.
Content validation can be enabled using the URL List secondary agent properties. For more information, see Settings.
Unexpected Content: If unexpected content validation is enabled for the agent instance that monitors this URL, and the unexpected content type is HTML-based, this is indicated in this column. Also, a text string could be used such as “laptop” and type laptop into this column. In case the monitoring agent detects binary content or the text string at this address, the validation fails and the agent logs an error message. If this column is empty, that means the agent is not required to perform unexpected content validation.
Unexpected Content validation can be enabled using the URL List secondary agent properties. For more information, see Settings.
Get Page Header Only. Indicates whether the monitoring agents collect only the page header.
Display Name. The display name of the transaction.
URL. The URL of the monitored Web site.

Lists one or more hosts on which the monitoring Web Monitor Agent and Foglight Agent Manager are installed.

Agent Name. The name of the Web Monitor Agent instance that gathers information about this transaction.
Location (FglAM). The name of the host on which the Agent Manager is installed.

Displays thresholds for alarm generation and any authentication settings, if they exist.

Authentication and proxy settings. These settings specify user authentication and proxy connection settings that may be required to monitor some transactions. For additional details about these settings and instructions on how to edit them, see Viewing and editing individual Web transaction details.
Response time alarm firing conditions. These settings control alarm generation. The default values are set in the Foglight registry:
Synthetic_Transaction_MET_Warning: Controls the global default value of the threshold for generating Warning alarms.
WebMonitor_Transaction_Response_Time_Critical: Controls the global default value of the threshold for generating Critical alarms.
WebMonitor_Transaction_Response_Time_Fatal: Controls the global default value of the threshold for generating Fatal alarms.

For additional details about these settings and instructions on how to edit them, see Viewing and editing individual Web transaction details.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択