Foglight for Application Operations 5.9.8

Defining how the SLA is calculated for services

When you create a new service, or edit an existing one, you can specify which components of the service are used to determine its overall availability.


	NOTE: This feature requires Foglight Management Server 5.6.4 or later.

For more information, see the topic “Building a new service > Adding a new category” in the Foglight User Guide.

Prerequisites for monitoring end user transactions in the SOC

In order to make full use of the End User performance monitoring in the SOC, ensure that the following prerequisites are met:

•

The End User Core Cartridge, the Cartridge for FxM, and the Cartridge for FxV are installed on the Management Server.


	IMPORTANT: These cartridges must be installed to enable the Transactions tab in the SOC, regardless of whether you are collecting data from FxM and FxV.

•

The Foglight Experience Monitor (FxM) and/or Foglight Transaction Recorder (FTR) are installed and configured to capture end user data and the appropriate End User cartridges are installed and configured to send end user data to Foglight and so that it can be viewed in the browser interface.

•

You must create a service that includes FTRResult and/or FxMApplicationResult objects. You can create and edit services using the service builders included with Foglight for Application Operations (that is, Build Service from Host Dependencies, Update Service from Dependency Data, or Build Services from Service Suggestions). For information about building services, see “Creating and maintaining services” in the Managing Dependency Mapping User Guide.

For Foglight cartridge installation instructions, see the Administration and Configuration Guide.


	IMPORTANT: If you choose to manually create a service using the Foglight Service Builder, you must manually identify and select topology objects. For more information, see “Manually building a service” in the Managing Dependency Mapping User Guide.

For more information, see Configuring trace analysis for the SOC.

Configuring trace analysis for the SOC

In order to make the trace analysis functionality in Foglight for Application Operations useful, you need to create hit filters in FxV.

A hit filter is a collection of match conditions and actions to be performed when a hit matches those conditions. Every hit filter is evaluated against each hit as it enters an FxV Archiver.

Hit filters can be used to detect and alert on any per-hit conditions, to mark interesting hits for later searching, and to manage hit storage. They can also be used to define events within transaction filters.

Hit filters are helpful because they provide a human context to the captured hits. For example, it is easier to search and alert on login attempts using a hit filter than to search and alert on login attempts by the server, path, and fields used by the web application.

Hit filters are very powerful in their ability to extract custom fields and update metrics. Using regular expressions, hit filters can pull data from fields, headers, cookies, or from page content.

In order to ensure that hit filters are coordinated with the FxMApplicationResult, use the FxMApplicationResult name as a filter criterion in FxV. For procedures describing how to configure hit filters in FxV, see “Configuring the hit analysis process” in the Foglight Experience Viewer User Guide.

For more information about trace analysis in the SOC, see Real User (FxM) Performance detail view.