Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - Installation and Administration Guide

Installing and configuring Multi-appliance clusters Configuring the appliance Specifying monitored web traffic Transforming monitored URLs Managing applications Foglight components and the appliance Using the console program Troubleshooting the appliance Appendix: Third party software Appendix: Dell PowerEdge system appliance

Managing servers on a Portal

When you access the Servers page on a portal, a section for each probe displays the servers it has been configured to monitor. You cannot configure the list of monitored servers on a portal. Instead, use the web console for the probe whose server list needs to be changed.

Configuring servers on a Probe

On a portal, from the Servers page, click Configure servers on the probe to launch the web console for the probe so you can modify the configuration.

Figure 48. Servers page

Using filters to exclude traffic

Using filters to exclude traffic

Filters consist of regular expressions that are used to exclude specific traffic from being recorded in Foglight Experience Monitor or Foglight Experience Viewer. You can define two types of filters:

•
URL Filters—exclude traffic by URL, User Agent, HTTP URLs, or HTTPS URLs. These type of filters allow you to exclude traffic from Foglight Experience Monitor, Foglight Experience Viewer, or both.
•
Subnet Filters—exclude traffic by specifying a subnet.

For more information, see these topics:

•
Defining URL filters
•
Testing URL filters
•
Defining subnet filters
To define URL filters:
1
Navigate to Configure > Monitoring > Filters.
The Filters page displays.
2
Click Add a URL Filter.
3
The Filter dialog box displays.
4
In the Filter box, enter the regular expression that will be matched against the incoming URL, or user agent string.
5
From the Type list, select one of the following options:
•
URL—excludes all URLs matching the filter.
•
User Agent—excludes crawler and synthetically generated traffic.
•
HTTP URL—excludes all HTTP URLs matching the filter.
•
HTTPS URL—excludes all HTTPS URLs matching the filter.
6
To exclude specific traffic from appearing in the appliance’s metrics lists, select the Exclude traffic matching this filter from analysis check box.
7
To exclude matching URLs from being transmitted to the Foglight Experience Viewer, select the Exclude traffic matching this filter from hits sent to Foglight Experience Viewer check box.
8
Click OK.
You are returned to the Filters page.
 
* 
NOTE: If the regular expression is not valid, an error message is displayed.

After adding a URL filter you can verify that any data matching the filter criteria will be excluded from the traffic by clicking the Test link to the right of the filter. The Filter Test window displays a list of all URLs or user agents that match the filter you have entered and will be excluded from the traffic sent to analysis or playback.

Figure 49. Filter test page

You can define subnet filters in order to exclude traffic originating from a specific subnet of IP addresses.

To define subnet filters:
1
Navigate to Configure > Monitoring > Filters.
The Filters page is displayed.
2
In the Add a Subnet Filter box, enter the regular expression that should be matched against the incoming the subnet mask. Click Add.
The filter is added to the Subnet Filters list.

Defining subnets

Subnets provide an independent network segment that consists of all devices for an IP address that have the same prefix. Using subnet masks, networks are divided into subnests based on security, performance and physical requirements.

The Subnets page lists the IP address and subnet mask pairs that the appliance monitors. Each subnet can be further defined by a geographical location which consists of a city, a region and a country location. Configuring a subnet by location provides you with more control over incoming traffic. When using the geographical location, traffic is categorized by location based on a subnet’s address.

Figure 50. Subnets page

For more information, see these topics:

•
Manually adding subnets
•
Automatically discovering subnets
•
Checking for overlapping subnets
•
Configuring a default subnet
•
Removing subnet definitions
•
Managing subnets on a Portal

Manually adding subnets

To manually add subnets:
1
Navigate to Configure > Monitoring > Subnets page and click Add a Subnet.
The Subnets > Edit page is displayed.
2
In the Name box, type a name you would like to appear in the metrics displayed in the web console for this subnet. The system provides a default display name for the subnet when it is first added based on the IP and subnet mask.
Selecting a Geographical Location
3
In the Geographical location box, click the Select.
The Resource List appears.
4
In the Type list, select city, region or country to define the subnet.
5
Narrow the list to a more specific set of pages by entering a search string in the Search box.
6
If you need to search by Perl regular expression, check the Interpret as a regular expression option.
You can use an asterisk (*) as a wild card to define a segment of the string that matches any combination of characters.
7
Click Go.
8
Select a location from the list.
You are returned to the Subnets > Edit page.
Selecting Masks
9
In the Subnet Masks section, type an IP address and subnet mask, separated by a “/” in the text box (for example, 192.168.1.0/24).
10
Click the Add button.
11
Click OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating