Foglight Cartridge For FxV Reference Guide

Transcription

1 Foglight Cartridge For FxV

2 2008 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. 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 legal@quest.com Refer to our Web site for regional and international office information. Trademarks Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix L7 Enterprise, Akonix L7 Enforcer, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vanalyzer, vautomator, vcontrol, vconverter, vessentials, vfoglight, voptimizer, vranter PRO, vreplicator, Vintela, Virtual DBA, VizionCore, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners. Disclaimer 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. License Credits and Third Party Information To view license credit information, click the License Credits link on the Welcome to Foglight online help page. November 2008 Version 5.2.4

3 Table of Contents Introduction to this Guide...7 About Foglight... 8 About this Guide... 8 Foglight Documentation Suite... 8 Core Documentation Set... 9 Cartridge Documentation Sets Feedback on the Documentation Text Conventions About Quest Software, Inc Contacting Quest Software Contacting Quest Support Views...13 Overview of Views FxV System Health Summary Dashboard Server Summary Container View Collector Summary Container View Archiver Summary Container View FxV Capture Archivers Dashboard Capture Archiver Warning Summary View Hardware Container View Hit Processing Container View Archiver Health Container View Hit Analysis Container View Database Container View FxV Collectors Dashboard FxV Collector Health Views... 58

4 4 Foglight Cartridge for FxV FxV Storage Archivers Dashboard Hardware Container View Archiver Health Container View Storage Database Container View Rules FxM Collector Health Rules Collector Health Captured Incomplete Rule Collector Health Captured No Session ID Rule Collector Health Captured Timeout Rule Collector Health Discarded Malformed URL Rule Collector Health Discarded Shared Memory Full Rule Collector Health Discarded Total Rule Collector Health Upload Queue Utilization Rule Collector Health Discarded Upload Queue Full Rule Total Collector Health Captured Incomplete Rule Total Collector Health Captured No Session ID Rule Total Collector Health Captured Timeout Rule Total Collector Health Discarded Total Rule Total Collector Health Discarded Malformed URL Rule Total Collector Health Discarded Shared Memory Full Rule Total Collector Health Discarded Upload Queue Full Rule FxV Server Rules Server Health Database Connections Rule Server Health Database Size Rule Server Health Event History Trimming Rule Server Health Last Metric Updated Rule Server Health Value History Trimming Rule Server Hit Searches Slow Rule Server Hit Details Searches Slow Rule Server Replay Cache Reloaded Requests Rule Server Session Searches Slow Rule Server Transaction Searches Slow Rule FxV Capture Archiver Rules Capture Archiver Cached Items Rule... 94

5 Table of Contents 5 Capture Archiver Capture Rate Rule...94 Capture Archiver Clock Skew Rule...95 Capture Archiver Config Available Rule...95 Capture Archiver Content Keyword Indexing Rule...96 Capture Archiver Root FileSystem...96 Capture Archiver Variable FileSystem...97 Capture Archiver Temporary FileSystem...97 Capture Archiver Health Failures Rule...98 Capture Archiver Health Segments Dropped Rule...98 Capture Archiver Health Write Buffers Failed Rule Capture Archiver Metric Refresh Rule Capture Archiver Metrics Available Rule Capture Archiver Open Segment Aspects Rule Capture Archiver RAID Array Health Rule Capture Archiver Segments Closing Rule Capture Archiver Segments Copying Rule FxV Storage Archiver Rules Storage Archiver Clock Skew Rule Storage Archiver Config Available Rule Storage Archiver Metric Refresh Rule Storage Archiver Metrics Available Rule Storage Archiver RAID Array Health Rule Storage Archiver Root FileSystem Storage Archiver Variable FileSystem Storage Archiver Temporary FileSystem Appliance Group Rules Discarded Hits Rule Hit Summary Failed Rule Total Discarded Hits Rule Total Hit Summary Failed Rule Metric Rules StateMetric Outlier Detection Index...113

6 6 Foglight Cartridge for FxV

7 Introduction to this Guide This chapter provides information about what is contained in the. It also provides information about the Foglight documentation suite and Quest Software. This chapter contains the following sections: About Foglight...8 About this Guide...8 Foglight Documentation Suite...8 Text Conventions...11 About Quest Software, Inc...11

8 8 Foglight Cartridge for FxV About Foglight Foglight is an application management solution that reduces or eliminates service disruptions to unify IT and the business. Unlike other solutions, it provides a correlated, 360 degree view of your applications from end user to database and from service levels to infrastructure to source the root cause of every incident impacting your business and fix them quickly. Foglight correlates data from multiple perspectives into a single version of the truth to provide deep insight into the service relationships that exist between end users, the business and infrastructure components. Its unique adaptive technology rapidly adjusts to change for improved application performance and service levels, reduced operational cost and risk, and enhanced visibility for all stakeholders. About this Guide This provides configuration instructions, conceptual information and instructions on how to use the browser interface. This guide is intended for any user who wants to configure Foglight using the browser interface. The is organized as follows: Chapter 1, Views This chapter describes the predefined views included in the cartridge. Included in this chapter are view descriptions and their details. Chapter 2, Rules This chapter describes rules that monitor the health of your application server environment. Foglight Documentation Suite The Foglight documentation suite is made up of the core documentation set, plus the documentation set for each Foglight cartridge that you deploy. Documentation is provided in a combination of online help, PDF and HTML.

9 Introduction to this Guide 9 Foglight Documentation Suite Online Help: You can open the online help by selecting the Help tab from Foglight s action panel. PDF: The complete Foglight documentation set is available in PDF from SupportLink. The PDF documentation can also be found in the Documentation folder on the Foglight DVD. The following subset is available from the computer Foglight is installed on: Administration and Configuration Guide, User Guide, Command-Line, Web Component Guide and the Web Component Tutorial. In addition, the cartridges ship with PDF guides. To view the installed PDF guides, in Windows go to Start > Programs > Quest Software > Foglight > Documentation. The default location of the documentation after an installation is <foglight_home>/docs. Adobe Reader is required. HTML: Release Notes are provided in HTML. Core Documentation Set The core documentation set consists of the following files: Release Notes (HTML) Getting Started Guide (PDF) What s New Guide (PDF) System Requirements and Platform Support Guide (PDF) Installation and Setup Guide set (all in PDF format):

10 10 Foglight Cartridge for FxV Installation and Setup Guide Installing on Windows with an Embedded MySQL Database Installation and Setup Guide Installing on Windows with an External MySQL Database Installation and Setup Guide Installing on Windows with an External Oracle Database Installation and Setup Guide Installing on a UNIX System with an Embedded MySQL Database Installation and Setup Guide Installing on a UNIX System with an External MySQL Database Installation and Setup Guide Installing on a UNIX System with an External Oracle Database Administration and Configuration Guide (PDF and online help) Foglight User Guide (PDF and online help) Command-Line (PDF and online help) Transition Guide (PDF) Web Component Guide (PDF and online help) Web Component Tutorial (PDF and online help) Web Component Reference (online help) Cartridge Documentation Sets When you deploy a cartridge, the documentation set for the cartridge is installed. The online help for the cartridge is integrated automatically with the core Foglight help. When you open the help, the name of the cartridge is displayed in a top level entry within the table of contents. Some cartridges include additional PDF guides, which may be one or more of the following: a Getting Started Guide, an Installation Guide, a User Guide, and a. Feedback on the Documentation We are interested in receiving feedback from you about our documentation. For example, did you notice any errors in the documentation? Were any features undocumented? Do you have any suggestions on how we can improve the

11 Introduction to this Guide 11 Text Conventions documentation? All comments are welcome. Please submit your feedback to the following address: Please do not submit Technical Support related issues to this address. Text Conventions The following table summarizes how text styles are used in this guide: Convention Code Variables Interface Files, components, and documents Description Monospace text represents code, code objects, and commandline input. This includes: Java language source code and examples of file contents Classes, objects, methods, properties, constants, and events HTML documents, tags, and attributes Monospace-plus-italic text represents variable code or command-line objects that are replaced by an actual value or parameter. Bold text is used for interface options that you select (such as menu items) as well as keyboard commands. Italic text is used to highlight the following items: Pathnames, file names, and programs The names of other documents referenced in this guide About Quest Software, Inc. Quest Software, Inc., a leading enterprise systems management vendor, delivers innovative products that help organizations get more performance and productivity from their applications, databases, Windows infrastructure and virtual environments. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 90,000 customers worldwide meet higher expectations for enterprise IT. Quest provides customers with client management as well as server and

12 12 Foglight Cartridge for FxV desktop virtualization solutions through its subsidiaries, ScriptLogic and Vizioncore. Quest Software can be found in offices around the globe and at Contacting Quest Software Mail Web site Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA Refer to our web site for regional and international office information. Contacting Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at: From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: Support Guide.pdf.

13 1 Views Foglight ships with predefined views to help you monitor the end-user experience within the Foglight environment. This chapter contains the following sections: Overview of Views...14 FxV System Health Summary Dashboard...15 FxV Capture Archivers Dashboard...33 FxV Collectors Dashboard...57 FxV Storage Archivers Dashboard...61

14 14 Foglight Cartridge for FxV Overview of 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 do not receive data from other views. Dashboards usually contain a number of lower-level views. The dashboards supplied with Foglight, as well as those created by users, are available in 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 Foglight 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.

15 Views 15 FxV System Health Summary Dashboard FxV System Health Summary Dashboard The FxV System Health Summary dashboard provides summary views of the key appliance components: the Server, one or more Collectors, and one or more Archivers. Views in this section include: Server Summary Container View on page 16 Collector Summary Container View on page 21 Archiver Summary Container View on page 24

16 16 Foglight Cartridge for FxV Server Summary Container View The Server Summary view provides a complete health and status summary for the FxV Server. Use this view to ensure the Server is managing queries properly with the Archiver(s). If the Server appliance is not a dedicated machine and is also running an Archiver, the statistics provided in this view are still exclusively for the Server. Example Description of Embedded Views This view is made up of the following embedded views: JVM Memory Usage Database Statistics and Details Replay Cache Details Archiver Search Details

17 Views 17 FxV System Health Summary Dashboard JVM Memory Usage Description Data displayed This view displays memory usage information for the Java Virtual Machine on the Server. Peak. The peak memory usage within the displayed time frame. Current. The current JVM memory usage. Free. The amount of JVM memory that is currently available. This value should oscillate as normal garbage collection occurs. Allocated. The total amount of JVM memory that has been allocated on the Server. This amount can suddenly increase as the JVM automatically resizes the heap size to minimize garbage collections, and gradually decrease during Server inactivity. Note that these fluctuations correspondingly affect the other JVM memory usage statistics.

18 18 Foglight Cartridge for FxV Database Statistics and Details Description Data displayed This view displays information about the Server database and database performance. The Server database is used to store the metric history and system configuration. Size. The size of the Server database. Note that it is not very large since it only stores the metric history and system configuration; captured data is not stored in this database. Connections. The number of database connections currently open by the Server. The Server Sessions data at the top of the Server Summary container view displays the number of users currently logged in to the Server. The number of logins should help determine whether the number of open database connections is reasonable. Cache Size. The number of items that are currently stored in the Server cache. This metadata is used to build lists of field, cookie, and header names for use in the appliance web console. Event Trimming. The time taken to trim old alarm history data from the database. This action is performed as a background task every fifteen minutes. Metric Trimming. The time taken to trim old metric history data from the database. This action is performed as a background task every fifteen minutes. Metric Updates. The time taken to update the current value of all metrics that are being tracked by the Server. This action is performed as a background task every two minutes.

19 Views 19 FxV System Health Summary Dashboard Replay Cache Details Description Data displayed This view displays information about the Server replay cache. Session and transaction are cached in memory by the Server. Hits. The number of hits currently stored in the replay cache. You can expect this value to increase and decrease based on the number of request made by the Server. Requests. The number of sessions or transactions that have been requested from the Server for a given time frame. Sequences. The number of sessions or transactions currently stored in the replay cache. You can expect this value to increase or decrease based on the number of requests made by the Server. Sequences Requested. The number of times the Server attempted to find a session or transaction in the replay cache for a given time frame. Sequences Parsed. The number of sessions or transactions that required the content to be parsed. This typically occurs when the session or transaction contains at least one frameset. These sequences take longer to rewrite than sequences without frames. Missed. The number of times the Server was not able to find a requested session or transaction in the replay cache, forcing the Server to request the captured data from the Archiver(s). Reloaded. The number of times a requested session or transaction was found in the replay cache, but was cleared to reduce memory usage, forcing the Server to request the captured data from the Archiver(s).

20 20 Foglight Cartridge for FxV Archiver Search Details Description Data displayed This view displays the number of searches the Server made to the Archiver(s), indicating how many are considered to be slow. The Server searches the Archiver for hits, hit details, transactions and sessions. Search Hits. The number of hit searches the Server made to the Archiver(s) in a given time frame. The reported searches include those that took longer than ten seconds to complete. Search Hit Details. The number of searches for hit details that the Server made to the Archiver(s) in a given time frame. The reported hit detail search counts include those that took longer than fifteen seconds to complete. Search Transaction. The number of searches for transactions that the Server made to the Archiver(s) in a given time frame. The reported transaction search counts include those that took longer than ten seconds to complete. Search Sessions. The number of session searches that the Server made to the Archiver(s) in a given time frame. The reported session search counts include those that took longer than ten seconds to complete.

21 Views 21 FxV System Health Summary Dashboard Collector Summary Container View The Collector Summary container view provides information about how well the Collector is collecting traffic from the web server. Use this container view to ensure incoming hits are not being discarded. If hits are being dropped, various views describe the reasons why this is happening, helping you take corrective action. Example Description of Embedded Views This view is made up of the following embedded views: Incoming Hits Statistics Lost Hits Summary

22 22 Foglight Cartridge for FxV Incoming Hits Statistics Description Data displayed This view displays the ratio of captured hits to discarded hits, and breaks down the types of hits that may have flaws, but were captured regardless. Captured. The amount of incoming hits that were captured and sent to the Archiver(s) relative to hits that were discarded. Discarded. The amount of incoming hits that were discarded, relative to those that were captured and sent to the Archiver(s). Normal. The number of captured hits that are considered normal (i.e., not timed out, incomplete, or without a session ID). Timed Out. The number of hits that were captured by the Collector that did not include the entire response due to an application or web server timeout. Incomplete. The number of hits, captured by the Collector, that were incomplete or missing details. These hits are marked with the INVALID request header. No Session ID. The number of hits captured by the Collector with no specified session ID. This typically occurs when no sessionizing cookie was present. Although these types of hits are still sent to the Archiver(s), the session cannot be replayed normally due to the missing session ID.

23 Views 23 FxV System Health Summary Dashboard Lost Hits Summary Description Data displayed This view displays the number and type of lost hits. Discarded Hits. The number of hits discarded before being sent to an Archiver. Dropped. The number of hits discarded before being sent to an Archiver because a packet was dropped within the hit or SSL connection. This typically occurs when the Collector is overloaded. Malformed URLs. The number of hits discarded before being sent to an Archiver because the URL was non-standard or could not be parsed. Memory Full. The number of hits discarded before being sent to an Archiver because the Collector s shared memory buffer was full. Queue Full. The number of hits discarded before being sent to an Archiver because the upload queue was full. Each Collector has a queue to hold hits before sending them to Archivers. Whenever this queue is full, extra incoming hits are discarded.

24 24 Foglight Cartridge for FxV Archiver Summary Container View The Archiver Summary container view provides a snapshot of each Collector s performance status, as well as hit and database information for all Collectors as a whole. Use this view to ensure a particular Collector is not experiencing load or hardware issues. Example Description of Embedded Views This view is made up of the following embedded views: Hit Processing Details and Statistics

25 Views 25 FxV System Health Summary Dashboard Corrupt Data Counts Database Details and Rates Archiver Warning Summaries

26 26 Foglight Cartridge for FxV Archiver Profile Statistics

27 Views 27 FxV System Health Summary Dashboard Hit Processing Details and Statistics Description This view provides information about how successful hits are being transferred from the Server to the Archiver.

28 28 Foglight Cartridge for FxV Hit Processing Details and Statistics Data displayed Processed. The total number of hits that were captured by a Collector, sent to the Archivers, and analyzed and processed successfully. Note that not all of these processed hits were necessarily written to the database; after processing, some hits may still be intentionally dropped by a Hit Filter, or may have been unintentionally discarded if the appliance was overloaded. Failed. The total number of hits that could not be processed by the Archivers due to an Archiver runtime failure. Failures can be further investigated in the Archiver logs. Failed hits do not contribute to the Processed tally. Discarded. The total number of hits that were sent to the Archivers for storage, but were discarded before processing could be completed. Typically, incoming hits are discarded when an Archiver s memory buffer is filled, and do not contribute to the Processed tally. Note that hit discards can also occur at the Collector before hits are sent to the Archiver. Total. The count totals for hits process, failed, and discarded. Available. This count indicates whether the Archiver was successful in its regular attempt to poll the Server for configuration settings. Intentionally Dropped. The number of hits that were intentionally dropped by Hit Filters in order to conserve disk space. It is not uncommon for the Archiver(s) to drop hits from static areas of web sites, or to drop hits from non-html resources such as images or style sheets. Sessions Active. The number of session facts, used for hit analysis, currently active in the Archiver rules engine. This count increases and decreases as sessions are captured or stopped, thus indirectly measures the number of concurrent client browsers. Note that larger values indicate increased memory usage and concurrency. A large number of sessions may indicate session timeouts have been set to be too short. Transactions Active. The number of transaction facts, used for hit analysis, currently active in the Archiver rules engine. This count increases and decreases as sessions are captured or stopped, thus indirectly measures the number of concurrent client browsers. Note that larger values indicate increased memory usage and concurrency, and are typically the result of the creation of transaction filters.

29 Views 29 FxV System Health Summary Dashboard Corrupt Data Counts Description Data displayed This view provides information about the volume of corrupt data that is being sent to the Archivers. Cookie Names. The number of hits whose sessionizing cookie was missing. The absence of a cookie in a captured hit affects future playback. Request Header Names. The number of hits captured by the Collector that were missing details in the request header. These hits are marked with the INVALID request header. Request Field Names. The number of hits captured by the Collector that were missing fields. Response Header Names. The number of hits captured by the Collector that were missing details in the response header.

30 30 Foglight Cartridge for FxV Database Details and Rates Description Data displayed This view provides information on the capture database, or the repository formed by all Archivers that is used for searching and replay. Capture Size. The size of all database segments in the FxV database. If there are no storage appliances, then this value is the total volume of available data for search and replay tasks. If a storage tier exists, this value represents the temporary amount of data currently held in the capture database. Note that in the latter case, the database size increases and decreases as segments are written to the capture database, and are discarded after being transferred to the storage tier. Storage Size. The size of all database segments currently being maintained by capture appliances. If there are no storage appliances, this value is zero; otherwise, this value is the size of the storage database. Note that in the latter case, the database size will continue to grow in size until it has reached maximum capacity. Sessions. The number of sessions in all segments of the capture database that are available for search and replay. Note that as segments are removed from the database, the sessions they contain are correspondingly removed. Segments. The number of database segments, each of which contains a time span of captured data, currently in use in the capture database. Note that the segment count decreases when segments are deleted. A large number of segments can degrade search performance. Hits. The number of hits in all segments in the capture database. This value represents the total hits available for search and replay. Note that as segments are removed from the database, the hits they contain are correspondingly removed. Capture Rate. The rate at which hits are received from all Collectors, and written to the capture database. The rate represents hits captured per second over the last two-minute interval. Growth Rate. The rate at which the segment database has changed over the last two minutes. This value is indicative of the volume of data being written to the appliance.

31 Views 31 FxV System Health Summary Dashboard Archiver Warning Summaries Description Data displayed This view displays counts for warnings that may occur when capture data is moving from the Server to an Archiver. Hits Discarded. The total number of hits that were sent to the Archivers for storage, but were discarded before processing could be completed. Typically, incoming hits are discarded when an Archiver s memory buffer is filled, and do not contribute to the Processed tally. Note that hit discards can also occur at the Collector before hits are sent to the Archiver. Hit Analysis Failures. The total number of hits that could not be processed by the Archivers due to an Archiver runtime failure. Failures can be further investigated in the Archiver logs. Hit Analysis Warnings. The total number of hits that were marked as warnings by a hit filter. Dropped Segments. The number of times a database segment was deleted from the local disk before it could be transferred to a storage appliance. If segment transfer is enabled, this value should be zero unless errors have occurred; otherwise, this value will increase linearly. Write Buffer Failures. The number of times a write buffer was lost due to an internal error. The support bundle will include all the error details.

32 32 Foglight Cartridge for FxV Archiver Profile Statistics Description Data displayed These views provide a snapshot of each Archiver, indicating how well the hardware on which the Archiver exists is keeping up with tasks such as hit processing and writing to the database. CPU Idle. The percentage of time the CPU was idling on the appliance. This value is averaged over a five-second period during the last metric update. A consistently low value indicates the appliance is overloaded. CPU IO Wait. The percentage of time the CPU was waiting on disk operations. This value is averaged over a five-second period during the last metric update. Note that this value can increase sharply (up to 70% or more) for very short periods of time, but should normally be 10% or less. A consistently high value indicates that there may be a hard drive failure. Raid Array. This value reports whether the performance of the appliance RAID array is degraded. If the RAID array is reported to be degraded, degradation may be due to a hard disk failure, but may also occur if the RAID array is initializing or being repaired in the background. Alarms. The number of alarms generated by the Collector. Note that this indicates a possible issue with the Collector, not the web application that is being monitored.

33 Views 33 FxV Capture Archivers Dashboard FxV Capture Archivers Dashboard The FxV Capture Archivers dashboard provides complete performance-related views for the selected FxV Archiver. Views in this section include: Capture Archiver Warning Summary View on page 34 Hardware Container View on page 36 Hit Processing Container View on page 39 Archiver Health Container View on page 42 Hit Analysis Container View on page 47 Database Container View on page 49

34 34 Foglight Cartridge for FxV Capture Archiver Warning Summary View This view displays counts for warnings that may occur when capture data is moving from the Collector to an Archiver. Example

35 Views 35 FxV Capture Archivers Dashboard Capture Archiver Warning Summary View Description Data displayed This view displays counts for warnings that may occur when capture data is moving from the Server to an Archiver. Alarms. The number of alarms generated by the Collector. Note that this indicates a possible issue with the Collector, not the web application that is being monitored. Analysis Failures. The total number of hits that could not be processed by the Archivers due to an Archiver runtime failure. Failures can be further investigated in the Archiver logs. Buffer Failures. The number of times a write buffer was lost due to an internal error. The support bundle will include all the error details. Segments Dropped. The number of times a database segment was deleted from the local disk before it could be transferred to a storage appliance. If segment transfer is enabled, this value should be zero unless errors have occurred; otherwise, this value will increase linearly. Segments Closing. The number of segments currently being closed by the Archiver. This value should be been zero and one; otherwise, the Archiver health needs to be investigated.

36 36 Foglight Cartridge for FxV Hardware Container View The Hardware container view provides performance information about the hardware platform on which the Archiver is running. Example Description of Embedded Views This view is made up of the following embedded views: Hardware Usage Graph Views Hardware Statistics FileSystem View Hardware Usage Graph Views Description Data displayed This view displays usage graphs for the Archiver hardware memory and CPU. CPU Usage. The amount of CPU cycles used by the appliance to run user and system processes during the given time frame. Memory Usage. The amount of system memory used by the appliance during the given time frame.

37 Views 37 FxV Capture Archivers Dashboard Hardware Statistics Description Data displayed This view displays status information about the Archiver hardware memory, CPU, RAID, and internal clock. CPU Idle. The percentage of time the CPU was idling on the appliance. This value is averaged over a five-second period during the last metric update. A consistently low value indicates the appliance is overloaded. CPU IO Wait. The percentage of time the CPU was waiting on disk operations. This value is averaged over a five-second period during the last metric update. Note that this value can increase sharply (up to 70% or more) for very short periods of time, but should normally be 10% or less. A consistently high value indicates that there may be a hard drive failure. Raid Array. This value reports whether the performance of the appliance RAID array is degraded. If the RAID array is reported to be degraded, degradation may be due to a hard disk failure, but may also occur if the RAID array is initializing or being repaired in the background. Processes Running. The number of currently running processes, averaged over a five-second period during metric updates. For light loads, this value may be small, but for heavy loads, the value will oscillate normally as I/O operations are synchronized. Processes Blocked. The number of processes that are currently waiting to run, averaged over a five-second period during metric updates. For light loads, this value may be zero, but for heavy loads, the value oscillate normally as I/O operations are synchronized. Note that a consistently high value may indicate a threading problem. Clock Skew. This indicates whether the respective clocks on the Server and Archiver are out of sync. Unsynchronized clocks between different appliances has an adverse effect on the reliability of captured data.

38 38 Foglight Cartridge for FxV FileSystem View Description Data displayed The FileSystem view provides information about the percentage of space used on the variable, temporary and root file systems.use this view to ensure that the file systems are functioning correctly, and are not being overloaded with incoming data. Warnings and errors are triggered when the file system space fills with data to a maximum capacity. Variable. The amount of variable space available on the file system. Temporary. The amount of temporary space available on the file system. Root. The amount of root space available on the file system.

39 Views 39 FxV Capture Archivers Dashboard Hit Processing Container View The Hit Processing container view provides information on how cleanly hit processing is occurring as the Archiver receives and records data from the Collector. Example Description of Embedded Views This view is made up of the following embedded views: Hit Processing Details Hit Processing Statistics

40 40 Foglight Cartridge for FxV Hit Processing Details Description Data displayed This view provides historical information about how successfully hits are being transferred from the Collector to the Archivers. Processed. The total number of hits that were captured by a Collector, sent to the Archivers, and analyzed and processed successfully. Note that not all of these processed hits were necessarily written to the database; after processing, some hits may still be intentionally dropped by a Hit Filter, or may have been unintentionally discarded if the appliance was overloaded. Failed. The total number of hits that could not be processed by the Archivers due to an Archiver runtime failure. Failures can be further investigated in the Archiver logs. Failed hits do not contribute to the Processed tally. Discarded. The total number of hits that were sent to the Archivers for storage, but were discarded before processing could be completed. Typically, incoming hits are discarded when an Archiver s memory buffer is filled, and do not contribute to the Processed tally. Note that hit discards can also occur at the Collector before hits are sent to the Archiver.

41 Views 41 FxV Capture Archivers Dashboard Hit Processing Statistics Description Data displayed This view provides count information on how active hit processing currently is on the Archiver. Available. This count indicates whether the Archiver was successful in its regular attempt to poll the Server for configuration settings. Intentionally Dropped. The number of hits that were intentionally dropped by Hit Filters in order to conserve disk space. It is not uncommon for the Archiver(s) to drop hits from static areas of web sites, or to drop hits from non-html resources such as images or style sheets. Sessions Active. The number of session facts, used for hit analysis, currently active in the Archiver rules engine. This count increases and decreases as sessions are captured or stopped, thus indirectly measures the number of concurrent client browsers. Note that larger values indicate increased memory usage and concurrency. A large number of sessions may indicate session timeouts have been set to be too short. Transactions Active. The number of transaction facts, used for hit analysis, currently active in the Archiver rules engine. This count increases and decreases as sessions are captured or stopped, thus indirectly measures the number of concurrent client browsers. Note that larger values indicate increased memory usage and concurrency, and are typically the result of the creation of transaction filters.

42 42 Foglight Cartridge for FxV Archiver Health Container View This view offers a complete summary of assets and actions that are indicative of the Archiver s health. Use this view to ensure the Archiver is not overloaded. Example Description of Embedded Views This view is made up of the following embedded views: JVM Statistics TCP Batches Memory Details Segment Transfer Details Archiver Health Counts

43 Views 43 FxV Capture Archivers Dashboard JVM Statistics Description Data displayed This view displays memory usage information for the Java Virtual Machine on the Archiver. Peak. The peak memory usage within the displayed time frame. Current. The current JVM memory usage. Free. The amount of JVM memory that is currently available. This value should oscillate as normal garbage collection occurs. Allocated. The total amount of JVM memory that has been allocated on the Archiver. This amount can suddenly increase as the JVM automatically resizes the heap size to minimize garbage collections, and gradually decrease during Archiver inactivity. Note that these fluctuations correspondingly affect the other JVM memory usage statistics.

44 44 Foglight Cartridge for FxV TCP Batches Memory Details Description Data displayed This view displays memory usage information for the Java Virtual Machine on the Archiver for running TCP batches. Peak. The peak JVM memory usage for running TCP batches in the given time frame. Current. The amount of JVM memory currently in use for TCP batches. Free. The amount of unused JVM memory running TCP batches. This value should oscillate as normal garbage collection occurs. Note that the amount of free memory can change very rapidly as the JVM automatically resizes the heap. Allocated. The amount of heap memory allocated to the JVM for running TCP batches. Note that this value can suddenly increase when a spike in capture traffic occurs, after which it will gradually decrease after periods of relative inactivity. Shared. The total size of shared JVM memory allocated to store raw hits prior to them being sent to the Archiver for processing. Each TCP batch has a limited number of hits that it can buffer. Used. The amount of shared JVM memory currently in use to store raw hits that are awaiting being sent to the Archiver for processing. Note that this will be discarded if this value exceeds the shared amount. Also note that a small amount of shared memory is typically used, but short, periodic bursts are normal. A sustained value above 25% of the shared memory size indicates the appliance is having difficulty keeping up with incoming traffic.

45 Views 45 FxV Capture Archivers Dashboard Segment Transfer Details Description Data displayed This view provides status information on segment transfers from the Archiver to a Storage appliance. In some appliance configurations, the Storage appliance option and segment transfer feature are not used. Attempts. The number of times the Archiver tried to transfer a database segment to or from a remote appliance. Since segment transfer involves a bi-directional handshake, transfer attempts are tracked at both the capture appliance and the storage appliance. Note that this value is zero if segment transfer is not enabled; otherwise the value increases linearly as regular transfer attempts are made. Attempts Waiting. The number of database segments that have copied to the storage appliance and initialization and transfer has not yet been completed. Note that if segment transfer is enabled, this value should be small unless errors have occurred. Completions. The number of times the capture archiver has successfully transferred a segment to or from a remote appliance. Since segment transfer involves a bi-directional handshake, transfer attempts are tracked at both the capture appliance and storage appliance. Note that this value is zero if segment transfer is not enabled; otherwise the value should be identical to the number of segment attempts if no errors or repeated attempts have occurred. Copying. The number of segments currently being copied to the Storage Appliance. Note that this value should be between zero and two when the Capture Archiver is healthy. Copying Waiting. The number of database segment that have been closed and removed, but the actual process of copying the segment to the remote Storage Appliance has not yet begun. Note that if segment transfer is enabled, this value should be small unless errors have occurred; otherwise, this value increases linearly.

46 46 Foglight Cartridge for FxV Archiver Health Counts Description Data displayed This view lists counts that relate to Archiver performance. Cached Items. The number of unique data items currently in the Archiver memory cache. These data items assist with the removal of duplicate captured data. A large value may indicate a data quality problem or that the appliance is overloaded. Batch Queue. The number of raw hits queued up for processing. Although this number should not exceed the batch limit, note that the Archiver queue and queue limit are often the same. Incoming hits are first kept in shared memory, then placed in the queue for processing one at a time. Refresh Time. The time required to recalculate dynamic metrics, including: Available Database Aspects, Hits, Segments, and Sessions, Capture Rate, Database Size, and all metrics in the Archiver Appliance category. These dynamic metric values are updated in the background every two minutes. A consistently large refresh time indicates the appliance is experiencing heavy loads. Configuration. Indicates whether an Archiver was able to retrieve configuration settings from the Server. Archivers always periodically contact the Server to verify configuration settings in order to capture incoming hits. Failure to retrieve configuration settings indicates a networking issue.

47 Views 47 FxV Capture Archivers Dashboard Hit Analysis Container View The Hit Analysis container view displays count information for actions related to hit analysis. Use this view to ensure the Archiver is not experiencing load issues with hit traffic, and if this is the case, pinpoint where the problem lies. Example

48 48 Foglight Cartridge for FxV Hit Analysis Counts Description Data displayed This view displays counts related to hit analysis. Rules Fired. The number of times a hit filter match condition or transaction filter event condition was true. Note that there typically is a correlation between the number of hit or transaction filters and this value. A large rules fired count indicates a greater amount of CPU time spent on hit analysis. Session Filters. The number of session facts, used for hit analysis, currently active in the Archiver rules engine. This value increases as new session IDs are captured, and decreases as sessions stop, indirectly measuring the number of concurrent client browsers. Note that a larger count indicates indicate increased memory usage and higher concurrency, and may also indicate that session timeouts have been set to be too short. Session Filters Completed. The number of sessions that have stopped and were written to the capture database. Transaction. The number of transaction facts, used for hit analysis, currently active in the Archiver rules engine. This value increases as start events, defined for transaction filters, are met, and decreases as transactions stop. Note that a large count indicates increased memory usage and CPU cycles spent on hit analysis. Transaction Completed. The number of transactions that have have stopped and were written to the capture database. Custom Fields. The number of custom field facts, defined by all active sessions and transactions. A fact is created for each session or transaction custom field value. Note that larger values indicate increased memory usage. Session Timeouts. The number of completed sessions that have stopped due to a timeout rule instead of an explicit Default Session Stop Condition.

49 Views 49 FxV Capture Archivers Dashboard Database Container View The Database container view provides a complete summary of the Archiver s database and database activity including segment status, incoming data make-up, and search and call activity. Example Description of Embedded Views This view is made up of the following embedded views: Database Details Database Rates and Counts Database Cache Counts Call and Search Status and Counts Incoming Counts FileSystem View

50 50 Foglight Cartridge for FxV Database Details Description Data displayed This view provides information about the segments that are currently in the Archiver database. Size. The size of all database segments in the FxV database. If there are no storage appliances, then this value is the total volume of available data for search and replay tasks. If a storage tier exists, this value represents the temporary amount of data currently held in the capture database. Note that in the latter case, the database size increases and decreases as segments are written to the capture database, and are discarded after being transferred to the storage tier. Sessions. The number of sessions in all segments of the capture database that are available for search and replay. Note that as segments are removed from the database, the sessions they contain are correspondingly removed. Segments. The number of database segments, each of which contains a time span of captured data, currently in use in the capture database. Note that the segment count decreases when segments are deleted. A large number of segments can degrade search performance. Hits. The number of hits in all segments in the capture database. This value represents the total of hits available for search and replay. Note that as segments are removed from the database, the hits they contain are correspondingly removed. Aspects. The number of aspects in the open database segment. Aspects are created dynamically as needed to track fields, cookies, headers, and other searchable database objects. Note that a high aspect count indicates the possibility of a data quality issue, and degraded search performance.