Foglight® 5.6.5 Monitoring Application Performance User and Reference Guide

© 2012 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc. The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: [email protected] Refer to our Web site for regional and international office information.

Trademarks Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please see http:// www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

Third Party Contributions Foglight contains some third party components. For a complete list, see the License Credits page in Foglight online help.

User and Reference Guide September 2012 Version 5.7

Monitoring Application Performance: User and Reference Guide

3

Table of Contents Introduction to this Guide..................................................................................................................................................5 About Quest Software, Inc. ............................................................................................................................................................. 5 Contacting Quest Software ..................................................................................................................................................... 5 Contacting Quest Support ....................................................................................................................................................... 6

Introducing Foglight APM..................................................................................................................................................7 Understanding the Foglight APM Implementation........................................................................................................................... 8 Foglight Requirements for APM Workflows............................................................................................................................. 8 Recommended Service Structures.......................................................................................................................................... 8 Service Level Agreements in Foglight APM ............................................................................................................................ 9

Using the SOC End User Tab ..........................................................................................................................................11 Pre-requisites for Monitoring End User Data in the SOC .............................................................................................................. 11 Configuring Trace Analysis for the SOC ............................................................................................................................... 12 Exploring the End User Tab .......................................................................................................................................................... 12 Real Users............................................................................................................................................................................. 14 Synthetics.............................................................................................................................................................................. 15 Configuring Display Options.................................................................................................................................................. 16

Understanding Geographical Perspectives ...................................................................................................................18 Creating a Map Agent ........................................................................................................................................................... 19 Viewing Real End User Activity ............................................................................................................................................. 22 Editing Map Agent Properties................................................................................................................................................ 25

Using the SOC for APM Triage ........................................................................................................................................27 Database Layer ............................................................................................................................................................................. 27 Application Layer........................................................................................................................................................................... 34 Virtual Machine.............................................................................................................................................................................. 40

Creating Custom Drag-and-Drop Dashboards...............................................................................................................46 Linking a Custom Dashboard to the Explore Icon for a Service............................................................................................ 55 Using Drag-and-Drop Dashboarding to Map Synthetic Transaction Locations and Infrastructure................................................ 57

Reference ..........................................................................................................................................................................65 Overview of APM Tiles .................................................................................................................................................................. 65 .NET Tile ....................................................................................................................................................................................... 67

Monitoring Application Performance: User and Reference Guide

4

Table of Contents

DB2 Tile ......................................................................................................................................................................................... 68 FTR (Synthetics) Tile ..................................................................................................................................................................... 68 Multi-Location Synthetics Tile ................................................................................................................................................ 68 Single-Location Synthetics Tile.............................................................................................................................................. 69 FxM (Real User) Tile...................................................................................................................................................................... 70 Host Tile......................................................................................................................................................................................... 71 Java Tile ........................................................................................................................................................................................ 72 JMX Tile......................................................................................................................................................................................... 73 OS Tile........................................................................................................................................................................................... 73 MQ Tile .......................................................................................................................................................................................... 76 Oracle Tile ..................................................................................................................................................................................... 77 SQL Server Tile ............................................................................................................................................................................. 78 Sybase Tile .................................................................................................................................................................................... 79 Virtual Hyper-V .............................................................................................................................................................................. 79 VMware Tile................................................................................................................................................................................... 80 Overview of Detail Views ............................................................................................................................................................... 81 Application Server Detail View....................................................................................................................................................... 82 Host Detail View ............................................................................................................................................................................ 83 Real User Performance Detail View .............................................................................................................................................. 83 Performance Tab ................................................................................................................................................................... 84 SLA Violators Tab.................................................................................................................................................................. 85 Synthetic Result Detail View.......................................................................................................................................................... 87 Synthetic User Performance Detail View....................................................................................................................................... 88 Virtual Machine Detail View ........................................................................................................................................................... 88 ESX Server Detail View ......................................................................................................................................................... 89

Index.................................................................................................................................................................................. 91

Introduction to this Guide This User and Reference Guide provides an overview of Application Performance Monitoring (APM) with the Foglight Cartridge for Application Operations. It includes conceptual information to help you envision an APM installation with Foglight and an overview of incident management workflows through the Service Operations Console (SOC). This guide is intended for Application Performance Managers who administer the overall design, implementation, and execution of the application performance monitoring strategy.

About Quest Software, Inc. Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and innovative IT management solutions that enable more than 100,000 global customers to save time and money across physical and virtual environments. Quest products solve complex IT challenges ranging from database management, data protection, identity and access management, monitoring, user workspace management to Windows management. For more information, visit www.quest.com.

Contacting Quest Software Email

[email protected]

Mail

Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA

Web site

www.quest.com

Refer to our Web site for regional and international office information.

Monitoring Application Performance: User and Reference Guide

6

Introduction to this Guide

Contacting Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at http://www.quest.com/support. From our Support Portal, you can do the following: • Retrieve thousands of solutions from our Knowledge Base • Download the latest releases and service packs • Create, update, and review Support cases View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures. The guide is available at: http://www.quest.com/ support.

1 Introducing Foglight APM Application Performance Monitoring (APM) refers to a set of capabilities or technologies used by IT staff to support the incident and problem management processes on multi-tier applications. A comprehensive APM implementation generally includes technology that includes the following capabilities: • End-user experience monitoring • Run-time application topology and execution path discovery, modeling, and display • Transaction profiling across the technology stack • Resource consumption and event monitoring within the discovered components • Analytics Quest’s Foglight APM solution supports all of these features, and provides the information to the right users at the right time through a set of role-oriented operational dashboards. Although there is no single organizational alignment or uniformly agreed upon set of titles for the actual practitioners of APM, the following role descriptions indicate the types of functions that typically interact with a Foglight APM installation: Foglight Administrator — responsible for configuring and managing Foglight, and for performing administrative tasks. Note

With the exception of Foglight Administrator, the roles described here are not roles defined in Foglight.

Application Performance Manager — responsible for the design, implementation, and execution of the APM strategy. Application Support — responsible for ensuring that application services are performing as expected. Identifies and triages service degradations or outages. Platform Specialist or Administrator — responsible for the operation of an individual application component (for example, a database, a host, an application server, or a web server). Receives and responds to Foglight alarms on their platform or domain. Application Architect — a senior escalation resource who is typically engaged by Application Support for assistance in locating the source of an application issue. Application Developer — responsible for the application code. Uses the Foglight transactional performance dashboards to gain understanding of the operational execution and performance of their code.

Monitoring Application Performance: User and Reference Guide

8

Chapter 1—Introducing Foglight APM

Understanding the Foglight APM Implementation Foglight supports a modular approach to APM that allows customers to implement as many or as few pieces of the APM solution as required. This guide is intended as a comprehensive overview of an end-to-end APM installation strategy, and therefore includes cross-domain views. Before you implement an APM strategy, it is important to perform proper requirement gathering, environment sizing, project planning, and scoping, just as you would with any other application. Quest Professional Services has developed a comprehensive strategy for APM implementation. You can review our process online at: http://www.quest.com/professional-services/performance-monitoring.aspx.

Foglight Requirements for APM Workflows In order to make the best use of this document, ensure that your Foglight installation meets the following requirements before beginning the workflows: • Install the Foglight Management Server and ensure it is running. For more information, see the Foglight Installation and Setup Guide set. • Install and configure the cartridges required to monitor application components (for example, operating system, application servers, databases). For more information, see the documentation included with the cartridges you are using. • Configure End-User transaction in Foglight Experience Monitor (FxM), Foglight Transaction Recorder (FTR), and Foglight Experience Viewer (FxV). For more information, see the documentation for these components. • Build services, either through Dependency Mapping or manually, and add the services to the Service Operations Console. For more information, see the topic “Creating and Maintaining Services” in the Managing Dependency Mapping User Guide.

Recommended Service Structures In Foglight, a service is any component or group of components that you want to monitor. If you have the Advanced Operator role, you can create services in the Service Builder dashboard to reflect the components in your monitored environment that are meaningful or interesting to your organization. For more information, see the topic “Monitoring Your Services” in the Foglight User Help. APM users typically organize their application services into three types: a Top Level Service, Tier Services, and one or more User Services. Each logical tier in the application should have its own service, which includes the application components (for example, databases, application servers, web servers), and the hosts that support the components. • The Top Level Service contains all elements in the application. It includes all child services and is added to the Service Operations Console (SOC) for Application Support. • The Tier Service is a logical representation of a service component. Foglight organizes data into default tiers, including User, Web, Application, Database, Host, and Agent. Over time, this Tier Service can track operational level agreements.

Monitoring Application Performance: User and Reference Guide

9

Chapter 1—Introducing Foglight APM

• The User Service contains all End-User artifacts, and organizes the transactions that support the application. For most users, a single End User service is sufficient. For example, a typical small web application might have the following service structure:

This is a high-level, or tier view of the service structure. This service includes four tiers: user, web, application, and database. This service can also be represented as:

This is the Application Infrastructure view. Here you can see the hosts contained in each tier: an Apache server (Web tier), two instances of WebLogic each hosted on a separate application server (App tier), and an Oracle database instance (DB tier). For more information, see “Using the SOC End User Tab” on page 11.

Service Level Agreements in Foglight APM Foglight automatically examines each service and establishes its availability and service level compliance. By default, a service is available and compliant with its Service Level Agreement (SLA) if it does not have any fatal alarms. Quest recommends the following general guidelines for APM: • Implement a top-level SLA based on end-user transactional data to allow the Application Support team to become familiar with SLA functions and the data available. For more information, see “Defining How the SLA is Calculated for Services” on page 10. • Defer the implementation of tier-based SLAs until your organization is ready to implement official operational level agreements for the infrastructure and component level teams.

Monitoring Application Performance: User and Reference Guide

10

Chapter 1—Introducing Foglight APM

Defining How the SLA is Calculated for Services When you create a new, or edit an existing, service, you can specify which components of the service are used to determine its overall availability. Note

This features requires Foglight Management Server 5.6.4 or later.

To define how the SLA is calculated: 1 On the Foglight navigation panel, under Dashboards, click Services > Service Builder. 2 To edit an existing service, click the edit icon Tip

for the tier.

To create a new service, click Add A New Category, and review the “Building a Service” topic in the Foglight User Help.

The Create Basic Information page of the Edit Service Wizard opens. 3 In the Objects used to determine the availability of this service section, select one of the

following options:

• All components added to this service. This is the default option. • Only components in selected tiers. Select this option to specify the individual tiers that you want to include. Click the check box beside the tier name to include it. 4 Click Finish.

2 Using the SOC End User Tab Service mechanisms in Foglight allow users to organize monitoring components into logical groups. A primary use case for this is for a multi-tier application where objects are organized into service tiers and visualized in the Service Operations Console (SOC). The Foglight Cartridge for Application Operations includes an extension to the SOC that adds visualization for end-user data in the context of application services in Foglight. This information appears on the End User tab of the SOC. Use this tab to quickly identify if any transactions are having issues, to determine the magnitude of impact on the user population, and to view preliminary information that can aid in troubleshooting, including geographic discrepancies and whether the performance problems are in the back end architecture or the client-side browser or network. The following specific end-user monitoring systems can be included: • FTR — Foglight Transaction Recorder. A Windows-based application that records and plays back synthetic Web transactions on regular intervals. • FxM — Foglight Experience Monitor. A network appliance that monitors Web transactions from real end users by tapping into the HTTP/HTTPS traffic stream as it transverses the internal network. • FxV — Foglight Experience Viewer. A transaction repository that stores and indexes every HTTP/HTTPS request/response pair captured from the network. FxV users can search, find, and analyze individual problematic transactions. Note

For complete information about FxM, FxV, and FTR, see their product documentation.

Pre-requisites for Monitoring End User Data in the SOC In order to make full use of the End User performance monitoring in the SOC, ensure that the following pre-requisites are met: • The End User Core Cartridge, the Cartridge for FxM, and the Cartridge for FxV have been installed on the Management Server. Important These cartridges must be installed to enable the End User tab in the SOC, regardless of whether you are collecting data from FxM and FxV.

Monitoring Application Performance: User and Reference Guide

12

Chapter 2—Using the SOC End User Tab

• 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 visualize it 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 the Cartridge 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 Help. 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.

Configuring Trace Analysis for the SOC In order to make the trace analysis functionality in the Cartridge 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 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 Performance Detail View” on page 83.

Exploring the End User Tab The End User tab displays a set of tiles representing transactional performance collected from FxM and/or FTR. The type and dynamics of transactional data dictate the number and type of tiles that appear on this tab, along with the Display Options you can configure (see “Configuring Display Options” on page 16).

Monitoring Application Performance: User and Reference Guide

13

Chapter 2—Using the SOC End User Tab

End user transactions are divided into: Real Users (FxM and FxV)

Synthetics (FTR)

There are a number of options for controlling how end user transactions are grouped together. For more information, see “Configuring Display Options” on page 16. Note

You must add a service containing end user objects (FTRResults and/or FxMApplicationResults) to the SOC in order for the End User tab to be visible.

To access the End User tab: 1 Log in to the Foglight browser interface. 2 On the navigation panel, under Homes, click Service Operations Console. 3 On the Service Operations Console, click the End User tab.

Monitoring Application Performance: User and Reference Guide

14

Chapter 2—Using the SOC End User Tab

Real Users When a service includes an FxMApplicationResults model object, it appears on the FxM (Real User) Tile, providing an at-a-glance view of that transaction’s performance. This tile displays the total number of active end users interacting with the monitored application, transaction front-end and back-end response times, and other metrics. These metrics are collected by FxM.

The Trace Analysis health status icon, located in the bottom right corner, shows that trace analysis metrics are tracking to their historical norms. Deviations from those norms indicate an anomaly. For more information about the information appearing on this tile, see “FxM (Real User) Tile” on page 70. Drill down on this tile (click the title bar) to open the Real User Performance Detail View. For more information about the metrics appearing on this view, see page 83.

Monitoring Application Performance: User and Reference Guide

15

Chapter 2—Using the SOC End User Tab

Synthetics When a service includes an FTRResults object, the End User tab displays one or more Synthetics tiles. These metrics are collected by Foglight Transaction Recorder (FTR). Depending on the number of tiles and the configured Display Options (see “Configuring Display Options” on page 16), a collection of Single-location Synthetic Layout or Multi-location Synthetics Layout tiles appear.

Single-location Synthetic Layout The Single-Location Synthetics Tile shows summarized data about a synthetic transaction executed from a single location. This type of layout shows the number of script executions and their execution times over the monitored period, along with other metrics. For more information about the metrics appearing on this tile, see page 69.

.

Drill down on this tile (click the title bar) to open the Synthetic Result Detail View. For more information about the metrics appearing on this view, see page 87.

Multi-location Synthetics Layout The Multi-Location Synthetics Tile shows summarized data about a synthetic transaction executed from multiple locations. This type of layout shows the total number of script execution locations and the numbers of locations for each alarm state (Normal, Warning, Critical, and Fatal). For more information about the metrics appearing on this tile, see page 68.

Drill down on this tile (click the title bar) to open the Synthetic User Performance Detail View. For more information about the metrics appearing on this view, see page 88.

Monitoring Application Performance: User and Reference Guide

16

Chapter 2—Using the SOC End User Tab

Drilling down on an individual location displays the Synthetic Result Detail View. For more information about the metrics appearing on this view, see page 87.

Configuring Display Options You can customize the layout of the End User tab by selecting the appropriate options in the Tile Display Options dialog box. Use these options to control the total number of tiles, the order in which they appear, and the roll up options for multiple FTR locations. Note

These settings apply on a per-user basis.

To configure display options: 1 On the Service Operations Console, on the End User tab, click Display Options.

The Tile Display Options dialog box opens.

Monitoring Application Performance: User and Reference Guide

17

Chapter 2—Using the SOC End User Tab

2 Configure these options, as required.

• The Enable Grouping option groups user tiles together by transaction name. By default, groups are sorted by their severity first, then by their name. This grouping is not affected by the Sort Order options. • The Show at most n tiles or groups setting determines the total number of tiles displayed. Synthetic transaction locations are first rolled up using the rollup criteria below. After that, the total number of tiles is truncated based on the maximum number of tiles that you specify. • You can roll up synthetic transactions locations into multi-location FTR (Synthetics) tiles based on these criteria, in the following order: • the maximum number of single-location Synthetics tiles, using the Rollup if there are more than n FTR tiles setting, and then • the maximum number of locations per script, using the When there are more than n location(s) for a script setting. • Use the Sort Order options to sort the tiles by either type (Real End Users first) or alarm severity (Sort by Alarm State). For example, you can configure the End User tab to display a maximum of ten tiles and sort them by the alarm state (highest severity first). 3 Click Save.

The Tile Display Options dialog box closes and the End User tab refreshes, reflecting the newly updated display options.

3 Understanding Geographical Perspectives The Geographical Perspective dashboard displays the real end user activity for the top 100 locations for a selected application component based on performance problems and errors, total traffic, response time, and other factors. It provides a list of performance-related measurements (such as, “Show locations with the most: Hits” or “Show locations with the highest: Hit Response Times”) that help you quickly and easily find patterns and problems that have geographical features.

Requirements for Using the Geographical Perspective Dashboard

• Foglight Experience Monitor (FxM) Appliance • FxM Agent configured and actively collecting data • Foglight Management Server, version 5.6.5 or later • Cartridge for FxM and End-User Core Cartridge installed on the Management Server • Cartridge for Application Operations, version 5.7 or later • FxM Map Agent deployed and configured

Foglight: Monitoring Application Performance Guide

19

Chapter 3—Understanding Geographical Perspectives

Creating a Map Agent To visualize real end user activity on the map, you must first configure a map agent. A map agent monitors a single FxM Appliance. It must be paired with an existing Foglight Real User Monitoring for Web agent to import geographical information into Foglight. You can only deploy one map agent per Foglight Real User Monitoring for Web agent instance. To create a map agent: 1 On the navigation panel, under Dashboards, click End User > Geographical Perspective. 2 The Geographical Perspective for ApplicationName dashboard opens in the display area. 3 Select an FxM Application from the FxM Application Result Table located at the bottom of

the navigation panel.

4 On the Geographical Perspective dashboard, click Create a map agent to import

geographic data. The Map Agent Setup wizard opens. The map agent requires an existing FxM agent that is active and collecting data from a Foglight Experience Monitor (FxM) Appliance.

Foglight: Monitoring Application Performance Guide

20

Chapter 3—Understanding Geographical Perspectives

Important If your FxM Appliance is at or near capacity, or if it is experiencing packet drops, it is recommended that you do not deploy the map agent. The map agent causes a small but measurable impact on the Appliance.

5 Verify that your FxM Appliance and agent are in a healthy state and click Next. 6 On the Advanced Agent Settings page, specify the agent settings.

Foglight: Monitoring Application Performance Guide

21

Chapter 3—Understanding Geographical Perspectives

a Select the granularity levels at which you want the map agent to import data. You can

select any combination of: Hourly, Daily, Weekly, or Monthly. By default, only Hourly and Daily are selected. b Specify the location where the map agent is deployed. By default, this is the same Agent

Manager that is hosting the FxM agent. Select an alternate location from the drop-down list if necessary. 7 Click Finish. 8 On the Geographical Perspectives for ApplicationName dashboard, click Import

geographical data to import the data for that application from FxM to Foglight. A message box opens.

9 Review the health of your Appliance. Note

If the load on your FxM Appliance is too high due to other geographic data collections that are currently running, you can deactivate those collections to reduce the load. Click the text link: Click here to deactivate or reactivate geographical data import for other applications.

10 Click OK. The map agent imports geographical data for the selected application.

The dashboard refreshes, displaying the relevant end user activity. Note

This process may take some time, depending on the amount of data being imported. If there is no data available for your selected time period, the aggregation interval and timeslice fields will appear empty.

If necessary, you can edit the map agent properties through the Agent Status dashboard. For more information, see “Editing Map Agent Properties” on page 25.

Foglight: Monitoring Application Performance Guide

22

Chapter 3—Understanding Geographical Perspectives

Viewing Real End User Activity The Geographical Perspective dashboard is divided into three panes. The left-hand pane contains lists of: available aggregation intervals, timeslices, and measurements. The center pane displays either a map, if the Map tab is selected, or a list of results in a tabular format, if the List tab is selected. The right-hand pane provides graphical results from the measurements, and the option to drill down for more information. Note

If you are using a version 5.6.4 Management Server, only the List tab is available. The Map tab requires Management Server 5.6.5 or later. If you are using Internet Explorer (IE) 8 or earlier, only the List tab is available.

To view real end user activity in a geographical perspective: 1 On the navigation panel, under Dashboards, click End User > Geographical Perspective. 2 Select an FxM application component from the FxM Application Result Table at the

bottom of the navigation panel. 3 Select a Measurement from the list to view the related transaction data. The map and right

pane update based on your selection. For example: select Show locations with the highest: Page Response Times.

The map updates to indicate the locations that are experiencing the highest average page response times in the selected timeslice. The right pane displays a chart of the page processing time for the entire application (all locations), and the top five locations are listed in a table below the graph and timeslice selector. Double-click anywhere on the map to zoom in on that location. You can also use the zoom tool in the map pane to zoom in or out. You can move the map in any direction by clicking and holding the left mouse button and dragging the cursor.

Foglight: Monitoring Application Performance Guide

23

Chapter 3—Understanding Geographical Perspectives

The fill-level of each location indicator on the map shows how close that location is to the maximum value in the current timeslice. In this example, Georgia has the highest response time, so its location indicator appears full. 4 Select a timeslice from the Timeslice list, or use the forward or back arrow buttons to step

through the available timeslices. Tip

The vertical blue bar on the graph indicates the currently selected timeslice.

5 Hover your cursor over a location indicator to open a quick view of metrics for that location.

6 Click an individual location indicator to view a graph of the average page response time for

that location in the right pane.

The Similar Locations list in the right pane updates to show locations that are ranked near the selected location in the current category.

Foglight: Monitoring Application Performance Guide

24

Chapter 3—Understanding Geographical Perspectives

that are also exhibiting the performance issues that the selected location is experiencing. Click any location name in the list to view the graph for that location. 7 Click Location Detail to drill down to detailed information for the selected location.

The Location Detail view provides a table of measurements in context that helps you understand how the selected location is behaving relative to other locations during the selected timeslice and aggregation period. Measurements for the selected location are sorted in order of severity. The value in the Highest Rank column indicates the highest ranking that the selected location attained at any point during the selected time range. The time range may span multiple timeslices. For example, at some time during the selected time range, New York had the highest page response time of all locations. Therefore, for the measurement Page Response Time, New York’s Highest Rank is 1 (first). The value in the Current Rank column indicates the selected location’s current ranking for the selected timeslice. This may or may not be the same as its highest rank, depending on when the peak value for the location occurred. In this example, New York is ranked second for the Current Rank for Page Response Time. That is, during the currently selected timeslice, New York has the second highest page response time. 8 Click any location’s name in either the Similar Locations list or the Top Ranked Location

column to open a detail view for that location for comparison. 9 To view the transaction data for the selected location in the FxM Appliance, click More

Details.

Foglight: Monitoring Application Performance Guide

25

Chapter 3—Understanding Geographical Perspectives

Editing Map Agent Properties After you have created a map agent, as described in “Creating a Map Agent” on page 19, you can edit its properties from the Agent Status dashboard. For example, you may want to change the available aggregation granularity, or change the scheduled collection interval. To edit map agent properties: 1 On the navigation panel, under Dashboards, click Administration > Agents > Agent

Status. 2 Select the map agent in the list and click Edit Properties. Tip

Map agents have the type MapFxMAgent and, by default, their names begin with Geo@.

3 Click Modify the private properties for this agent.

The settings become editable.

4 Ensure that the settings for the FxM Appliance database IP address and password match

those that the FxM agent is using to access the database. 5 The Associated FxM Agent Name must match the name of the FxM agent exactly. If this

box is blank, or if the value does not match that of the FxM agent, the map agent cannot access the FxM data to populate the geographical perspectives. 6 The Locations Per Measurement setting determines the number of locations from which

real end user activity is collected for display on the Geographical Perspective dashboard. By default, this value is 100.

Foglight: Monitoring Application Performance Guide

26

Chapter 3—Understanding Geographical Perspectives

7 The Maximum SQL Retries setting controls the number of times the map agent tries to

reconnect to an appliance that is unreachable before stopping data collection. The default is twelve attempts. 8 The five True/False settings allow you to specify the granularity of the data aggregation.

Click True for each of the FxM reporting intervals you want to make available: five minutes, hourly, daily, weekly, or monthly. By default, the five minute, weekly, and monthly intervals are disabled (set to False). Important If you have a large number of application components, using the five minute interval can cause a heavy load on the FxM Appliance, negatively impacting performance.

9 The FxM Application Collection list controls which of the available application

components the map agent collects data from. • To edit the default list, click Edit. Select or clear the check boxes for the applications and click Save Changes. or

• To create a new list without affecting the default list, click Clone. Type a name for the cloned list and click OK. To edit the cloned list, click Edit. Select or clear the check boxes for the applications and click Save Changes. 10 The Data Collection Scheduler setting controls how frequently the map agent checks the

FxM Appliance for data. By default, the collection interval is fifteen (15) minutes. Note

The agent imports all data for the selected granularities up to one hour old regardless of the collection interval.

To edit the default schedule, click Edit. To create a new schedule without affecting the default schedule, click Clone. 11 When you are finished setting the agent properties, click Save.

4 Using the SOC for APM Triage In order to support triage use cases, Foglight APM provides unique views that cover the intersection of transactions, application components, and infrastructure elements that define an application. The Service Operations Console is the primary dashboard for performing incident management workflows that terminate with a handoff to application, domain, or platform specialists. A user with the application support role for their organization uses the SOC to visually assess the current state of one or more applications. If transactional issues are present, they examine the state of transactions supported by a particular application, and assess the impact on the user population. They then visualize and evaluate the state of supporting applications and infrastructure to isolate the probable source of the issue. Finally, they engage the appropriate specialist. This chapter presents use cases that illustrate the types of issues you may encounter. Follow the walkthroughs for these use cases to gain a greater understanding of how Foglight simplifies the triage process. These walkthroughs demonstrate problems arising from the following sources: • Database Layer • Application Layer • Virtual Machine

Database Layer Begin all investigations by looking at the multi-application table at the top of the SOC dashboard. Here you can see an overview of the service or tier, including name, service level compliance, and user health status.

Only one service is shown in this example, but in a typical environment, there would be several. Tip

You can add and remove columns to customize the information that appears in this table by clicking the customizer icon to the right of the Search box.

Monitoring Application Performance: User and Reference Guide

28

Chapter 4—Using the SOC for APM Triage

To triage an application: 1 Review the Service Level Compliance and User columns of the table to locate the tier of the

service that is experiencing performance degradation. In this case, the User tier icon

indicates an issue for users.

The service level compliance icon indicates that the service has not yet violated the service level compliance policy in Foglight. However, if the issue persists, this icon may change to indicate a violation. 2 Review the End User tab to determine the impact on users.

End user tiles are grouped by transaction: MD1Patient (top row), MD1Physician (middle row), and MD1Admin (bottom row). They are also ordered by severity (that is, the users with the worst health status or most alarms appear at the top). Here you see that one transaction is having an issue, with both the real user tile and synthetic tiles reflecting an issue when accessing MD1Patient. The users accessing MD1Physician and MD1Admin are not experiencing any issues (their status is green across the board), which indicates that the issue is not affecting the whole application, only the MD1Patient transaction. The Trace Analysis health status ( ) icon on the MD1Patient Real User tile indicates that there is a problem somewhere in the trace analysis metrics. Foglight has also generated critical level alarms ( ) for all four MD1Patient transactions. Since all synthetic transactions are affected, this is not a location-specific issue. Synthetic transactions can be used as a benchmark for healthy performance. In this case, the fact that the synthetics are affected indicates that this is not a problem caused by a one-time error from a single user; it is a recurring or ongoing problem affecting all users.

Monitoring Application Performance: User and Reference Guide

29

Chapter 4—Using the SOC for APM Triage

3 Click the title bar of the affected Real Users tile to drill down for more information.

The Real User Performance detail view opens.

This detail view captures several key metrics in chart format. Consider the following: Metric

Key Insight

Response Time

Beginning at 09:35, users are experiencing a longer response time.

Page Requests

At 09:35, the number of page requests is slightly lower than earlier peak loads. This indicates that the problem is not due to a spike in user activity.

SLA/OLA Attainment

Also at 09:35, the Service Level Agreement (SLA) and Operating Level Agreement (OLA) are still being met, but the percentage is decreasing.

Front End / Back End

The time the transaction spent in the back end (that is, in the supporting architecture) has increased, and the problem appears to have started shortly before users were affected (that is, before 09:35).

Monitoring Application Performance: User and Reference Guide

30

Chapter 4—Using the SOC for APM Triage

Metric

Key Insight

Trace Analysis

The overall number of hits has decreased, as shown in the MD1Patient Hits chart. The number of users experiencing delay of more than seven seconds in their transaction execution has increased, as shown in the MD1Patient Hits Over 7 Seconds chart.

Note

Click the title bar of the MD1Patient Hits Over 7 Seconds chart to drill down into the individual sessions recorded by FxV. The FxV details allow you to see the Hit URLs and error messages, and to drill down into individual sessions, where you can step through a session to locate the error point. In this case, drilling down to the sessions shows that this is a content error issue. Some users are seeing error messages in their web browsers. This increases the priority of this issue.

This looks like a serious problem that is impacting many users, and the issue seems to be originating in the back end. Close this view by clicking the ‘x’ in the upper right corner. 4 Next, investigate the application topology to determine where in the supporting architecture

the problem originates. Click the Dependencies tab to view the application topology. Tip

Always work from left to right when triaging dependencies.

Overall, the infrastructure is in good health — all of the hosts have a green check mark, indicating that their status is normal. However, several of the tiers that contain platform and code components appear to have issues that must be investigated.

Monitoring Application Performance: User and Reference Guide

31

Chapter 4—Using the SOC for APM Triage

The Web tier has no issues. Moving to the right, you see that there is a warning on the Application (MedRecApp) tier. Tip

Hover the mouse pointer over a host icon to open a popup view of the application components.

5 Click the application tier title bar to drill down for more details.

The MedRecApp Details view opens. The banner section of the Summary tab displays the service level compliance for the tier. The lower portion of the view contains a tile for each application component, grouped by host.

Tip

For more information about the metrics displayed on views and tiles, see “Reference” on page 65.

6 Click the title bar of the application component tile to open the Application Details view.

Monitoring Application Performance: User and Reference Guide

32

Chapter 4—Using the SOC for APM Triage

On the Request Types tab, you see that POST/medrec/patient/viewPatient.action is the source of the warning. Select this request. Tip

Use the Search box to filter the list of requests. Type medrec/patient to include only those requests with that string in the name.

The response time for this request has increased and remains high. The Bottleneck Tier Name column lists the database tier as the source of the bottleneck. Note

There are additional columns that may be of interest that are hidden by default. To show them, click the customizer icon to the right of the Search box and select the columns you want to display.

The Execution Time chart at the bottom of the Application Details view (below the list of request types) indicates that the most time is spent in the database tier. It also shows that the time spent in the database tier began to increase at 09:30, which corresponds to the increase in the time spent in the back end that appeared in the Real User Performance view in step 3. This evidence all points to a problem in the database tier, which is where you should look next. Click the ‘x’ in the upper-right corner to close the Application Details view. Close the MedRecApp Details view as well. 7 On the Dependencies tab, click the title bar of the MedRecDB database tier to drill down for

more details. The details view for the database tier opens.

Monitoring Application Performance: User and Reference Guide

33

Chapter 4—Using the SOC for APM Triage

There is a critical alarm

on the application component tile for the Oracle database.

The Oracle Tile displays the top four session bottlenecks as color-coded bars. The larger the main color bar, the higher the percentage of resources were spent on that metric. The thin blue lines on the top of each bar indicate the range for the normal state. The thin green/ yellow/orange bar below the main color bar indicate the metric’s trend compared against itself. In this case, the database has Lock wait issues. Now that you have determined the most probable source, you can engage the database administrator to evaluate the problem. In this scenario, the database and application administrators should have been aware of the problems before the Application Performance Manager became involved. If the administrators were using Foglight, they would have received alarms generated and sent by Foglight.

Monitoring Application Performance: User and Reference Guide

34

Chapter 4—Using the SOC for APM Triage

Application Layer Begin all investigations by looking at the multi-application table at the top of the SOC dashboard. Here you can see an overview of the service or tier, including name, service level compliance, and user health status.

Tip

You can add and remove columns to customize the information that appears in this table by clicking the customizer icon to the right of the Search box.

To triage an application: 1 Review the Service Level Compliance and User columns of the table to locate the service

that is experiencing performance degradation. In this case, the User tier icon indicates an issue for users. The Service Level Compliance icon is green, indicating that the service level compliance policy in Foglight is being met. 2 Review the End User tab to determine the impact on users.

Monitoring Application Performance: User and Reference Guide

35

Chapter 4—Using the SOC for APM Triage

Tip

You can change the display options to roll-up single synthetic transaction locations into multi-location tiles, as shown above. For more information, see “Configuring Display Options” on page 16.

Here you see that Real Users are experiencing an issue when accessing MD1Physician, but the problem is only visible in the Trace Analysis. Synthetic transactions are not experiencing this problem. The Trace Analysis health status ( ) icon on the MD1Physician Real User tile indicates that there is a problem originating in a traced request. The OLA (Operating Level Agreement) and SLA (Service Level Agreement) values have degraded slightly. This suggests there are some outliers that are violating the compliance policy in Foglight. 3 Click the title bar of the affected Real User tile to drill down for more information.

The Real User Performance view opens.

Monitoring Application Performance: User and Reference Guide

36

Chapter 4—Using the SOC for APM Triage

This detail view captures several key metrics in chart format. Consider the following: Metric

Key Insight

Response Time

Starting at 06:30, the response time has increased slightly, but the increase is constant.

Page Requests

The number of page requests increased slightly before the response time increased, and has remained high. This indicates an increased load, not just a single spike in user activity.

SLA/OLA Attainment

The Service Level Agreement (SLA) and Operating Level Agreement (OLA) are still being met. The majority of users are not experiencing any problems.

Front End / Back End

The time spent in both the front end and back end (infrastructure) has increased, with the larger portion of the time being spent in the back end.

Monitoring Application Performance: User and Reference Guide

37

Chapter 4—Using the SOC for APM Triage

Metric

Key Insight

Trace Analysis

The MD1Physician Hits Over 7 Seconds chart shows the number of users experiencing a delay of more than seven seconds in their transaction execution has increased and remains high. This indicates that a handful of outlier transactions are severely impacting these users, but other users remain unaffected.

Tip

Click the MD1Physician Hits Over 7 Seconds chart to drill down to the user sessions in FxV.

The evidence from the metrics indicates that a small number of users are consistently experiencing problems. Close this view by clicking the ‘x’ in the upper right corner. Next, investigate the application topology to determine where in the supporting architecture the problem originates. 4 Click the Dependencies tab to view the application topology. Tip

Always work from left to right when triaging dependencies.

Overall, the infrastructure is in good health — all of the hosts have a green check mark, indicating that their status is normal. However, the tiers that contain platform and code components appear to have issues that must be investigated. 5 Click the MedRecApp application tier title bar to drill down for more details. Tip

If one of the hosts was experiencing an issue, you could click the host icon to drill down into a Host Detail View instead of looking at the tier view.

The MedRecApp Details view opens. The banner section of the Summary tab displays the service level compliance for the tier. The lower portion of the view contains a tile for each application component, grouped by host.

Monitoring Application Performance: User and Reference Guide

38

Chapter 4—Using the SOC for APM Triage

Here you can see that both nodes in the WebLogic Server cluster (MedRec1Server1 and MedRec1Server2) are experiencing a problem with requests. The hosts are unaffected. 6 Click the title bar of the MedRec1Server2 application component tile to open the Application

Details view.

Monitoring Application Performance: User and Reference Guide

39

Chapter 4—Using the SOC for APM Triage

On the Request Types tab, you see that POST/physician-web/physician/ createRecord.action is the source of the warning. Select this request. Tip

Use the Search box to filter the list of requests. Type physician to include only those requests with that string in the name.

The response time for this request has increased and remains high. The Bottleneck Tier Name column lists the MedRec1Cluster tier as the source of the bottleneck. The Execution Time chart below the list of request types also indicates that the most time is spent in the MedRec1Cluster of the application tier. This evidence points to a problem in the Java code, but requires further investigation. 7 Now that you have determined the probable source of the issue that is affecting users, you

can engage the domain expert to investigate further. The domain expert can use the Custom Applications (Java) dashboards to examine the request and traces in greater detail.

Monitoring Application Performance: User and Reference Guide

40

Chapter 4—Using the SOC for APM Triage

Virtual Machine Begin all investigations by looking at the multi-application table at the top of the SOC dashboard. Here you can see an overview of the service or tier, including name, service level compliance, and health status for selected tiers.

Tip

You can add and remove columns to customize the information that appears in this table by clicking the customizer icon to the right of the Search box.

To triage an application: 1 Review the Service Level Compliance, User, and App columns of the table.

In this case, the User tier icon indicates an issue for users. The Service Level Compliance icon is green, indicating that the service level compliance policy in Foglight is still being met. The App tier icon

indicates there are issues somewhere in the application tier as well.

2 Review the End User tab to determine the impact on users.

Here you can see that problems are occurring for both real users and synthetic transactions.

Monitoring Application Performance: User and Reference Guide

41

Chapter 4—Using the SOC for APM Triage

Real users for two of the three transaction types (MD1Patient and MD1Physician) are affected. The response time is increasing, and the OLA and SLA for these users are not being fully met. The Trace Analysis health icon indicates a problem somewhere in the traced requests. You can also see that the issue has begun to affect synthetic transactions. There are spikes present in the response time charts, where there had been previously steady lines. This points to outlier sessions experiencing issues. 3 Click the title bar of the MD1Physician Real User tile to drill down for more information.

The Real User Performance view opens.

The following trends are visible: • • • • •

Response time spiked sharply then levelled out, but is increasing again. The SLA is still being attained, but the OLA is no longer being fully met. There have been sharp changes in the page requests (user activity). The longest amount of time is being spent in the back end. The number of requests taking over seven seconds (MD1Physician Hits Over 7 Seconds) is increasing.

Close this view by clicking the ‘x’ in the upper right corner. Next, investigate the application topology to determine where in the supporting architecture the problem originates.

Monitoring Application Performance: User and Reference Guide

42

Chapter 4—Using the SOC for APM Triage

4 Click the Dependencies tab to view the application topology.

One of the hosts in the application tier is in a fatal condition. The rest of the infrastructure is in good health. 5 Click the title bar of the application tier to drill down for more information.

The first host in the tier (alvscjw143) and the application server on that host (MedRec1Server1) are both healthy.

Monitoring Application Performance: User and Reference Guide

43

Chapter 4—Using the SOC for APM Triage

The other host (alvscjw145) is in a fatal condition. The CPU Ready percentage on this host is very high, at 55.1%, indicating a CPU starvation issue, which appears to now be impacting the ability of the MedRec1Server2 application server to process its requests effectively. Tip

You could click the title bar of the MedRec1Server2 tile to drill down to the requests. In some cases, the requests can also provide more evidence to support your conclusions about the source of the issue.

6 Click the title bar of the host tile with the fatal alarm (alvscjw145) to drill down for details.

This detail view provides a summary of the host status with graphed data as well as the numerical values for metrics that are also present on the host tile. Here you can see the steep increase and high level of CPU Ready, and the sawtooth patterns of unstable Memory and CPU use.

Monitoring Application Performance: User and Reference Guide

44

Chapter 4—Using the SOC for APM Triage

7 Click the ESX tab to investigate the state of the host server and the virtualization layer.

Here you can see the top resource usage on the ESX host. The CPU Load is at 100% Used, and has been for some time. The Network I/O and Disk I/O both look healthy, but the Memory usage is also quite high at 87% of total. The table at the bottom of the view summarizes the most used resources and the VM that is consuming them. 8 Click the (more...) link for the Top CPU Utilization to compare the CPU usage of the hosts

on this server.

Monitoring Application Performance: User and Reference Guide

45

Chapter 4—Using the SOC for APM Triage

The bar chart makes it easy to see the VM (qscracsvrlc) that is currently consuming the most CPU resources. It has also been hogging the CPU resources over the entire period. 9 Now that you have determined the most likely source of the problem, you can engage the

VM administrator to further investigate and resolve the situation.

5 Creating Custom Drag-and-Drop Dashboards You can quickly and easily create a drag-and-drop dashboard to customize the view you want to use for triage with a specific application. This can be helpful when you want to: • Enhance or simplify your triage process for a specific application by exposing important components or notes for a specific application. • Visualize your end users and applications in a geographical distribution. For example, suppose you have a service that includes summarized data from a number of different locations, and you want to visualize this at-a-glance, relative to their geographic location. The procedures that follow walk you through creating such a dashboard, adding view elements for Real User and Synthetic transactions, and adding map components.

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

To create a custom dashboard: 1 Open the action panel on the right-hand side of the Foglight interface. 2 In the Other actions section of the action panel, click Create dashboard.

The Create Dashboard wizard opens.

3 Select Use All Data (the default setting) and click Next.

47

Monitoring Application Performance: User and Reference Guide

48

Chapter 5—Creating Custom Drag-and-Drop Dashboards

4 On the View Properties page, type a name for your new dashboard in the Name box. 5 Select the Share this dashboard and allow it to be included in other custom dashboards

check box. 6 Click Next.

7 On the Select Dashboard Layout page, select Fixed Size. 8 Click Finish. 9 The Add View wizard opens automatically. Click Cancel.

Next, add Real User data views to the dashboard.

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

To add Real User data to a custom dashboard: 1 On the action panel, click the Data tab. 2 In the Data list, expand Services > All Services.

3 Locate and expand the service you want to view (for example, Medical Records). 4 Expand the Real User Results and select the application component (for example, MD

Admin).

49

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

5 Drag and drop the application component onto the dashboard in the display area. A menu

opens.

6 Click Select a view. The Create View wizard opens. 7 On the Select a Template page, expand Application Performance Monitoring, and click

Application Component Thumbnail.

8 Click Finish. 9 Drag and drop another application component onto the dashboard (for example, MD

PatientVisit). 10 From the menu that opens, click Use previous selection.

The Real User thumbnail view appears on the dashboard.

50

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

Next, add a table containing Synthetic transaction results. To add Synthetic Transaction data to a custom dashboard. 1 From the Data list in the action panel, drag and drop Synthetic User Results onto the

dashboard display area. 2 From the menu that opens, select Create a table. The Create View wizard opens. 3 On the Select Properties page, select the Show All check box.

4 Select the following properties:

• Aggregate State Severity - AlarmSeverity • Name - String • availability - Metric

51

Monitoring Application Performance: User and Reference Guide

52

Chapter 5—Creating Custom Drag-and-Drop Dashboards

5 Click Next. 6 On the Configure Columns page, click in the Renderer box for the availability property and

select Sparkline from the list.

7 Optional — Click in the Label box for the Aggregate State Severity property and type State. 8 Optional — Click in the Label box for the availability property and type Availability. 9 Click Next. 10 The Table Preview page loads, displaying a preview of the table you have just configured.

If you are satisfied with the table’s appearance, click Finish. 11 On the action panel, click the General tab. 12 Click Edit page layout. 13 Reposition the data views by dragging and dropping them into place. 14 With the table view selected, you can enlarge the table by dragging the border to the desired

dimensions.

15 Click Done to lock the views in place and continue adding views.

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

To add Real User data in a Geographical Perspective to the dashboard: 1 On the action panel, click the Data tab. 2 Drag and drop a Real User result (for example, MD Admin) onto the dashboard. 3 From the menu that opens, click Select a view. 4 Expand End User > Geographical Perspective > Measurements. 5 Select Map of Users.

6 Click Finish. 7 Drag and drop another application component onto the dashboard (for example, MD

PatientVisit). 8 From the menu that opens, click Use previous selection. 9 On the action panel, click the General tab. 10 Click Edit page layout. 11 Reposition the data views by dragging and dropping them into place.

Finally, add views for application and database servers.

To add application component views to the dashboard: 1 On the action panel, click the Data tab.

53

Monitoring Application Performance: User and Reference Guide

54

Chapter 5—Creating Custom Drag-and-Drop Dashboards

2 Drag and drop an application server from the JavaEE Application Servers list (for

example, MedRec1Server1). 3 On the menu that opens, click Select a view. 4 Expand Application Performance Monitoring and click Application Component

Thumbnail.

5 Click Finish. 6 Drag and drop another application server onto the dashboard (for example,

MedRec1Server2). 7 On the menu that opens, click Use previous selection. 8 Reposition the thumbnail views as necessary. 9 Expand Oracle Instances and drag and drop a database server instance onto the dashboard

(for example, MEDRECDB-MEDREC1). 10 On the menu that opens, click Select a view.

Monitoring Application Performance: User and Reference Guide

55

Chapter 5—Creating Custom Drag-and-Drop Dashboards

11 Expand Application Performance Monitoring and click Application Component

Thumbnail. 12 Click Finish. 13 On the action panel, click the General tab. 14 On the dashboard, click Done.

The at-a-glance custom dashboard is now complete. You can link this dashboard to the Explore icon for the service it represents on the Service Operations Console.

Linking a Custom Dashboard to the Explore Icon for a Service After you have created the dashboard, you can add a link to it from the Explore icon for a service in the SOC. Note

This features requires Foglight Management Server 5.6.4 or later.

To link a custom dashboard to the SOC: 1 Open the Service Builder. Under Dashboards, click Services > Service Builder. 2 Locate the service in the Component list (for example, Medical Records). 3 Click the edit icon

for the tier. The Edit Service Wizard opens.

Monitoring Application Performance: User and Reference Guide

56

Chapter 5—Creating Custom Drag-and-Drop Dashboards

4 On the Create Basic Information page, click the text link beside Drilldown. A list opens.

5 Locate the custom dashboard to which you want to link. 6 Click the name of the dashboard.

The list closes, and the name appears on the Create Basic Information page. 7 Click Finish.

Now, return to the SOC and click the Explore icon

The custom dashboard opens.

for the service.

Monitoring Application Performance: User and Reference Guide

57

Chapter 5—Creating Custom Drag-and-Drop Dashboards

Using Drag-and-Drop Dashboarding to Map Synthetic Transaction Locations and Infrastructure You can quickly and easily create a drag-and-drop dashboard to visualize your services in a geographic distribution. This can be helpful when you want to: • Enhance or simplify your triage process for a specific application by exposing important components or notes for a specific application. • Overlay your application components on a custom architecture diagram. • Visualize your data centers in a geographical distribution. For example, suppose you have an end-user service that includes summarized data from a number of different locations, and you want to visualize this at-a-glance, relative to their geographic location. You can create a dashboard that includes a map as a background image, and place view elements (icons) that represent the status of your services onto the map. The procedures that follow walk you through creating such a dashboard, adding a background image, and adding view elements.

To create a custom dashboard: 1 With the Service Operations Console open in the display area, open the action panel on the

right-hand side. 2 In the Other actions section of the action panel, click Create dashboard.

Monitoring Application Performance: User and Reference Guide

58

Chapter 5—Creating Custom Drag-and-Drop Dashboards

The Create Dashboard wizard opens.

Tip

If you are using data from a single service, select Start with a service, as shown. If you want to use information from multiple services, select Use All Data. Review the procedure “To add Real User data to a custom dashboard:” on page 49 for more information.

3 Click Start with a service, then click Next. 4 On the Select a service page, select the service from the list and click Next.

Monitoring Application Performance: User and Reference Guide

59

Chapter 5—Creating Custom Drag-and-Drop Dashboards

5 On the View Properties page, type a name for your new dashboard in the Name box.

6 Select the Share this dashboard and allow it to be included in other custom dashboards

check box. 7 Click Next.

Monitoring Application Performance: User and Reference Guide

60

Chapter 5—Creating Custom Drag-and-Drop Dashboards

8 On the Select Dashboard Layout page, select Fixed Size. 9 Click Finish. 10 The Add View wizard opens automatically. Click Cancel.

To add a background image to the dashboard: 1 On the action panel, in the Actions section, click Properties. 2 A popup opens. Click Edit basic properties.

3 On the Edit View Properties dialog box, click the icon

select a map. The Select an Image dialog box opens.

beside Background Image to

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

4 Do one of the following:

• Type a valid URL for a map or architecture diagram that you want to upload. or

• Select from the images available within Foglight. Expand the Dashboard Development > Maps > Base Theme modules. Click the name of the map you want to use, for example: images/maps/north-america/united-states-800x600.png A preview of the map appears in the Preview pane on the right. 5 Click OK. The Select an Image dialog box closes. 6 On the Edit View Properties dialog box, click OK.

The map appears on the dashboard.

61

Monitoring Application Performance: User and Reference Guide Chapter 5—Creating Custom Drag-and-Drop Dashboards

To add views to the dashboard: 1 On the action panel, in the Actions section, click Add view.

The Add view dialog box opens. Use this page to add data views to the dashboard. 2 In the View Styles column on the right, click Select a View Template. 3 In the Input Data list on the left, expand the modules to locate the synthetic transaction

result you want to use. For example, FTR > FTR Sessions > MD Admin (New York) to display summarized data from a single location.

62

Monitoring Application Performance: User and Reference Guide

63

Chapter 5—Creating Custom Drag-and-Drop Dashboards

4 Click Next. 5 On the Select a Template page, in the Select a view list, click Application Performance

Monitoring > Application Component Mini.

Tip

To add a tile view instead of an icon, click Application Component Thumbnail. For more information about tile views, see “Reference” on page 65.

6 Click Finish. 7 On the General tab of the action panel, click Edit page layout to adjust the sizing and

placement of the icon on the map.

8 Click Done to stop editing the layout and lock the icons in place. Tip

After you have finished editing the layout, you can click an icon to open a summary view of the service.

9 To add more locations, click Add view on the action panel. 10 Repeat step 2 through step 8 for each view component that you want to add.

Monitoring Application Performance: User and Reference Guide

64

Chapter 5—Creating Custom Drag-and-Drop Dashboards

After you have created the dashboard, you can add a link to it from the Explore icon for a service in the SOC. For more information, see “Linking a Custom Dashboard to the Explore Icon for a Service” on page 55.

6 Reference This chapter contains reference information about views that are included with the Cartridge for Application Operations. Read this chapter to find out more details about the metrics appearing on these views. Foglight displays monitoring data in views that group, format, and display data. The main types are described below. Dashboards are top-level views that contain lower-level views. The dashboards supplied with Foglight, as well as those created by users, are accessible from the navigation panel. Lower-level views in Foglight can be added to dashboards or can be accessed by drilling down from a dashboard. They receive and display data directly from the Management Server or from other views. Some views filter or select data that appears in other views in the same dashboard. Some are tree views with expandable nodes for selecting servers, applications, or data. The Cartridge for Application Operations includes the End User tab that allows you to monitor End User transactions. This tab contains a combination of tiles and can display drill down views when the appropriate options are selected. The Dependencies tab allows you to monitor your infrastructure with dependency mapping. This tab contains tile icons that you can click to access tiles and drill down views. This section describes these tiles and views in more detail.

Overview of APM Tiles The Cartridge for Application Operations includes a tile view for each monitored domain. In order to populate these tiles, the appropriate Foglight cartridge must be installed and configured to monitor the domain or component. For example, in order to view the Java Tile, you must install the Cartridge for Java EE Technologies, and configure it to monitor at least one Java application server. The metrics displayed are specific to the domain, but the overall look and functionality of the tiles are common. For example, the following tile presents Java EE Technologies data:

Monitoring Application Performance: User and Reference Guide

66

Chapter 6—Reference

Title Bar

Alarm State

Graphical Summary

Component Icon

Key Metric

Additional Metrics

Alarm State Title Bar

The icon in the top left corner indicates the current state of alarms on the component. The title bar includes the component name, and the Explore icon . Click the icon to open a details view. For more information, see “Overview of Detail Views” on page 81.

Component Icon

Each component is represented by a unique icon that provides easy at-a-glance recognition of the domain.

Key Metric

The most important metric for the domain is displayed in the largest font, directly below the component icon, on the left side of the tile. Where no one metric takes precedence (for example, on the Host tile), the current Alarms are displayed instead.

Graphical Summary

The right side of the tile displays a graphical summary of key metrics for the component. For example, the Java tile includes a health breakdown for All Request Types, as in the example above. Other domains include a chart of the key metric for the time range selected (such as Response Time), an overall health history (color-coded bar), or a list of session bottlenecks.

Additional Metrics

Additional metrics that are key to the component appear at the bottom of the tile. Note

The value of these metrics is always current, unless the value appears in italics (for example, JVM Memory 122 MB). Italicized metrics reflect the period average instead of a current value.

Monitoring Application Performance: User and Reference Guide

67

Chapter 6—Reference

.NET Tile Use the .NET tile to gather performance information about the state of .NET transactions monitored by the Cartridge for Microsoft .NET. This tile displays the current top used external resources from the list below.

Description of the View Data displayed

External Resource Breakdown by Method Call Type. The current number of resources in each state (Normal , Warning , Critical , Fatal ), along with a color-coded bar. The colored portion of the bar indicates the number of resources in this state compared to the number of resources in the state that has the highest number of resources. The four top used external resources from the following list are displayed on the tile: • Internal. All method calls that are not related to any other call types in this list. • Database. Method calls related to databases. • Web Svc. Method calls related to web services. • Mail. Method calls related to sending mail. • Remoting. Method calls related to remoting client side resources. • WCF. Method calls related to WCF client side resources. • • • •

Load. The average load on the .NET system. Transaction. The current number of transactions per second. Exception. The current number of exceptions per second. Server. The .NET server name.

Monitoring Application Performance: User and Reference Guide

68

Chapter 6—Reference

DB2 Tile Use the DB2 tile to gather performance information about the state of DB2 transactions monitored by the Cartridge for IBM DB2 LUW.

Description of the View Data displayed

• Number of Connections. The sum of the average number of local and remote DB2 connections. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Response Time. A plot of the database response time. • Used Space. The average amount of database space used, as a percentage of the total space available. • Up Since. The date the database was last restarted. • CPU. The average CPU usage for all DB2 agents. • Memory. The average memory usage for all DB2 agents.

FTR (Synthetics) Tile The Multi-Location and Single-Location Synthetics Tiles tile show summarized data about user transactions recorded by FTR.

Multi-Location Synthetics Tile The Multi-Location Synthetics Tiles summarizes the performance of a synthetic transaction from multiple locations. Use this tile to gather performance information about the overall state of rolled up locations.

Monitoring Application Performance: User and Reference Guide

69

Chapter 6—Reference

Click the title bar to drill down to the Synthetic User Performance Detail View. Description of the View Data displayed

• Locations. The current number of agent locations. • Location Health Breakdown. The current number of locations in each state (Normal , Warning , Critical , Fatal ), along with a color-coded bar. The colored portion of the bar indicates the number of locations in this state compared to the number of locations in the state that has the highest number of locations. • Worst Location. The location of the Foglight Transaction Player Intelligent Agent with the worst period average success rates. • Best Location. The location of the Foglight Transaction Player Intelligent Agent with the best period average success rates. Note

Best and Worst Location are always displayed, even when all locations are 100% operational.

Single-Location Synthetics Tile The single-location Synthetics tile displays a summary of a synthetic transaction from a single location.

.

Click the title bar to drill down to the Synthetic Result Detail View. Description of the View Data displayed

• Executions. The number of times the script executed over the time range selected.

Monitoring Application Performance: User and Reference Guide

70

Chapter 6—Reference

Description of the View • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Response Time. The average script execution time over the time range selected. The red dashed line indicates the response time threshold. The background shading of the chart represents the status. Green shading indicates that the response time is currently good. • Availability. The period average percentage of time the service is available. • Met. The period average percentage of time the service met its required Service Level Agreement for the expected response time. • Latest. The most recent time the script executed. • Agent Status. An icon indicating the current state of the FTR agent: Normal Warning , Critical , or Fatal .

,

FxM (Real User) Tile The Real Users tile shows summarized data about real-user transactions measured by FxM.

Click the title bar to drill down to the Real User Performance Detail View. Description of the View Data displayed

• Current Sessions. The total number of active end users that are currently interacting with the monitored transaction. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State.

Monitoring Application Performance: User and Reference Guide

71

Chapter 6—Reference

Description of the View • Front End. The time from when the first byte of a transaction is sent from the end user’s browser until the time the last byte of that transaction was processed in the browser. This includes all Back End time, network time and browser processing time. Front End times are given over the time range period selected in the Service Operations Console. • Back End. The time from when the first byte of a transaction request is detected on the receiving Web server until the time the last byte of that transaction response was sent out of the Web server. This includes all Web server time, application server time, database time, and Web service call time spent behind the Web server needed to fulfill the transaction request. Back End times are given over the time range selected. • OLA. The current average percentage of pages that satisfy the Operation Level Agreement (OLA), as defined by the Page Processing Time threshold. • SLA. The current average percentage of pages that satisfy the Service Level Agreement (SLA), as defined by the Page End-to-End Time threshold. • Page Count. The average number of page download requests over the time range selected. • Trace Analysis. If any counters are selected in the Real User Performance Detail View, this indicator shows the highest severity alarm raised against one or more selected counters: Normal , Warning , Critical , or Fatal . If no counters are selected, this indicator appears disabled .

Host Tile The Host Tile summarizes the performance of a host system monitored by the Cartridge for Infrastructure. Use this tile to gather performance information about the state of host transactions.

Click the title bar to drill down to the Host Detail View. Description of the View Data displayed

• Alarms. A count of fatal, critical, and warning alarms on the host system. • CPU. An icon representing the health state of the CPU, and the CPU utilization expressed as a percentage of total available.

Monitoring Application Performance: User and Reference Guide

72

Chapter 6—Reference

Description of the View • Memory. An icon representing the health state of the memory, and the memory utilization expressed as a percentage of total available. • Network. An icon representing the health state of the network transactions, and the network utilization expressed as a percentage of total available. • Storage. An icon representing the health state of the storage (disk space), and the disk utilization expressed as a percentage of total available. • Operating System. The name of the operating system. • Primary IP. The primary IP address for the host system.

Java Tile The Java Tile summarizes the performance of a Java system monitored by the Cartridge for Java EE Technologies. Use this tile to gather performance information about the state of Java transactions.

If the application server includes Request Types in the selected time range, you can click the title bar to drill down to the Application Server Detail View if the application server has served requests in the selected time range. If there are no request types, clicking the title bar drills down to the server details. Description of the View Data displayed

• Calls. The number of calls served in the most recent collection interval. • Request Type Health Breakdown. The current number of request types in each state (Normal , Warning , Critical , Fatal ), along with a color-coded bar. The colored portion of the bar indicates the number of request types in this state compared to the number of request types in the state that has the highest number of request types. • Free Memory. The average JVM memory usage as a percentage of the total available. • Server. An icon indicating the overall health status of the server. • Server Type. The name and version information for the application server.

Monitoring Application Performance: User and Reference Guide

73

Chapter 6—Reference

JMX Tile The JMX Tile summarizes the performance of a JMX Server system monitored by the Cartridge for JMX. Use this tile to gather performance information about the state of JMX MBean transactions.

Description of the View Data displayed

• MBeans. The current average number of MBeans. • MBean Health Breakdown. The current number of MBeans in each state (Normal , Warning , Critical , Fatal ), along with a color-coded bar. The colored portion of the bar indicates the number of MBeans in this state compared to the number of MBeans in the state that has the highest number of MBeans. • Free Memory. The current free JVM memory, expressed as a percentage of the total allocated. • CPU Usage. The current average CPU usage. • Threads. The current number of threads. • GC Overhead. The period average garbage collection overhead expressed as a percentage for the selected time range.

OS Tile The OS tiles require the Cartridge for Operating Systems.

Server - Apache Monitor Tile The Apache Monitor Tile summarizes the performance of an Apache server. Use this tile to gather performance information about the state of server transactions.

Monitoring Application Performance: User and Reference Guide

74

Chapter 6—Reference

Description of the View Data displayed

• Alarms. A count of fatal, critical, and warning alarms on the host system. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Last Updated. The amount of time, in minutes, since the host information was updated. • Monitored Host. The name of the monitored host, and an icon representing the type of host.

Application Monitor Tile The Application Monitor Tile summarizes the performance of an application server. Use this tile to gather performance information about the state of server transactions.

Description of the View Data displayed

• Alarms. A count of fatal, critical, and warning alarms on the host system. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State.

Monitoring Application Performance: User and Reference Guide

75

Chapter 6—Reference

Description of the View • Last Updated. The amount of time, in minutes, since the host information was updated. • Monitored Host. The name of the monitored host, and an icon representing the type of host.

Log Filter Tile The Log Filter Tile summarizes the performance of an Alarm Filter agent. Use this tile to gather performance information about the state of server transactions.

Description of the View Data displayed

• Alarms. A count of fatal, critical, and warning alarms on the host system. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Last Updated. The amount of time, in minutes, since the host information was updated. • Monitored Host. The name of the monitored host, and an icon representing the type of host.

Web Monitor Tile The Web Monitor Tile summarizes the performance of a web server. Use this tile to gather performance information about the state of server transactions.

Monitoring Application Performance: User and Reference Guide

76

Chapter 6—Reference

Description of the View Data displayed

• Alarms. A count of fatal, critical, and warning alarms on the host system. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Last Updated. The amount of time, in minutes, since the host information was updated. • Monitored Host. The name of the monitored host, and an icon representing the type of host.

MQ Tile Use the MQ Tile to gather performance information about the state of queue transactions on an MQ Queue Manager monitored by the Cartridge for IBM WebSphere MQ Server.

Description of the View Data displayed

• Number of Connections. The average number of queue manager connections.

Monitoring Application Performance: User and Reference Guide

77

Chapter 6—Reference

Description of the View • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Enqueue/Dequeue. The message enqueue and dequeue rates. • Status. The average queue status for the time range: available, unavailable, or unknown. • Dead Letter Queue Depth. The average depth of the dead letter (undeliverable messages) queue.

Oracle Tile Use the Oracle Tile to gather performance information about the state of Oracle database transactions monitored by the Foglight for Oracle. This tile displays the current top used resources from the list below.

Description of the View Data displayed

• Sessions. The current average number of active sessions. • Top Session Bottlenecks. A breakdown of the health state of potential session bottleneck points by severity. The four top used resources from the list below are displayed on the tile. • IO • Network • Buffer • Lock • Latch • Redo • Cluster • CPU Usage • CPU Wait • Other

Monitoring Application Performance: User and Reference Guide

78

Chapter 6—Reference

Description of the View • Free Space. The amount of database storage space available, expressed as a percentage of the total available. • Up Since. The date the database was last restarted. • CPU. The average CPU usage for all Oracle agents. • Memory. The average memory usage for all Oracle agents.

SQL Server Tile Use the SQL Server Tile to gather performance information about the state of SQL Server database transactions monitored by Foglight for SQL Server. This tile displays the current top used resources from the list below.

Description of the View Data displayed

• Connections. The current average number of active connections. • Top Session Bottlenecks. A breakdown of the potential session bottleneck points. The four top used resources from the list below are displayed on the tile. • IO • Lock • Latch • Network • CPU • CPU Usage • Memory • CLR • Log • Remote Provider • Other • Used Space. The amount of database storage space used, expressed as a percentage of the total available. • Up Since. The date the database was last restarted. • CPU. The average CPU usage for all SQL Server agents. • Memory. The average memory usage for all SQL Server agents.

Monitoring Application Performance: User and Reference Guide

79

Chapter 6—Reference

Sybase Tile Use the Sybase Tile to gather performance information about the state of Sybase database transactions monitored by the Cartridge for Sybase.

Description of the View Data displayed

• Connections. The current average number of active connections. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Response Time. The time elapsed during database access, plotted over time. • Used Space. The amount of database storage space used, expressed as a percentage of the total available. • Up Since. The date the database was last restarted. • CPU. The average CPU usage for all Sybase agents. • Memory. The average memory usage for all Sybase agents.

Virtual Hyper-V Use the Virtual Hyper-V Tile to gather performance information about the state of virtual Hyper-V transactions monitored by the vFoglight Cartridge for Hyper-V.

Monitoring Application Performance: User and Reference Guide

80

Chapter 6—Reference

Description of the View Data displayed

• Alarms. A count of fatal, critical, and warning alarms on the virtual Hyper-V instance. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • CPU. The average CPU usage for the virtual system. • Network. The average network transfer rate for the virtual machine. • Storage. The average disk transfer rate for the virtual machine. • Operating System. The name of the operating system. • IP Address. The primary IP address for the virtual machine.

VMware Tile Use the VMware Tile to gather performance information about the state of a virtual machine monitored by the vFoglight Cartridge for VMware.

Click the title bar to drill down to the Virtual Machine Detail View. Description of the View Data displayed

• CPU Ready. The percentage of time that the virtual machine has spent waiting in the queue, ready to be scheduled on a CPU. An increase in this value indicates that the virtual machine is spending more time waiting and could be short on resources. • Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • CPU. The current amount of CPU resources used by the virtual machine, expressed as a percentage.

Monitoring Application Performance: User and Reference Guide

81

Chapter 6—Reference

Description of the View • Memory. The current amount of memory used by the virtual machine, expressed as a percentage. • Network. The current network transfer rate for the virtual machine. • Storage. The current disk transfer rate for the virtual machine. • Operating System. The name of the operating system. • IP Address. The primary IP address for the virtual machine.

Overview of Detail Views Detail views are drill down views accessible from some tile views. When you click the title bar of the VMware Tile, for example, the virtual machine detail view shown below opens.

Summary Banner

The Summary banner provides an overview of the selected component. This may include key statistics, or the service level compliance, depending on the component you are viewing. In the example above, the banner includes key metrics for the selected VM.

Monitoring Application Performance: User and Reference Guide

82

Chapter 6—Reference

Dependency Details

This tab provides dependency information. For details, see the Managing the Dependency Mapping User Guide.

Close-up Graph

This tab provides dependency information. For details, see the Managing the Dependency Mapping User Guide.

Component Tiles

The area below the banner includes a tile for each component that the selected component contains. For example, in the image above, the VM includes only one application server, MedRecServer, so one tile is displayed. For information about tile views, see “Overview of APM Tiles” on page 65.

More Details

Click this button to drill down to domain- or component-specific information and dashboards.

Application Server Detail View The Application Server detail view provides a list of Request Types, as well as Server Information for the selected application server.

The Request Types tab lists the following information for each request type: request name, response time, bottleneck location (based on the most time-consuming tier of a request), calls completed, calls incomplete, call exceptions, and number of traces. The chart shows the tier breakdown for the selected request. The information presented on the Server Info tab depends on the type of application server selected: JBoss, OracleAS, Tomcat, WebSphere, or WebLogic. Click Request Details to drill down for detailed information about a selected request.

Monitoring Application Performance: User and Reference Guide

83

Chapter 6—Reference

Host Detail View The Host detail view provides high-level host health, and tiles for any application components running on the selected host.

The banner shows host metrics if the host is monitored. If the host is not monitored, then: • If the host is a Federation Master, the banner shows a message indicating that the host is not monitored. • If the host is not part of a Federated environment, and the Cartridge for Infrastructure is installed, you are offered the option to configure host monitoring. For information, see the Managing the Infrastructure Cartridge User and Reference Guide. • If the host is not part of a Federated environment, and the Cartridge for Infrastructure is not installed, the banner shows message indicating that the Cartridge for Infrastructure is required for host monitoring.

Real User Performance Detail View The Real User Performance detail view provides detailed metrics for a single location real user transaction, including time spent in front-end and back-end, SLA and OLA attainment, page request volume, and more. To access this view, click the title bar of an FxM (Real User) Tile.

Monitoring Application Performance: User and Reference Guide

84

Chapter 6—Reference

Performance Tab The Performance tab displays charts of performance metrics and trace analysis information. From here, you can: • Click a Trace Analysis chart to drill down to the data in the Foglight Experience Viewer (FxV). • Click Edit Trace Analysis Associations to view and edit the state of the available counters that represent statistics for the monitored application. Select one or more of the available counters in the Edit Trace Analysis Associations dialog box to display their statistics in the Real User Performance detail view, under Trace Analysis.

Monitoring Application Performance: User and Reference Guide

85

Chapter 6—Reference

Note

This is only possible if your monitoring environment includes an FxV Appliance and the Cartridge for FxV is installed on the Management Server.

• Click View Recent URLs to drill down to the Foglight Experience Monitor (FxM) views and data. • Click View in End User Explorer to see the application statistics in the End User Explorer dashboard. For more information about this dashboard, see the Managing the Cartridge for FxM User and Reference Guide.

SLA Violators Tab The SLA Violators tab provides a map view that helps you determine if your SLA violations are geographic in nature.

Monitoring Application Performance: User and Reference Guide

86

Chapter 6—Reference

Note

This view is only available if the specific application has been configured for mapping, and you have configured a map agent. For more information, see “Creating a Map Agent” on page 19.

Hover the cursor over a location indicator to view a graph of the service level performance for that location.

Click a location indicator to open the Location Detail view for that location. For more information, see “Viewing Real End User Activity” on page 22. Click More Details on the SLA Violators tab to open the Geographical Perspective dashboard. For more information, see “Understanding Geographical Perspectives” on page 18.

Monitoring Application Performance: User and Reference Guide

87

Chapter 6—Reference

Synthetic Result Detail View The Synthetic Result detail view provides detailed metrics for a single location synthetic transaction, including health, response time, and a summary of executions.

Description of the View Data displayed

Health History Bar. The color-coded bar represents the alarm state of the monitored component over the time range selected in the Service Operations Console. The color of the bar changes depending on the alarm state. Red indicates a Fatal state, orange indicates Critical, yellow means Warning, and green is the Normal State. • Response Time. A chart of the response time for the transaction. The shaded background • Summary. Provides the total number of executions over the given time range, and the number of instructions for transaction. • Health. This icon indicates the transactions overall health status. • Alarms. Indicates how many of each type of alarm (Fatal, Critical, Warning) occurred in the selected time range.

From here, you can: • Click Synthetic Result Detail to see the script execution statistics in the End User Explorer dashboard. For more information about this dashboard, see the Foglight Transaction Player User and Reference Guide.

Monitoring Application Performance: User and Reference Guide

88

Chapter 6—Reference

Synthetic User Performance Detail View The Synthetic User Performance detail view provides a container view of results from all locations for a selected synthetic transaction. Each location is displayed in a single tile view that provides the same information as the Single-Location Synthetics Tile.

Click the title bar of any tile to drill down to the Synthetic Result Detail View for that location.

Virtual Machine Detail View The Virtual Machine (VM) detail view provides high-level performance metrics for both the currently selected VM and for its host ESX Server, and tiles for any application components running on the selected VM.

Monitoring Application Performance: User and Reference Guide

89

Chapter 6—Reference

From here, you can: • Click the ESX: tab to access the ESX Server Detail View. • Click More Details to drill down to a vmExplorer view. • Click the title bar of an application component tile to open the detail view for that component.

ESX Server Detail View This tab displays the CPU, Memory, Network, and Disk utilization for the from the perspective of the ESX server. The lower part of the tab displays the top resource consumers for this host. From this tab you can navigate to the vmExplorer dashboard by clicking More Details. This dashboard allows you to further investigate the performance of the selected ESX host.

Monitoring Application Performance: User and Reference Guide Chapter 6—Reference

From here, you can: • Click More Details to drill down to a vmExplorer view.

90

Monitoring Application Performance: User and Reference Guide

91

Index Symbols .NET. See DotNET

A about APM 7 Foglight APM 8 service level agreements 9 administrator, Foglight 7 agent name, FxM 25 APM 7, 8 overview of tiles 65 tiles 65 workflows, Foglight requirements for 8 application layer triage 34 Application Performance Monitoring. See APM application result table 19 Application Server Detail view 82 Request Types 82 Server Info 82 associated FxM agent name 25

C calculating SLA for services 10 configuring display options 16 configuring trace analysis 12 creating map agent 19

D dashboard, Geographical Perspectives 18 data collection scheduler 26 database layer use case 27 DB2 Tile 68 detail view Application Server 82 Host 83 overview 81 Real User Performance 83

Synthetic Result 87 Synthetic User Performance 88 Virtual Machine 88 DotNET Tile 67

E editing map agent properties 25 End User activity, viewing 22 Explorer, view in 85 End User tab configuring display options 16 exploring 12 real user transactions 14 synthetic transactions 15 End Users FTR 11 FxM 11 FxV 11

F Foglight administrator 7 APM 7, 8 Foglight Experience Monitor. See FxM. Foglight Experience Viewer. See FxV. Foglight Transaction Recorder. See FTR. FTR 11 (Synthetic) Tile 68 FxM 11 (Real User) Tile 70 FxM agent name 25 FxM application collection 26 FxM Application Result Table 19 FxV 11

G geographical perspectives

Monitoring Application Performance: User and Reference Guide

92

Index

requirements 18 geographical perspectives dashboard 18

H Host Detail View 83 Host Tile 71 how to, access End User tab 13

I introducing Foglight APM 7

J Java Tile 72 JMX Tile 73

P performance tab 84 pre-requisites for monitoring end user data 11 properties, map agent 25

R Real User FxM Tile 70 Performance Detail View 83 Performance tab 84 SLA Violators Tab 85 transactions 14 recommended service structures 8 Request Details 82 Request Types tab 82 requirements for geographical perspectives 18

L location detail 24 locations per measurement 25 Log Filter Tile 75

M map agent creating 19 editing properties 25 maximum SQL retries 26 monitoring end user data, pre-requisites for 11 MQ Tile 76 multi-location Synthetics tile 68 transaction layout 15

O Oracle Tile 77 OS Tiles 73 Apache Server 73 Application Monitor 74 Log Filter 75 Web Monitor 75 overview APM tiles 65 Detail views 81 service level agreements 9

S Server Info tab 82 Service Level Agreements. See SLA. service structures 8 single-location Synthetics tile 69 transaction layout 15 SLA 9, 10 calculating availability for services 10 SLA violators tab 85 SQL Server Tile 78 support 6 Sybase Tile 79 Synthetic multi-location layout 15, 68 multi-location Synthetics tile 68 Result Detail View 87 single-location layout 15, 69 single-location Synthetics tile 69 transactions 15 User Performance Detail View 88 Synthetic, FTR Tile 68

T technical support 6 tiles configuring display options 16 DB2 68 display options 16

Monitoring Application Performance: User and Reference Guide

93

Index

DotNET 67 FTR 68 FxM 70 Host 71 Java 72 JMX 73 MQ 76 Oracle 77 OS 73 overview 65 Real User 70 SQL Server 78 Sybase 79 Synthetic Users 68 Virtual Hyper-V 79 VMware 80 trace analysis, configuring for the SOC 12 Trace Analysis, editing trace analysis associations 84 transactions real user 14 synthetic 15 multi-location layout 15 single-location layout 15 triage application layer 34 database layer 27 virtual machine 40 triage, troubleshooting, APM, SOC, 27

U use cases application layer 34 database layer 27 virtual machine 40

V viewing end user activity 22 statistics in End User Explorer 85 views Apache Server Tile 73 Application Monitor Tile 74 DB2 Tile 68 DotNET Tile 67 FxM Tile 70 Host Tile 71

Java Tile 72 JMX Tile 73 Log Filter Tiles 75 MQ Tile 76 multi-location Synthetics tile 68 Oracle Tile 77 OS Tiles 73 overview 81 Real User Tile 70 single-location Synthetics tile 69 SQL Server Tile 78 Sybase Tile 79 Virtual Hyper-V Tile 79 VMware Tile 80 Virtual Hyper-V Tile 79 Virtual Machine Detail view 88 virtual machine triage 40 VMware Tile 80

W workflows for APM 8