Foglight for Infrastructure 5.9.2 - Infrastructure Utilities User Guide

Monitoring URLs that require a client certificate

Monitoring URLs that require client authentication requires some additional configuration. To successfully access these URLs with the Web Monitoring Agent and collect response time metrics, you must import the certificates for URLs.

NOTE: Ensure you have read and write rights for the following path: {fglam_home}/state/default/certificates NOTE: The tool for importing the client authentication depends on the JRE being used. Ensure that the JRE exists in one of the following locations: • When Fglam is external, the JRE should be found in {fglam_home}. • When the Fglam is embedded, the JRE should be found in {foglight_home}. • When the JRE is neither in {fglam_home} nor {foglight_home}, the path to the JRE should be found in the environment variable JAVA_HOME.

The Microsoft® Internet Information Server (IIS) by default enables the TLSv1 and disables the TLSv1.2 protocols. The JDK 1.7+ (included in Foglight Agent Manager 5.7.4 and later) by default handles handshake with TLSv1.2. If the server side and the client side do not include the same supported TLS version, this causes the HTTPs request to fail. The following workarounds are available in this case:

Exploring your collection of monitored Web sites

The Transaction Management dashboard displays a list of monitored Web sites and the locations from which they are monitored. One Web site can be monitored from one or more locations. This can give you a good understanding of the complexity of your monitored environment and the locations from which a specific Web site is monitored.

For complete details about the data appearing on this dashboard, see the Transaction Management table.

For more information, see the following topics:

Expanding your collection of monitored sites

The Transaction Management dashboard allows you to add URLs to the existing collections of monitored sites. Adding a new URL causes the Web Monitor Agent to start collecting information about that URL in the next collection period.

This assumes that you already have the agent package deployed to the Foglight Agent Manager host, and one or more active Web Monitor Agent instances in place. For complete information on how to deploy an agent package, and to create and activate agent instances, see the Administration and Configuration Help.

TIP: The Web Monitor Agent validates the URL address in the background, to prevent you from adding the dupicate URL address that has been monitored.

NOTE: It is not allowed to associate multiple URL addresses with a same transaction.

3	To add more URLs to the list, click Add, and populate the row that appears. To remove a row from the list, click .

TIP: The Web Monitor Agent requires a running instance of the Foglight Agent Manager on the same host. For details on installing and running the Agent Manager, see the Agent Manager Guide.

TIP: When finished, you can return to this dialog box using the breadcrumb trail.

Removing Web sites from the existing collection

The Transaction Management dashboard allows you to remove URLs from the existing collection of monitored sites. Removing a URL from the list causes the Web Monitor Agent to stop collecting Web site transaction information about that URL. The data collected from a removed URL is kept in the Foglight database in accordance with the existing persistence settings. For more information, refer to the Administration and Configuration Help.