Chat now with support
Chat with Support

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 32. Monitoring Locations view

Transaction Detail view
Purpose

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.

How to get here
1
On the Administration Home page, click Manage Web Monitor Transactions.
2
On the Transaction Management dashboard that appears, in the Transaction Management table, click a transaction name.
The Transaction Detail view appears in the display area.
Description of embedded views

This view is made up of the following embedded views:

•
Basic Information
•
Monitoring Locations
•
Advanced Settings
 
Basic Information
 
Table 31. Basic Information view
Description

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

Data displayed
•
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.
Monitoring Locations
Table 32. Monitoring Locations view
Description

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.
Advanced Settings
Table 33. Advanced Settings view
Description

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 33. Advanced Settings view

Transaction Detail view
Purpose

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.

How to get here
1
On the Administration Home page, click Manage Web Monitor Transactions.
2
On the Transaction Management dashboard that appears, in the Transaction Management table, click a transaction name.
The Transaction Detail view appears in the display area.
Description of embedded views

This view is made up of the following embedded views:

•
Basic Information
•
Monitoring Locations
•
Advanced Settings
 
Basic Information
 
Table 31. Basic Information view
Description

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

Data displayed
•
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.
Monitoring Locations
Table 32. Monitoring Locations view
Description

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.
Advanced Settings
Table 33. Advanced Settings view
Description

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.

Transaction Management table

Purpose

The Transaction Management table displays a list of monitored Web sites and helps you understand which locations monitor them. It provides insight into the complexity of your monitored environment.

How to get here
•
On the Administration Home page, click Manage Web Monitor Transactions.
On the Transaction Management dashboard that appears, the Transaction Management table appears across the middle section of the display area.
 
 
Description of the view
Table 34. Transaction Management table
Data displayed
•
Active Agents. The number of active Web Monitor Agent instances that currently monitor this Web site out of the total number of agents configured to collect data from it. For example, 1/2 means that only one active agent currently monitors this transaction out of two configured agents.
•
Locations. The names of the hosts running the Web Monitor Agent instances that currently monitor this Web site.
•
Transaction Name. The transaction name associated with the monitored Web site.
•
Display Name. The display name of the transaction.
•
URL. The URL of the monitored Web site.
Where to go next

Drill down on:

•
Any row in this table. For more information, see Transaction Detail view.

Table 34. Transaction Management table

Transaction Management table
Purpose

The Transaction Management table displays a list of monitored Web sites and helps you understand which locations monitor them. It provides insight into the complexity of your monitored environment.

How to get here
•
On the Administration Home page, click Manage Web Monitor Transactions.
On the Transaction Management dashboard that appears, the Transaction Management table appears across the middle section of the display area.
 
 
Description of the view
Table 34. Transaction Management table
Data displayed
•
Active Agents. The number of active Web Monitor Agent instances that currently monitor this Web site out of the total number of agents configured to collect data from it. For example, 1/2 means that only one active agent currently monitors this transaction out of two configured agents.
•
Locations. The names of the hosts running the Web Monitor Agent instances that currently monitor this Web site.
•
Transaction Name. The transaction name associated with the monitored Web site.
•
Display Name. The display name of the transaction.
•
URL. The URL of the monitored Web site.
Where to go next

Drill down on:

•
Any row in this table. For more information, see Transaction Detail view.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating