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

Monitoring Microsoft Office SharePoint Servers

Microsoft® Office SharePoint® Server is used to facilitate a collaborative environment for SharePoint sites. You can enable the appliance to monitor requests sent to and responses received from the server and report statistics about these user activities.

Figure 79. SharePoint page

Configuring the SharePoint® options controls which URLs are treated as SharePoint requests. Hits with URLs that match any regular expressions (configured on the SharePoint page) are processed by the appliance to reconstruct the user's actions based on the sequence of SharePoint URLs and then determines the performance of these user actions. These SharePoint user actions display in the Page category.

For more information, see these topics:

Configuring SharePoint monitoring

Configuring SharePoint® monitoring involves defining a set of regular expressions and installing a set of pre-defined configuration settings.

Navigate to the Configuring > Applications > SharePoint.
Type a Perl regular expression in the box. For example, if you know where the SharePoint applications are located (all components are found under, type the expression (in this case,*).
Alternatively, if you don’t know where application components are located, click the Pick a Directory link to display a window that lists the directories in use on your site.
Optionally, select the Enable FxV sessionizing by IP address to override the default behavior of not sessionizing hits for Foglight Experience Viewer that do not contain any session ids. Enabling this option means that user sessions will appear in Foglight Experience Viewer based on the client IP address for each hit.
Only enable the Enable FxV sessionizing by IP address check box when monitoring intranet SharePoint sites where there are no cookies available to serve as a session identifier. If you are not sure if cookies are available, navigate to the Session Identification Variable list in the User Sessions page (Configure > Monitoring > User Sessions) and run the auto-discover variables option.
In the SharePoint Configuration Settings section, click the Apply button to install pre-defined configuration settings.

Configuring how URLs display

When SharePoint® monitoring is configured, the appliance records when information is transmitted to and from the server. For example, when a user publishes content to a SharePoint server, in a form (POST parameter), the appliance monitors the URLs that contain this activity. You can define how the URLs display in the web console using several options. For example, you can display request methods (POST, GET) in URLs by setting the Show HTTP request methods in URL option using the Advanced Options on the URL page. For more information, see Advanced URL options.

By default, SharePoint encodes its URLs in a manner that makes their URLs difficult to read. In the web console, you can decide whether to display URLs as they are originally encoded or decoded in a manner that makes them more readable. For information about displaying URLs in the web console, see Encoded and decoded URLs.

When SharePoint monitoring is first enabled, the appliance automatically populates a list of default variable rules. You can customize a variable rule defining how the system will transform the query segments of URLs. For more information, see Managing variable rules.

When a document is edited on a SharePoint site, its name is stored on the server and by default, the appliance displays this document name in the URL displayed in the web console. If you do not want to display this information in URLs, you can configure whether these document names are displayed by changing the variable rules. For more information, see Managing variable rules.

SharePoint and SOAP

If you are monitoring SOAP based web services you can view SOAP Operations for SharePoint®, on the All Metrics View > User Sessions. For many of the user actions performed in SharePoint, a SOAP operation call is made by the browser. Examples of user actions that result in SOAP operations are document checkout and check in. These SOAP operations are often intermixed with non-SOAP requests. The SharePoint analysis module within the appliance will combine these SOAP and non-SOAP requests to form a page. The metrics for this page display in the Page category. The display of SOAP operations names is handled differently from non-SOAP names. Regular hits display as a standard URL, and might include additional form variables appended to the URL. For example:

A SOAP operation however will show the soap action and request method.

Additionally, there are several more options for controlling how the SOAP operation name is constructed, such as including the adaptor in SOAP Operations, including server display names in SOAP Web Service and SOAP Operation names, and including the port in SOAP Web Services, SOAP Operation and SOAP Server names. To configure these options navigate to Configure > Applications > SOAP page.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating