Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - User 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 Monitoring the user experience Customizing reports The alarm system Integrating the appliance SOAP-based web services

Server-side monitoring

The Cartridge for FxM, with Foglight 5, gives you insight on the back-end performance of the servers monitored by Foglight Experience Monitor.

Load balancing refers to the technique of distributing processing and communications activity evenly across a computer network, so that no single device is overwhelmed. This is especially important when it is difficult to predict the number of requests a network’s servers receives.

Busy web sites typically employ two or more web servers in a load-balancing scheme: if one server’s ability to handle an increasing number of requests becomes strained, requests are forwarded to another server with more capacity. Load balancing can also refer to the communications channels themselves.

Foglight Experience Monitor provides the Processing Load Percentage metric in its Server metric category. This metric shows the percentage of processing load attributed to a specific server. In an optimal load-balanced environment, this metric should be 1/N, where N is the number of servers in the server farm. For example, if there are eight servers in a server farm the processing load on each server should be approximately 12.5%.

The Cartridge for FxM provides Rules and Views for this metric in the Foglight Console that allow you to constantly monitor the effectiveness of your load balancing implementation. The Foglight Experience Monitor_Server_Load rule allows you to define which actions Foglight takes when the Processing Load Percentage metric rises above thresholds that you define. This rule allows you to establish guidelines for expected behavior of your load balanced server farm, and verify that your architecture is working as designed.

By logging into Foglight Experience Monitor you can examine all metrics for the server in question and determine whether other factors may be accounting for unbalanced loads.

Web servers that are generating HTTP error response codes (500-504) can indicate the presence of serious problems that require immediate attention as described in the following table.

Internal Server Error
(500)

The server encountered an error that prevented it from fulfilling a request.

Configuration or hardware problems with the server

Not Implemented
(501)

The client made a request that is beyond the server’s capabilities.

The web server software may need to be upgraded or the client is using a non-standard application

Bad Gateway
(502)

The server, while acting as a proxy or gateway, received an invalid response from an upstream server

Poor IP communication between servers in the network

Service Unavailable
(503)

The server is temporarily unable to service the request

Administrator error that leaves the server improperly configured or in an unavailable state

Gateway Timeout
(504)

The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server

Poor IP communication between servers in the network

HTTP Version Not Supported
(505)

The server cannot support the version of HTTP requested

The web server software may need to be upgraded or may be improperly configured

To provide a measure of the frequency with which your servers are generating these errors, Foglight Experience Monitor provides the Success Ratio (with Server Errors) metric in the Server category. This metric shows the ratio of successful requests, to the total number of requests with HTTP server errors (code 5XX) that indicate a response failure. In the Foglight Experience Monitor console, this ratio is represented as a percentage, with 100% indicating that every request has been serviced successfully.

The Cartridge for FxM provides Rules and Views for this metric in Foglight that allows you to constantly monitor the health of your servers. The Foglight Experience Monitor_Srv_Success_Ratio rule allows you to define what actions Foglight takes while it monitors this metric (including email notifications).

If Foglight notifies administrators that there exist server issues, they can then log in to the application and determine which error codes are being generated, and examine other metrics regarding the web server in question.

NOTE: For the Cartridge for FxM installation information, as well as product version requirements, see the End User Monitoring Installation and Configuration Guide and the Cartridge for FxM Release Notes.

Integrating with Foglight Experience Viewer

The Foglight Experience Viewer is an appliance-based solution that gives organizations the ability to capture, store and play back web user sessions in real time for immediate insight into web application failures. Foglight Experience Viewer allows you to record, store and replay individual user sessions in any browser platform to see the exact text, images and pages its web systems served to end users.

When viewing Foglight Experience Monitor’s User Sessions Log, if the Foglight Experience Viewer and the Foglight Experience Monitor has been integrated, you have the added option to view the user session from an Foglight Experience Viewer perspective. See Using the User Sessions Log for more information.

NOTE: For information on integrating Foglight Experience Viewer with Foglight Experience Monitor, see the Foglight Experience Monitor Installation and Administration Guide.

 

SOAP-based web services

This section describes web services architecture and how SOAP messages are monitored by the appliance.

About web services

Web services are web-based applications that are integrated using the XML, SOAP, WSDL, and UDDI open standards over an Internet protocol backbone. The roles played by different web services within the same application framework may differ in size and scale, but when considered as a whole, they collectively serve a purpose traditionally fulfilled by a single web application.

There are certain key differences between web services, and the web application model, as specified in the following table.

A web application typically performs its role as a single entity.

Web services perform specific functions that allow application tasks to be distributed across networks.

End users connect to web applications.

Web services connect to other web services.

Web applications reside on a server, and are accessed with a web browser on the client side.

Web services are available from different locations, and can be accessed by different clients on different platforms.

Web applications make use of local resources.

Much like web services themselves, the resources they use can be found in both local and remote locations.

Based on these differences, web services are efficient, portable ways of sharing information. However, despite the differences, web services still make use of the same infrastructure that web applications do. As such, when accessing web services, your end-users are subject to the same issues that they may face when dealing with your web applications (for example, excessively long processing times).

For more details, refer to these topics:

Related Documents