Beruflich Dokumente
Kultur Dokumente
5.5.0
Trademarks
Quest, Quest Software, the Quest Software logo, AccessManager, ActiveRoles, Aelita, Akonix, AppAssure, Benchmark Factory, Big Brother, BusinessInsight, ChangeAuditor, ChangeManager, DeployDirector, DirectoryAnalyzer, DirectoryTroubleshooter, DS Analyzer, DS Expert, ERDisk, Foglight, GPOADmin, Imceda, IntelliProfile, InTrust, Invirtus, iToken, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin, MessageStats, Monosphere, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure, Quest Central, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin, SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon, Tag and Follow, Toad, T.O.A.D., Toad World, vAutomator, vControl, vConverter, vFoglight, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vSpotlight, vStream, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vBackup, Vizioncore vEssentials, Vizioncore vMigrator, Vizioncore vReplicator, Vizioncore vTraffic, Vizioncore vWorkflow, WebDefender, Webthority, 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.
Table of Contents
Introduction to this Guide ...................................................................................................................................7
About Foglight .................................................................................................................................................................. 8 About this Guide............................................................................................................................................................... 8 Foglight Documentation Suite .......................................................................................................................................... 9 Core Documentation Set ....................................................................................................................................... 10 Cartridge Documentation Sets .............................................................................................................................. 17 Feedback on the Documentation........................................................................................................................... 17 Text Conventions ........................................................................................................................................................... 18 About Quest Software, Inc. ............................................................................................................................................ 18 Contacting Quest Software.................................................................................................................................... 19 Contacting Quest Support ..................................................................................................................................... 19
First Steps.......................................................................................................................................................... 39
Getting Started with SupportLink .................................................................................................................................... 40 Downloading Foglight ..................................................................................................................................................... 40 Next Steps ...................................................................................................................................................................... 41
Table of Contents
Index....................................................................................................................................................................75
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 infrastructureto 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.
Chapter 3, Installation and Setup OverviewProvides an overview of the Foglight installation and setup process and acts as a preface or supplement to the Administration and Configuration Guide and the appropriate part of the Installation and Setup Guide set. This chapter summarizes the main steps involved in installing and configuring Foglight. As well, this chapter directs you to the appropriate instructions in the Administration and Configuration Guide and in the Installation and Setup Guide set. Chapter 4, Starting Points in FoglightIntroduces several dashboards that are starting points in the Foglight browser interface. This chapter also includes examples of next steps that you can take. In addition, this chapter provides getting started tips on common elements in the browser interface and features that can affect how you see data in the monitoring dashboards. Foglight offers a wide range of functionality through its customizable dashboards. Consult this chapter to learn about some of the starting points, next steps, and workflows that are available to users with different roles and needs. Appendix A, Foglight Client ReferenceContains material drawn from the chapters Introducing Foglight, Installation and Setup Overview, and Starting Points in Foglight for users who continue to use the Foglight Client.
10
Online Help: You can open the online help by selecting the Help tab from Foglights action panel.
PDF: The complete Foglight documentation set is available in Adobe 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 Reference Guide, 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 5.5.0 > Documentation. The default location of the documentation after installation is <foglight_home>/docs. Adobe Reader is required. HTML: Release Notes are provided in HTML format. Videos: Tutorial videos are not provided with the product, but are available on SupportLink. They provide an easy and accessible way to learn about key features and help you get started with Foglight.
11
System Requirements and Platform Support Guide (PDF) Upgrade Guides (PDF) Installation and Setup Guide set (all in PDF format) Administration and Configuration Guide (PDF and online help) Foglight User Guide (PDF and online help) Command-Line Reference Guide (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)
12
installation and setup procedures and suggests starting points in the Foglight browser interface. In addition, it provides instructions for getting started with SupportLink and downloading Foglight. You can consult this guide prior to following the procedures described in the Installation and Setup Guide set, the Administration and Configuration Guide, and the Foglight User Guide, or use it as a supplement to these guides. Whats New Guide The Whats New Guide (PDF) outlines new features and enhancements in a release of Foglight. System Requirements and Platform Support Guide The System Requirements and Platform Support Guide (PDF) contains information about: Hardware requirements for 32- and 64-bit installations of the Foglight Management Server and the database. Platform requirements for the Foglight Management Server. Platform requirements for the Foglight Agent Manager. Platform requirements for the Foglight Client. Requirements for the Java Runtime Engine (JRE). Operating system requirements for the Cartridge for Operating Systems. Supported web browsers. Supported external databases. Supported report viewer. Review this guide prior to installing the Foglight Management Server. Installation and Setup Guide Set The Installation and Setup Guide set (PDF) includes: Installation prerequisites, recommendations, and guidelines. Instructions for installing, configuring, and running the Foglight Management Server.
13
Information about installing, configuring, and running the Foglight Agent Manager. Information about database configuration, tuning, and management. Information about installing cartridges and agents. An appendix with instructions for installing, configuring, and running the Foglight Client. Foglight Upgrade Field Guide The Foglight Upgrade Field Guide (PDF) provides instructions on how to upgrade the Foglight Management Server, the Foglight Agent Manager (FglAM), the Foglight Client (SPID) to the latest version. In addition, this guide discusses best practices for upgrading and provides information about the version compatibility of the Foglight Agent Manager, the Foglight Client, and the Cartridge for Operating Systems with version 5.5.0 of the Foglight Management Server. This guide is intended for any user who wants to upgrade one or more components in their current installation of Foglight to the latest version. The Foglight Upgrade Field Guide is available from SupportLink. Cartridge Upgrade Field Guide The Cartridge Upgrade Field Guide (PDF) provides instructions on how to upgrade Foglight cartridges to the latest version. This guide is intended for any user who wants to upgrade their Foglight cartridges. The Cartridge Upgrade Field Guide is available from SupportLink. Administration and Configuration Guide The Administration and Configuration Guide (PDF and online help) is intended to assist Foglight System Administrators to configure and manage Foglight. This guide provides: Conceptual information about Foglight administration components. Configuration instructions. Instructions on how to use the dashboards in the Administration module to perform administrative tasks such as managing agents, users, security, data, rules, registry variables, schedules, and cartridges. Information about building script agents.
14
Information about retrieving data with queries and scripts. Information about deploying and creating Foglight agents using the commandline interface. Information about the query language used in Foglight and instructions for using this language to set the scope for rules and derived metrics, create rule conditions and expressions, reference expressions in messages, and create derived metric expressions. A list and descriptions of the built-in, core Foglight rules that monitor the health of your application server environment. Instructions for performing certain agent management tasks from the command line, such as deploying agents, creating agent instances, and retrieving agent logs. A list and descriptions of default port assignments in Foglight. In addition, the Administration and Configuration Guide includes the following information in an appendix: Foglight Client Reference: This appendix shows examples of dashboards and command-line output in an environment that uses the Foglight Client. Foglight User Guide The Foglight User Guide (PDF and online help) includes configuration instructions, conceptual information, and instructions on how to use the browser interface. This guide provides: An introduction to the key screen elements in Foglight, the navigation tools used in the Foglight browser interface, and roles. Information about customizing Foglight according to User Preferences and setting home pages and themes. Descriptions of how to work with Foglight dashboards and common elements found on most dashboards. Information about working with services, alarms, reports, data, and data sources. Information about monitoring agents, hosts, and the Foglight Management Server. This guide is intended for any user who wants to configure Foglight using the browser interface.
Introduction to this Guide Foglight Documentation Suite Command-Line Reference Guide The Command-Line Reference Guide (PDF and online help) helps you use Foglight commands to interface with different components of your monitoring environment without using the browser interface.
15
This guide contains information about syntax conventions, lists the Foglight commands, and contains getting started instructions that show you how to configure your environment. It also contains information about the commands for performing tasks such as: Managing the Foglight Management Server, the Foglight Agent Manager, agents, cartridges, and licences. Upgrading the database or managing encryption keys. Working with entities such as metrics, monitoring policies, and schedules. In addition, it contains an appendix with information about the commands related to using the Foglight Client. This guide is intended for Foglight System Administrators who want to use Foglight commands. Transition Guide The Transition Guide (PDF) includes information that allows you to quickly transition to Foglight 5 from a Foglight 4 perspective. Use it to find your Foglight 4 components in Foglight 5, understand typical workflows, and perform some of the basic administrative tasks. This guide also contains an appendix with examples of dashboards and command-line output for environments that use the Foglight Client for agent communication and management. This guide is intended for Foglight 4 users who are getting started with Foglight 5. Web Component Tutorial Use the Web Component Tutorial (PDF and online help) as a first step in learning how to create custom views using the Web Component Framework technology in Foglight 5. It provides procedures that you can follow to construct simple views. This tutorial serves as a starting place for learning how to use the Web Component Reference, which contains a list of all the components in the Web Component Framework and a description of their properties.
16
This guide is intended for any user who wants to custom-build Foglight views for use in the browser interface. Web Component Guide The Web Component Guide (PDF and online help) builds on the Web Component Tutorial and provides information about the mechanisms of page creation using the Web Component Framework technology. It describes how pieces of information can be passed to related views and how information can be extracted from the underlying data sources for presentation in a view. It is intended to be used with the Web Component Reference to assist you in creating new views. Web Component Reference The Web Component Reference (online help) contains a list of all the view components in Foglight 5 and a description of their properties.
Introduction to this Guide Foglight Documentation Suite Managing Agents The video Managing Agents introduces you to the Agent-related dashboards in the Administration module and instructs you on how to perform agent management. Working with Alarms The video Working with Alarms provides information on how to locate alarms in the browser interface, filter alarms, and identify related hosts, related agents, and alarm sources. Working with Hosts The video Working with Hosts introduces you to the Hosts dashboard.
17
18
Text Conventions
The following table summarizes how text styles are used in this guide: Convention
Code
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
Variables
Interface
19
Web site
Refer to our web site for regional and international office information.
20
1
Introducing Foglight
This chapter discusses how Foglight works, defines key concepts and terms, and describes Foglight components. This chapter contains the following sections: Welcome to Foglight....................................................................................................................22 Key Concepts and Terms ............................................................................................................23 How Foglight Works ....................................................................................................................26 Foglight Components ..................................................................................................................33
22
Welcome to Foglight
What is 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 infrastructureto 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.
23
Topology
Model
Domain
24
Definition Data that is collected from your monitored environment and transformed into a standard format for use by the Foglight Management Server. Monitoring data includes both metrics and topology object properties. Monitoring data that describes a topology object, for example, a host name. An observation taken over time, for example, a Metric, StringObservation, or TopNList. In Foglight, every observation is linked to a specific part of the topology model, for example, CPU utilization on a particular monitored host. A simple value observation measured over time, for example, a count, rate, or percentage. A way of organizing objects in your monitored environment. Foglight automatically creates most of the object groups that you need to monitor your environment. Domains are examples of a type of object group that Foglight creates. Most users do not need to create object groups. Only advanced Foglight administrators should create object groups. See Object Groups on page 32 for more information. In Foglight, a service is defined as any grouping of meaningful or interesting things in your monitored environment, for example, a business process or an application. The monitoring dashboards in Foglight are organized around the theme of services. Foglight allows you to create and edit services. See Services on page 30 for more information. In Foglight, service levels are availability measurements on services. See Service levels, alarms, and state on page 31 for more information.
Service
Service Levels
25
Definition An agreement between information technology managers and end-users on the availability of system and application resources. Tiers help you structure services in a way that represents your monitored environment. By default, Foglight organizes data into tiers such as User, Web, Application, and Database. Using object groups, you can extend the set of tiers used by Foglight. See the Foglight User Guide. The central component of Foglight. The Management Server receives information from agents, stores and processes data, and makes it available in the browser interface. See Foglight Management Server on page 33 for more information. A Foglight middleware component that manages agents installed on monitored hosts. See Foglight Middleware on page 34 for more information. A unit that is added to the Foglight Management Server. Cartridges contain components that extend the functionality of Foglight, such as agents, rules, and views. See Cartridges on page 35 for more information. A Foglight component that monitors a specific part of your environment, such as an operating system, application, or server. Agents collect data from your monitored environment and send it to the Management Server. See Agents on page 36 for more information. A piece of business logic that links a condition with a result. Foglight evaluates rule conditions against monitoring data. If a condition evaluates to true, the results that are configured for that condition occur, for example, an alarm is fired and an email is sent.
Agent
Rule
26
Definition A variable stored in the Foglight registry that can be used in rule conditions, actions, and expressions. The value of a Foglight registry variable can be configured to change over time.
27
Figure 1 This diagram illustrates a model instance created using monitoring data for a particular domain (for example, an infrastructure domain such as Windows), and which is a representation of a model type. In this model instance, a host is represented by a node. It has three child nodes, which represent the CPU, memory, and disk of the host. The CPU and disk nodes also have child nodes that represent the individual processors and file systems, respectively. The monitoring data that populates this model instance is a mix of configuration data (host name, OS, patch level, CPU brand, clock speed, amount of memory) and metrics (CPU usage, allocated memory). Each piece of data is stored only once, but no context is lost. You can know the host name from the CPU or memory nodes, even though the host name is not stored along with the CPU or memory information. Metric data is also stored as part of the context. For example, if there are two hosts, the CPU usage for Host A would be stored with the Host A instance. What is truly innovative about Foglight is that these models can be built for any domain at any time. A model instance can be built at the click of a button in the browser interface (using the service builder), or as a result of new data arriving in the Foglight Management Server. Foglight models have been built for multiple domains, including Java, .NET, database, and custom applications (Siebel, PeopleSoft, Oracle E-Business).
28
More importantly, models can be built that represent anything in your monitored environmentyour organizational structure, the physical layout of your server room, or the geographical distribution of your data centers. Once built, the artifacts that are part of a model are packaged into a cartridge (a .car file) and installed on the Foglight Management Server.
Domains
A domain is a specific technology or part of your environment that you are interested in monitoring and for which Foglight collects data and builds model instances. As described above, Foglight models have been built for multiple domains. Foglight collects data for different categories of domains: custom applications, packaged applications, databases, end-user, and infrastructure. For example, you can choose to collect end-user data as well as data for an application domain such as WebLogic, a database domain such as Oracle DB, and for an infrastructure domain such as Windows. The domains and subdomains for which Foglight collects data are listed below: Domain Custom Applications Subdomain .NET JBoss Oracle AS WebLogic WebSphere
29
Domain Databases
Subdomain DB2 Oracle PA for Oracle PA for SQL Server SQL Server SQL Server 2005 Sybase
End User
Infrastructure
Packaged Applications
30
The Domains dashboard presents an overview of all domains for which Foglight collects data. It summarizes the state of all monitored domains and allows you to drill down on a specific domain and investigate problems related to it. See the Foglight User Guide for more information about monitoring domains. There are Foglight cartridges available for different domains. See Cartridges on page 35 for a list of cartridges.
Services
In the context of Foglight, a service is any component or group of components that you want to monitor. The services you create reflect the components in your monitored environment that are meaningful or interesting to you. Examples of services include: An application, including its Web servers, application servers, and databases A collection of related systems, such as all Windows machines in your monitored environment A business process, such as retail banking Using the Service Operations Console, you can focus on monitoring a specific group of services by subscribing to those services and viewing their dependencies. In addition, this dashboard allows you to select tiers that are relevant to you and display service breakdowns based on these tiers. See Service Operations Console on page 62 for more information about this dashboard. See the Foglight User Guide for more information about working with services. Creating and editing services Foglight allows you to create service categories. A category is a top-level service that contains a hierarchy of services. Each service can include any component in your monitored environment, including other services. A service can have relationships to other services, and is dependent on the services that are added to it. The state of a service is impacted by the services it contains. See Service levels, alarms, and state on page 31 for information about how state is rolled up in Foglight. When you create a service, you classify it as a global service or a local service. A global service can be used in multiple places. A local service belongs only to the parent service to which it was added. A corresponding service level is automatically created for each service you define. You can also use Alarm Filters to decide what alarms are relevant to a given service and can impact the availability of that service. See Services and availability on page 31 for more information.
31
You can make changes to existing services, such as renaming a service while preserving the history for that service. Using a rule-based group, you can define a set of components that are automatically included in a service when certain data arrives. Rulebased groups allow you to dynamically manage the components in a service. See the Foglight User Guide for more information about creating and editing. Service levels, alarms, and state In Foglight, service levels are availability measurements on services. Default service levels measure availability based on the state of individual nodes in a model instance. A Foglight rule evaluates a series of conditions designed to create an alarm if a performance probleman exception conditionhas occurred. The alarm has one of three severity levels: Warning, Critical, or Fatal. Rules are associated with nodes in the model. When one of the conditions of a rule evaluates to true, an alarm is attached to the node in the model instance with which the rule is associated. A state is set for each node in a model instance. If there have been no exception conditions, the nodes state is set to the default state Normal. However, if an alarm is attached to a node, then the state of the node is set to the severity level of the alarm (Warning, Critical, or Fatal). In general, the state of a node reflects the most severe alarm attached to that node. In addition to having an individual state, each node also has an aggregate state. By default, the aggregate state of a node represents the state of itself and all its children. Though there are some exceptions, in general, Foglight calculates a nodes aggregate state by evaluating the state of each of its child nodes and setting the aggregate state to be equal to the most severe child node state. In this way, state is propagated up the model instance. Services and availability The availability of a service is, by default, established based on a rollup of all the alarms fired for the monitored components added to that service. However, there can be cases in which you do not want this type of alarm rollup to be performed. Often, only a subset of the alarms fired for a monitored component are relevant to a given service. For example, an alarm fired by a rule called CPU Trending (which monitors the CPU usage over the last 12 months) may be relevant to your Management Planning service, but not to your Billing Application service. In this case, you would not want Fatal alarms fired by this rule for a component of the Billing Application service to signal a service outage.
32
Foglight allows you to specify the alarms that are relevant to a given service by means of Alarm Filters. See Filtering Alarms in the Foglight User Guide for more information. Alarm impact and history Although all alarms indicate a problem in your monitored environment, some alarms may be of higher priority to you, depending on the services that they affect. When investigating an alarm, you can see whether that alarm has a negative impact on the service levels of specific services. Performing impact analysis on an alarm can help you determine the priority of fixing the problem that is detected by the alarm. Certain alarms occur repeatedly over time in your monitored environment. Foglight allows you to see the history of an alarm to find out when that alarm fired previously for a specific monitored component. For example, if a fatal CPU utilization alarm fires for a host called Host1, you can drill down on that alarm to a view that shows historic occurrences of that alarm on Host1. The alarm history displays information about past occurrences, such as the severity when it occurred, whether it was cleared, and any notes that were added to it. This view helps you identify patterns in the occurrences of alarms for specific components. See Alarms Details in the Foglight User Guide for more information.
Object Groups
An object group is a way of organizing components that are part of your monitored environment. Foglight automatically creates most of the object groups that you need to monitor your environment. Domains are examples of object groups that Foglight creates. The tiers that you add to services in Foglight are based on object groups. Although both object groups and services contain and organize components in your monitored environment, there are differences between them. For example, unlike services, object groups do not have service levels or dependent services. See the Foglight User Guide for more information about the differences between services and object groups. Most users do not need to create object groups, and only advanced Foglight administrators should create them. See the Foglight User Guide for information about working with object groups.
33
Foglight Components
Foglight Management Server
The Foglight Management Server is the central component of Foglight. The Management Server receives information from agents and makes it available in the browser interface. The Foglight database stores all system, application, and performance data. Over time, it becomes an invaluable source of historical information for planning future system capacity requirements and for doing point-in-time analysis. The information in the database can also be made available for use in external systems. The Management Server performs continuous internal monitoring on itself and other Foglight components, as well as on the Java Virtual Machine (JVM) and the database.
34
Contains views and data that can be added to a dashboard or report that you are creating. Provides access to the online help.
Note The action panel is referred to as the page panel in the Web Component Framework documentation, for example in the Web Component Reference.
See the Foglight User Guide and the Administration and Configuration Guide for more information.
Customizable Dashboards
Foglight also includes the Web Component Framework, which allows you to create and populate your own custom interface views on top of the dynamic data schemas generated by the Foglight Management Server. See the Web Component Guide and the Web Component Tutorial for more information.
Foglight Middleware
Most Foglight 5 agents require a middleware component to manage their life cycles and centralize communications with the Foglight Management Server. The System Requirements and Platform Support Guide provides information about supported platforms for Foglight middleware. This release of Foglight contains first and second generation middleware components. The Foglight Client (also known as SPID) is the original technology for managing agents and was released with Foglight 5.0. The Foglight Agent Manager (also known as FglAM) is the next generation technology for managing agents. Over time, it will replace the Foglight Client as the primary middleware component.
35
You can run the Foglight Agent Manager only, the Foglight Client only, or a combination of the Foglight Client and the Foglight Agent Manager in the same installation. The sections below contain the recommendations made by Quest regarding Foglight middleware. New Foglight installations Whenever possible, all new Foglight installations should use the Foglight Agent Manager. However, several agents are not supported by the Foglight Agent Manager. If you plan to deploy these agents in your environment, Quest makes the following recommendation: run the Foglight Agent Manager on as many hosts as possible and run the Foglight Client only on hosts to which you deploy agents that are not supported by the Foglight Agent Manager. Existing Foglight installations If you have an existing Foglight installation where the Foglight Client is running, continue to use the Foglight Client unless you are advised to upgrade to the Foglight Agent Manager by Quest Professional Services or Quest Support. If you have an existing installation where the Foglight Agent Manager is running, continue to use the Foglight Agent Manager. If you have an existing installation in which you are deploying middleware and agents to new monitored hosts, you can use either the Foglight Client or the Foglight Agent Manager. Quest encourages you to start using the Foglight Agent Manager, but both options are supported. With the exception of Appendix: Foglight Client Reference, the instructions in this guide refer to the Foglight Agent Manager.
Cartridges
Cartridges extend the functionality of Foglight and are installed on the Foglight Management Server. A cartridge contains one or more components, such as agents for deployment, communication capabilities, and modifications to the way that data is transformed or handled, as well as rules, reports, and views. The following Foglight 5 cartridges are available: Foglight Cartridge for DB2 LUW Foglight Cartridge for Foglight Transaction Player
36
Foglight Cartridge for FxM Foglight Cartridge for FxV Foglight Cartridge for Integration Foglight Cartridge for Java EE Foglight Cartridge for .NET Foglight Cartridge for Operating Systems Foglight Cartridge for Oracle DB Foglight Cartridge for Oracle E-Business Foglight Cartridge for PeopleSoft Foglight Cartridge for Performance Analysis Oracle Foglight Cartridge for Performance Analysis SQLServer Foglight Cartridge for SAP NetWeaver Foglight Cartridge for Siebel Foglight Cartridge for SQL2005 Foglight Cartridge for SQLServer Foglight Cartridge for Sybase Foglight Cartridge for VMWare When a cartridge is installed and enabled, all of its components become part of the Management Server. Adding cartridges to the Foglight Management Server allows you to monitor additional operating systems, processes, databases, applications, and servers in your environment. See the Administration and Configuration Guide for more information about managing cartridges. See the cartridge documentation for information about each cartridge.
Agents
Agents are deployed on machines in your monitored environment and send data to the Foglight Management Server. Agents can monitor the availability and performance of many aspects of your environment, including network services, operating systems, databases, virtual hosts, log files, file systems, disk space and utilization, top processes, custom applications, application servers, and Web servers.
37
There are several types of agents. One or more instances of each type of agent managed by the Foglight Agent Manager can be deployed per host. For example, there is an agent that collects metrics from the operating system of the host machine. There are also agents that are embedded into systems or the software that they monitor. For example, the Java EE Agent, which collects service request traces, runs embedded in Java EE application servers. Foglight also includes internal agents that monitor Foglight components and services. See the Administration and Configuration Guide for more information about managing and configuring agents. See the documentation for the cartridge in which the agent was included for details about each agent.
38
2
First Steps
This chapter includes instructions on establishing a SupportLink account, logging in to SupportLink, and downloading Foglight 5 documentation and software packages from SupportLink. Follow these instructions if you want to use SupportLink, Quest Supports web self-service, to download Foglight 5.5.0. This chapter contains the following sections: Getting Started with SupportLink.................................................................................................40 Downloading Foglight ..................................................................................................................40 Next Steps...................................................................................................................................41
40
applicable). If you have any questions, contact supportadmin@quest.com or speak with a Support Administrator at one of the support numbers listed on the Contact Support page (Support > Getting Started > Contact Support from the menu bar). To log on to SupportLink:
1 Visit SupportLink at: http://support.quest.com. 2 Under SupportLink Login in the left-hand sidebar, enter the email address
If you have forgotten your password, click Forgot Password in the SupportLink Login left-hand sidebar to obtain your password. If you have any other questions concerning your SupportLink account, contact supportadmin@quest.com. See the Getting Started page (Support > Getting Started from the menu bar) for information about registration and logging in as well as PDFs about SupportLink and Quest Support.
Downloading Foglight
Once you have created a SupportLink account, you can download Foglight 5.5.0 and Foglight 5.5.0 documentation from SupportLink.
41
version 5.5.0.
6 Click the link for the document that you want to download.
Next Steps
Once you have downloaded Foglight 5.5.0 software and documentation, you can get started with the Foglight installation and setup process. See Installation and Setup
42
Overview for summaries of the main steps involved in installing and configuring Foglight.
3
Installation and Setup Overview
This chapter contains the following sections: Getting Started with the Installation and Setup Process .............................................................44 Part 1: Installing or Upgrading the Foglight Management Server................................................45 Part 2: Initializing the Database, Starting the Foglight Management Server, and Logging In .....46 Part 3: Installing or Upgrading Cartridges ...................................................................................47 Part 4: Installing, Configuring, and Starting the Foglight Agent Manager....................................49 Part 5: Deploying and Creating Agents .......................................................................................51 Next Steps...................................................................................................................................53
44
Installation and Setup Overview Part 1: Installing or Upgrading the Foglight Management Server
45
The Installation and Setup Guide also contains a brief overview of hardware requirements and installation recommendations. Prior to installing Foglight, review the System Requirements and Platform Support Guide as well as Before Installing Foglight and Preparing to Install in the Installation and Setup Guide.
Support Guide and the Installation and Setup Guide described in Before You Get Started on page 44.
2 Install or upgrade the Foglight Management Server:
If you are performing a new installation: Run the installer by following the appropriate set of instructions in Installing Foglight in the Installation and Setup Guide. An instance of the Foglight Agent Manager is automatically installed with the Foglight Management Server and runs on the Management Server machine. See Embedded Foglight Agent Manager in the Installation and Setup Guide for more information. If you are upgrading an existing installation: Consult the Foglight Upgrade Field Guide for detailed upgrade instructions.
3 Configure the Foglight Management Server and database:
Configuring the Foglight Management Server: Once you install the Management Server, you may need to configure it, change its settings, or perform other additional setup steps. In addition, if you want to set up Foglight Management Server Federation, postinstallation changes to configuration files are necessary.
Note Foglight Federation is an advanced feature, which requires separate dedicated Foglight Management Servers. Contact Quest PSO for implementation guidance. See the Foglight Federation Field Guide for a description of this feature.
46
For more information, see Foglight Settings in the Installation and Setup Guide for the platform and database you are running. Configuring the database: Depending on the type of database you are running, you may need to configure it or change its settings. For example: If you are using an external database and chose the installer option to manually set up the database later, see Manual Database Configuration in the Installation and Setup Guide for your platform and external database. If you are using an external MySQL database, see External MySQL Database Access for Remote Users in the Installation and Setup Guide for using an external MySQL database on your platform. If you are using an external MySQL database and want to set up an encrypted database connection, see Setting Up an Encrypted Database Connection with SSL in the Installation and Setup Guide for using an external MySQL database on your platform. For more information, see Foglight Settings in the Installation and Setup Guide for the platform and database you are running. Consult the Installation Troubleshooting section in the Foglight Release Notes if you encounter problems when performing the steps listed above.
Part 2: Initializing the Database, Starting the Foglight Management Server, and Logging In
The steps outlined in this section assume that you have already installed the Foglight Management Server. If you have not, refer to Part 1: Installing or Upgrading the Foglight Management Server for more information before proceeding.
1 Before you begin: If you are running a MySQL database (either embedded or
external) and want to migrate data to it from an existing MySQL database, follow the instructions in Migrating Data from an Existing Database in the Installation and Setup Guide for your platform and type of MySQL database (embedded or external).
2 Initialize the Database:
If you are using an external database, the database must be initialized successfully before you can run Foglight. If you are using the embedded database, the initialization is performed when you start the Foglight Management Server.
47
3 Start the Foglight Management Server: The Foglight Management Server can
be run in stand-alone mode, in High Availability (HA) mode (if you are using an external database), or as a Windows service. See Starting and Stopping the Foglight Management Server in the Installation and Setup Guide for information about starting and stopping the Management Server. For information about running the Management Server as a Windows service, see Starting the Foglight Management Server as a Windows Service in the version of Installation and Setup Guide Installing on Windows for the database you are using. For information about running the Management Server in HA mode, see High Availability Mode and Starting and Stopping the Server in High Availability Mode in the version of the Installation and Setup Guide for the external database and platform you are using. See Running the Foglight Management Server in the Command-Line Reference Guide for the full set of options available for starting the Management Server from the command line in either stand-alone or HA mode.
4 Configure the embedded Foglight Agent Manager: If you need to configure
the embedded Foglight Agent Manager, you can do so by running the Foglight Agent Manager configuration interface from the embedded Foglight Agent Manager installation directory. See Configuring the Embedded Foglight Agent Manager in the Installation and Setup Guide for more information.
5 Log in to Foglight: See Logging in to Foglight in the Foglight User Guide for
more information.
48
remote hosts as described below in Part 4: Installing, Configuring, and Starting the Foglight Agent Manager.
Note As described in Part 1: Installing or Upgrading the Foglight Management Server, an instance of the Foglight Agent Manager is automatically installed with new installations of the Foglight Management Server. This embedded Foglight Agent Manager instance runs on the Management Server machine. You can deploy agents to the embedded Foglight Agent Manager if you want to monitor the machine on which the Management Server runs. In addition, the Foglight Agent Manager Adapter cartridge is installed with the Management Server. If you already have Foglight Agent Manager instances running on remote hosts and you do not want to download Foglight Agent Manager installers to additional remote hosts, you do not need to install the Foglight Agent Manager cartridge. The existing Foglight Agent Manager instances can connect to the Management Server.
You can install and manage cartridges using either the command-line interface or the browser interface. In addition, you can download agent installers using the browser interface. The instructions below assume that you are using the browser interface. See Managing Cartridges in the Command-Line Reference Guide for information about performing cartridge-management tasks from the command line.
1 Before you begin:
Review the cartridge documentation for information about cartridge installation prerequisites. Ensure that the Foglight Management Server is running and that you have logged in to Foglight. Ensure that you are granted the required permissions by your Foglight administrator to access the dashboards under the Administration module.
2 Install or upgrade the cartridge:
If you are installing a new cartridge: Install the cartridge by following the instructions in Installing and Managing Cartridges in the Administration and Configuration Guide. In addition, you can install cartridges by means of the Extend Your Monitoring Reach dashboards. See Extending Your Monitoring Reach in the in the Administration and Configuration Guide for more information. If you are upgrading a cartridge: Install the cartridge by following the instructions for that cartridge in the Foglight 5.5.0 Upgrade Field Guide.
Caution Do not disable the previous version of the cartridge before installing the new one. Foglight automatically disables the older cartridge as part of the upgrade process. Once the new cartridge is enabled, you can then uninstall the previous version of the cartridge if you choose.
Installation and Setup Overview Part 4: Installing, Configuring, and Starting the Foglight Agent Manager
49
Ensure that the Foglight Management Server is running and that you have logged in to Foglight. Ensure that you have the required permissions from your Foglight administrator for the dashboards under the Administration module. Identify the host name and Management Server port of each Foglight Management Server with which the Foglight Agent Manager is supposed to communicate.
2 Download or retrieve the Foglight Agent Manager installer: The different
ways to obtain the installer for your platform (fglam-5_5_0<platform>.[bin|exe]) are described below. See the table in Foglight Agent Manager Installer Platform Support Matrix in the Installation and Setup Guide for the name of the installer for your platform. Download the installer from the Components for Download dashboard in Foglight to each machine where you want to install the Foglight Agent Manager: For instructions on navigating to and downloading installers from this dashboard, see Using the Components for Download Dashboard in the Installation and Setup Guide for your platform. Download or retrieve the installer from a URL to each machine where you want to install the Foglight Agent Manager: In situations where unauthenticated or headless access to the installers is required, you can access a URL for direct download using a browser or a file retrieval tool (for example, Wget). No login to Foglight is required. For instructions on navigating to and downloading installers from this URL, see Using the Components for Download Page in the Installation and Setup Guide for your platform.
50
If you are installing a new Foglight Agent Manager: There are different ways to install the Foglight Agent Manager: using the installer GUI, from the command-line, or using the silent (non-interactive) installer. Follow the appropriate set of instructions in Installing the Foglight Agent Manager in the Installation and Setup Guide for your platform. If you are upgrading from the Foglight Client to the Foglight Agent Manager: Consult the Foglight Upgrade Field Guide for detailed upgrade instructions.
4 Configure the Foglight Agent Manager: Some configuration of the Foglight
Agent Manager can be performed during installation. In addition, the Foglight Agent Manager can be configured after installation, for example, to set items such as: The host display name (the host name reported by the Foglight Agent Manager instance). This setting can be used in situations where you need to explicitly set the host name, for example, if the host name is already in use by another machine. Foglight Agent Manager connection options, such as the URL of a proxy used to connect to the Foglight Management Server or options to connect to the Management Server using HTTPS. An override option for using a self-signed server SSL certificate. The Foglight Agent Manager can automatically detect HA-enabled Management Servers and configure itself for them. However, you might need to perform some additional configuration if, for example, a Management Server in the HA cluster has special SSL certificate requirements or if it uses a proxy. Depending on the platform on which the Foglight Agent Manager is installed and the mode in which Foglight is running, you may need to perform additional configuration steps. For example: If you are running Foglight in HA mode, see Getting Started with Server Commands (in the chapter Managing the Foglight Management Server) in the Command-Line Reference Guide for information about configuring the Remote Monitor utility. If you want to run the Foglight Agent Manager as a daemon, see Configuring the Foglight Agent Manager to Run as a Daemon in the Installation and Setup Guide Installing on a UNIX System for the database you are using. If you want to run the Foglight Agent Manager as a Windows service, see Installing the Foglight Agent Manager as a Windows Service in the
51
Installation and Setup Guide Installing on Windows for the database you are using. On UNIX systems, certain Foglight agents require elevated permissions in order to gather the required system metrics. This is achieved by having the Foglight Agent Manager launch these agents with root privileges. To give these agents the required access, the Foglight Agent Manager is configured to launch these agents using an external application that allows privilege escalation (without a password), such as sudo. See Configuring Foglight Agent Manager Agent Privileges in the Installation and Setup Guide Installing on a UNIX System for the database you are using. See Configuring the Foglight Agent Manager in the Installation and Setup Guide for information about a Foglight Agent Manager configuration interface that you can run after installation and about other configuration you might need to perform.
5 Start the Foglight Agent Manager: See Running the Foglight Agent Manager
in the Installation and Setup Guide for information about starting the Foglight Agent Manager. See Running the Foglight Agent Manager in the Command-Line Reference Guide for information about starting the Foglight Agent Manager using the command-line interface on Windows or Unix platforms. Consult Installing and Running the Foglight Agent Manager FAQ in the Installation and Setup Guide if you encounter problems when performing the steps listed above.
52
Review the documentation for the cartridge in which the agent is included for information about agent installation prerequisites. Ensure that the Foglight Management Server is running and that you have logged on to Foglight. Ensure that you are granted the required permissions by your Foglight administrator to access the dashboards under the Administration module. Ensure that the Foglight Agent Manager is running on the machine(s) where you want to deploy agents.
2 Deploy agents and create agent instances:
First, agent packages need to be deployed to the Foglight Agent Manager running on the host that you want to monitor. Once you have deployed agents, you can create agent instances on that host. There are two ways to deploy and create agents: from the browser interface or from the command line: See Deploying Agent Packages to a Monitored Host and Creating Agent Instances on a Monitored Host in the Administration and Configuration Guide for instructions on deploying and creating agents from the Agent Status dashboard. See Deploying Agent Packages To Multiple Hosts and Creating Agent Instances On Multiple Hosts in the Administration and Configuration Guide for instructions on deploying agents to multiple hosts and creating agents on multiple hosts from the Agent Hosts dashboard. See Using the command line to deploy agent packages and Using the command line to create agent instances in the Administration and Configuration Guide for instructions on deploying and creating agents from the command-line. See Managing Agents in the Command-Line Reference Guide for details about the commands available for deploying and creating agents from the command-line.
3 Configure agents: After you deploy and create agents, you may need to edit the
agents properties. See Managing Agent Properties by Type in the Administration and Configuration Guide for information about agent properties. See the documentation for the cartridge in which the agent is included for information about the specific configuration options that are available for each agent.
4 Manage agents: You can perform agent-management tasks like starting,
53
agents from the browser interface and from the command line. See Accessing the Agent Status Dashboard and Assigning Blackouts to Agent Instances in the Administration and Configuration Guide for instructions on managing agents from the browser interface. See Managing Agents in the Command-Line Reference Guide for details about the commands available for managing agents from the command line.
Next Steps
Once you have completed the installation and setup process, you can get started using Foglight. See Starting Points in Foglight for descriptions of default views and dashboards where you can begin.
54
4
Starting Points in Foglight
Foglight offers a wide range of functionality through its customizable dashboards. This means that there are multiple starting points and workflows available for users with different roles and needsadministrators in charge of managing Foglight, operational users interested in troubleshooting problems throughout their monitored environment, users focused on monitoring a specific domain or system, or users interested in services management. When you log in to Foglight, several dashboards are initially selected as starting points and listed under Homes in the navigation panel. This chapter introduces some of these dashboards. Terminology specific to the Foglight browser interface is used throughout this chapter; see Introducing the Browser Interface in the Foglight User Guide for more information about these terms.
Note This chapter uses a facing page layout: details about the numbered items shown in the images are provided on the following page. Select one of the facing page layout options in your PDF viewer before proceeding.
This chapter contains the following sections: Before You Get Started ...............................................................................................................56 Operators Welcome Page ..........................................................................................................58 Administrators Welcome Page ...................................................................................................60 Service Operations Console........................................................................................................62 Hosts Dashboard.........................................................................................................................64 Next Steps...................................................................................................................................66
56
By default, the time range at the top of a dashboard is in real time. When the time range is in real time, the icon and the word Now are shown in the time range display. Figure 1 Hovering over the real time range icon displays a message that identifies the time range as real and informs you how to freeze the time range. Figure 2 If you drill down on an alarm, Foglight disconnects from real time and enters a diagnostic time range. The diagnostic time range spans the same length of time as the current time range did prior to the drill down. Within a diagnostic time range, Foglight typically sets three-quarters of this span to occur prior to the alarm being fired and one-quarter to occur after. For example, if the current time range spans four hours, when you drill down on an alarm, the diagnostic time range also covers a four-hour interval, from three hours prior to when the alarm fired to one hour after it fired (as shown in the image below).
57
Figure 3 In some cases, however, the alarm might have occurred close enough to the current moment that the last quarter of the diagnostic time range would cover a span of time that is in the future. If that is the case, Foglight sets the diagnostic time range to end at the current moment (shown as Now in the time range display). When you are working in a diagnostic time range, no new data is displayed in the views on the dashboard. Foglight indicates that you have frozen the time range and entered a diagnostic time range by presenting a frozen time range display. icon in the time range
Figure 4 Hovering over the icon displays a message that identifies the time range as frozen and informs you how to switch to real time. Figure 5 Until you unfreeze the time range, all drilldowns and navigation to views that use the global time range are frozen in this diagnostic time range. Unfreezing the time range causes it to revert to the last monitoring time range that you used. For more information on current and diagnostic time ranges, see Time Range in the Foglight User Guide.
58
59
1View, acknowledge and clear recent alarms: navigates to the Alarms dashboard. You can use this dashboard to view the state of all alarms across your monitored environment so you can take immediate action on an alarm. See the Foglight User Guide for more information.
Tip Use this dashboard to identify alarm storms or outage events by viewing the alarm count by time.
2View enterprise health organized by monitoring domain: takes you to the Domains dashboard, from which you can view an end-to-end summary of top-level views for all domains, organized by domain. See the Foglight User Guide for more information.
Tip From the Domains dashboard, drill down on a domain to view a high-level summary of its managed instances.
3View the health of critical services: causes the Service Operations Console to appear. In the Service Operations Console, you can choose a group of services as a focal point for your monitoring by subscribing to services of interest and viewing their service dependencies. See Service Operations Console on page 62 and the Foglight User Guide for more information. 4View the health of the monitored hosts in your enterprise: takes you to the Hosts dashboard. Navigate to the Hosts dashboard if you want to view a high-level summary of host-related alarms and performance on all monitored hosts. See Hosts Dashboard on page 64 and the Foglight User Guide for more information. 5Report on your enterprise: causes the Reports dashboard to appear. Use this dashboard to view reports that are scheduled, run a report using a report template, create a custom report, schedule a report to run at a specific time frame, and manage reports. See the Foglight User Guide for more information. 6Tap into the Foglight community: takes you to http://www.foglight.org, where you can read blogs about Foglight and actively participate in existing discussions.
60
61
1Extend Your Monitoring Reach: allows you to complete a configuration interview, generate a configuration plan for your environment, and then execute the plan step-bystep. See the Administration and Configuration Guide for more information. 2View Your Enterprise Health: causes the View Your Enterprise Health page to appear. This page provides links to dashboards that allow you to observe the overall health of your system by viewing existing alarms and the state of your domains, services, and monitored hosts. See the Administration and Configuration Guide for more information. 3Configure Email Settings: takes you to the Email Configuration dashboard, from which you can configure Foglight to direct outgoing mail and reports through your mail server. See the Administration and Configuration Guide for more information. 4Report on Your Enterprise: takes you to the Reports dashboard, from which you can view reports that are scheduled, run a report using a report template, create a custom report, schedule a report to run at a specific time frame, and manage reports. See the Foglight User Guide for more information. 5Do More with Foglight: causes the Do More With Foglight page to appear. This page provides links to dashboards that provide more details about each aspect of your system health. See the Administration and Configuration Guide for more information.
Tip Use the dashboards accessible through the Do More with Foglight page to define your own custom services, quickly build dashboards, view agent status, and perform other administrative functions.
6Tap Into the Foglight Community: takes you to http://www.foglight.org, where you can read blogs about Foglight and actively participate in existing discussions.
62
63
1Service Operations Console Customizer link: opens the Service Operations Console Customizer, which allows you to subscribe to the services that interest you. Subscribing to services causes them to appear in the Service Operations Console table. The Service Operations Console Customizer allows you to select the services you want to monitor and the tiers you want to see; dwells and popups are provided to help you make your selections. See the Foglight User Guide for details. 2Service Name column: lists the services to which you subscribe. See Services on page 30 for more information about services.
Tip Click the name of a service to display a popup with details about that item and links to more detailed views. See the Foglight User Guide for more information about these links.
3 Service Level Compliance column: shows the service level for each service to which you subscribe. Foglight automatically creates a service level for each service. The level of compliance is determined by the component in the most severe state. See Service levels, alarms, and state on page 31 for more information.
Tip Click an icon in this column to display a popup with more information about the Service Level Agreement for the service. Follow the Explore > Service Level Agreement(s) link in the popup to navigate to the Service Levels dashboard populated with information specific to that service. See Viewing Service Levels in the Foglight User Guide for details.
4Alarms column: Shows the number of alarms for the services to which you subscribe. Clicking one of the icons in this column causes an Outstanding Alarm(s) view to appear with a list of alarms specific to that service. 5Tier columns: Show performance information for the tiers you chose to display using the Service Operations Console customizer. The tiers that are available to display in this table are based on the object groups to which you subscribed in the Tier Definition dashboard. See the Foglight User Guide for more information. The icons in each column show the aggregate state of that tier for that category or service. The state of a tier is determined by the most severe state of all the monitored components that belong to this tier. See Service levels, alarms, and state on page 31 for more information about how state is rolled up in Foglight.
Tip Click an icon in one of these columns to display a popup that lists the monitored components within that tier and their current state, as well as drill-downs for the components.
6Service Operations Console tabs: Display details for the selected category or service, such as its contents and dependencies. See the Foglight User Guide for details.
64
Hosts Dashboard
This section provides an introduction to the Hosts dashboard and the views and dashboards to which you can drill down from it. You can use the Hosts dashboard to monitor problems in your environment by focusing on a set of hosts. From this dashboard, you can drill down to different dashboards and views, depending on the host type (physical or virtual). Drill down on a physical host (monitored by Cartridge for Operating Systems agents) to see a real-time monitor for a particular host, details about its alarms, or details about its CPU, memory, disk, or network-related performance. Drill down on a virtual host (monitored by Cartridge for VMWare agents) to see a vmMonitor Virtual Machine dashboard (if the host is a VMWare image); a vmMonitor ESX Server dashboard (if the host is an ESX server); details about its alarms or details about its CPU, memory, disk, or network-related performance. If you are responsible for the availability of a set of hosts and prefer to think in terms of systems, this dashboard is helpful as it allows you to view a summary of the state and performance of those hosts. Filter the list to show all hosts, only monitored hosts (hosts for which Foglight collects CPU and memory metrics), or only hosts that belong to a specific category, for example, all hosts with a particular operating system or all VMWare hosts. You can also search the list of hosts by name. Use this dashboard as the starting point in a host-oriented workflow.
Figure 6
65
1State indicators: allow you to see at a glance the state of the listed hosts. Each indicator shows the aggregate alarm state of the host, which is determined by the most severe alarm for the host. In this dashboard, the indicator represents a state rollup from the host and its children, excluding the state of agents on that host. 2Host name: clicking the host name allows you to drill down to a real-time monitor that provides you with an overview of that hosts health. Drill down to this monitor if you want to see detailed information about how a host is functioning for the time range displayed at the top of the dashboard. A different monitor appears depending on whether the host is physical or virtual. For example, drilling down on a physical host displays a monitor with information such as the number of processes running on it and the top consumers of various metrics.
Tip You can drill down on items in the monitor. For example, if you are interested in investigating memory consumption on a physical host and drill down the monitor for that host, click the Memory button to view memory-related metric charts and tables, such as charts for the top memory consumers on that host.
3 Alarms column: shows the number of alarms for each host. If you are investigating alarms for a host, click one of the icons in this column to cause an Outstanding Alarm(s) view to appear with a list of alarms specific to that host. You can filter the alarms displayed in this view using the Alarm Filter Applied/Not Set dialog box (click Alarm Filter Applied or Alarm Filter Not Set in the title bar to launch this dialog); see Filtering the Alarms View in the Foglight User Guide for details. In addition, you can change the perspective on alarms by selecting one of the tabs at the top of the table; see Alarm List in the Foglight User Guide for details. In the Outstanding Alarm(s) view, click anywhere in the row for an alarm to display a popup with details about that alarm and links to drilldowns. See Alarm Details in the Foglight User Guide for details. 4 CPU, Memory, Disk, and Network columns: each column displays recent and current values for that category of metrics. These columns allow you to obtain a concise overview of CPU-, memory-, disk-, and network-related performance for each host. The values displayed in the sparkline change in accordance with the time range selected at the top right of the dashboard.
Tip If you want to perform further investigation on CPU-, memory-, disk-, and network-related performance for a host, click either the sparkline or current value to drill down to a dashboard with more detailed information for that metric category.
66
Next Steps
Your next steps depend on how you are using this guide and the way you want to use Foglight. Some examples are provided below. If you read this guide prior to installing Foglight: select the appropriate platform- and database-specific Installation and Setup Guide and follow the instructions for installing and configuring Foglight. If you are an operator responsible for monitoring a large environment: you can follow a service- or host-oriented workflow. For example, if you are responsible for ensuring the availability of your Accounting Application service, you can follow a service-oriented workflow that begins in the Service Operations Console. Alternatively, if you prefer a less abstract approach, you can follow a host-oriented workflow that begins in the Hosts dashboard. If you are a technical expert interested in monitoring a specific domain: start with the documentation included with the Foglight cartridge for monitoring that domain. If you are interested in monitoring services: you can follow a service-oriented workflow. See the Foglight User Guide for details about the drilldowns available from the Service Operations Console. If you want to customize aspects of the Foglight browser interface: begin by following the instructions in Customizing Foglight in the Foglight User Guide. If you are a Foglight administrator: consult the Administration and Configuration Guide and the Command-Line Reference Guide for information about performing administrative tasks (in addition to those described above) from the Foglight browser interface and from the command line. If you want to create custom dashboards: review the information in Creating a Custom Dashboard in the Foglight User Guide. You could then learn more about creating dashboards by following Tutorial 1: Creating a Dashboard in the Web Component Tutorial. If you want to create custom views: begin by following Tutorial 3: Adding Views in the Web Component Tutorial. After this tutorial, consult the Web Component Guide and the HTML Web Component Reference pages. These resources can help you create new views using the Quest Web Component Framework technology.
A
Appendix: Foglight Client Reference
This appendix contains material drawn from the chapters Introducing Foglight and Installation and Setup Overview for users who continue to use the Foglight Client.
Note This release of Foglight contains first and second generation middleware components: the Foglight Client (SPID) and the Foglight Agent Manager (FglAM). For recommendations on which middleware component is right for you, see Foglight Middleware on page 34.
This appendix contains the following sections: Introducing Foglight.....................................................................................................................68 Installation and Setup Overview ..................................................................................................69
68
Introducing Foglight
This section presents introductory material about Foglight with reference to the Foglight Client. See Introducing Foglight for a discussion how Foglight works, additional key concepts and terms, information about the Foglight Agent Manager, and descriptions of other Foglight components.
Definition A Foglight middleware component that manages agents installed on monitored hosts. See Foglight Middleware on page 34 for more information.
Foglight Components
Foglight command-line interface
Foglight provides commands that allow you to manage and work with Foglight components without having to use the browser interface. These commands allow you to perform tasks such as managing the Foglight Management Server, the Foglight Client, agents, cartridges, and licences, as well as work with entities such as metrics, monitoring policies, and schedules. For example, this interface allows you to automate component-management tasks using scripts or to use regular expressions to select multiple entities. See the Command-Line Reference Guide for more information.
Foglight Client
The Foglight Client manages certain types of agents installed on monitored hosts. It provides a centralized communications link between the Foglight Management Server and these agents and manages the agents life cycles. The Foglight Client also provides a number of support services such as deployment, upgrade, and the ability to configure agents.
69
Agents
Agents are deployed on machines in your monitored environment and send data to the Foglight Management Server. Agents can monitor the availability and performance of network services, operating systems, log files, file systems, disk space and utilization, top processes, custom applications, application servers, and Web servers. There are several types of agents. One or more instances of each type of agent managed by the Foglight Client can be deployed per host. For example, there is an agent that collects metrics from the operating system of the host machine. There are also agents that are embedded into systems or the software that they monitor. For example, the Java EE Agent, which collects service request traces, runs embedded in Java EE application servers. Foglight also includes internal agents that monitor Foglight components and services. See the Administration and Configuration Guide for more information about managing and configuring agents. See the documentation for the cartridge in which the agent was included for details about each agent.
70
You can install and manage cartridges using either the command-line interface or the browser interface. In addition, you can download agent installers using the browser interface. The instructions below assume that you are using the browser interface. See Managing Cartridges in the Command-Line Reference Guide for information about performing cartridge-management tasks from the command line.
1 Before you begin:
Review the cartridge documentation for information about cartridge installation prerequisites. Ensure that the Foglight Management Server is running and that you have logged in to Foglight. Ensure that you are granted the required permissions by your Foglight administrator to access the dashboards under the Administration module.
2 Install or upgrade the cartridge:
If you are installing a new cartridge: Install the cartridge by following the instructions in Installing and Managing Cartridges in the Administration and Configuration Guide. If you are upgrading a cartridge: Install the cartridge by following the instructions for that cartridge in the Foglight 5.5.0 Upgrade Field Guide.
Caution Do not disable the older cartridge before installing the new one. Foglight automatically disables the older cartridge as part of the upgrade process. Once the new cartridge is enabled, you can then uninstall the older cartridge if you choose.
Ensure that the Foglight Management Server is running and that you have logged in to Foglight. Ensure that you have the required permissions from your Foglight administrator for the dashboards under the Administration module.
71
Identify the host name of the Foglight Management Server with which the Foglight Client is supposed to communicate. See Installing the Foglight Client in the Installation and Setup Guide for details.
2 Download the Foglight Client installer: From the Components for Download
dashboard in Foglight, download the installer for your platform (Spid-5_5_0install_<platform>.[bin|exe]) to each machine where you want to install the Foglight Client. See Accessing the Components for Download Dashboard in the Administration and Configuration Guide for instructions on navigating to and downloading installers from this dashboard.
3 Install the Foglight Client:
If you are installing a new Foglight Client: There are different ways to install the Foglight Client: from the installer GUI, in silent mode, or in console mode (UNIX only). Follow the appropriate set of instructions from Installation Processes in the Installation and Setup Guide. If you are upgrading the Foglight Client: Consult the Foglight Upgrade Field Guide for detailed upgrade instructions.
4 Configure the Foglight Client: The Foglight Client may need to be configured
after installation depending on the platform on which it is installed and the mode in which Foglight is running: If you are running the Foglight Client on a UNIX System, see Configuring Foglight Client Agent Privileges For UNIX in the version of Installation and Setup Guide Installing on a UNIX System for the database you are using. If you are using an external database and are running Foglight in High Availability mode, see Configuring the Foglight Client for High Availability in the Installation and Setup Guide for the platform and type of external database you are running.
5 Start the Foglight Client: See Running the Foglight Client in the Installation
and Setup Guide for information about starting the Foglight Client and connecting it from a monitored host to the Foglight Management Server through a firewall. See Foglight Client Commands in the Command-Line Reference Guide for information about starting the Foglight Client using the command-line interface. Consult Installing and Running the Foglight Client (SPID) FAQ in the Installation and Setup Guide if you encounter problems when performing the steps listed above.
72
Review the documentation for the cartridge in which the agent is included for information about agent installation prerequisites. Ensure that the Foglight Management Server is running and that you have logged on to Foglight. Ensure that you are granted the required permissions by your Foglight administrator to access the dashboards under the Administration module. Ensure that the Foglight Client is running on the machine(s) where you want to deploy agents.
2 Deploy agents and create agent instances:
First, agent packages need to be deployed to the Foglight Client running on the host that you want to monitor. Once you have deployed agents, you can create agent instances on that host. There are two ways to deploy and create agents: from the browser interface or from the command line: See Deploying Agent Packages to a Monitored Host and Creating Agent Instances on a Monitored Host in the Administration and Configuration Guide for instructions on deploying and creating agents from the Agent Status dashboard. See Deploying Agent Packages To Multiple Hosts and Creating Agent Instances On Multiple Hosts in the Administration and Configuration Guide for instructions on deploying agents to multiple hosts and creating agents on multiple hosts from the Agent Hosts dashboard. See Using the command line to deploy agent packages and Using the command line to create agent instances in the Administration and Configuration Guide for instructions on deploying and creating agents from
73
the command-line. See Managing Agents in the Command-Line Reference Guide for details about the commands available for deploying and creating agents from the command-line.
3 Configure agents: After you deploy and create agents, you may need to edit the
agents properties. See Managing Agent Properties by Type in the Administration and Configuration Guide for information about agent properties. See the documentation for the cartridge in which the agent is included for information about the specific configuration options that are available for each agent.
4 Manage agents: You can perform agent-management tasks like starting,
stopping, activating, deactivating, deleting, and setting blackout periods for agents from the browser interface and from the command line. See Accessing the Agent Status Dashboard and Assigning Blackouts to Agent Instances in the Administration and Configuration Guide for instructions on managing agents from the browser interface. See Managing Agents in the Command-Line Reference Guide for details about the commands available for managing agents from the command line.
Next Steps
Once you have completed the installation and setup process, you can get started using Foglight. See Starting Points in Foglight for descriptions of default views and dashboards where you can begin.
74
Index
75
Index
A
about Foglight 8 about Quest Software 18 Administration home page 33 Administrators Welcome Page starting points 60 after reading this guide next steps 66 agent 25, 36 agent management component 68 alarm 31 history 32 impact 32 alarm rollup for services 31 Alarms column Hosts dashboard 65 Outstanding Alarm(s) for Selected Categories view 63 Outstanding Alarm(s) view 65 Service Operations Console 63 Alarms dashboard 59 availability measurement on services 24 availability of services 31 changing information categories Outstanding Alarm(s) view 65 client 25 component Foglight Agent Manager 68 configuring Foglight Agent Manager 49 Foglight Client 70 configuring browser interface next steps 66 contacting Quest 19 core 10 CPU, Memory, Disk, Network columns details dashboard 65 Hosts dashboard 65 sparkline values 65 creating and editing services service creating and editing 30 creating custom dashboards next steps 66 creating custom views next steps 66 current time range 56 customizable dashboards 55
B
business processes 24
D
dashboards Alarms 59 Do More with Foglight page 61 Domains 59 Email Configuration 61 Extend Your Monitoring Reach 61 Hosts 59 Reports 59, 61
C
cartridge 17, 25, 35 Categories and Services view details popup 63 changing alarm perspective Outstanding Alarm(s) view 65
76
Service Operations Console 59 View Your Enterprise Health page 61 Welcome page 58, 60 data collected from your monitoring environment 24 details dashboard CPU, Memory, Disk, Network columns 65 Host name 65 details popup Categories and Services view 63 Outstanding Alarm(s) view 65 Service Level Compliance column 63 determining compliance levels severe state components 63 diagnostic time range 56 Do More with Foglight page 61 documentation 9, 10, 17 domain 23, 28 Custom Applications 28 Databases 29 End User 29 Infrastructure 29 list 28 Packaged Applications 29 Domains dashboard 59 downloading Foglight from SupportLink 40
E
Email Configuration dashboard 61 embedded Foglight Agent Manager 47, 48 environment monitored by Foglight 23 establishing a SupportLink account 40 Extend Your Monitoring Reach dashboard 61
G
getting started with SupportLink 40 grouping objects 24 grouping of objects 32
H
history of an alarm 32 Homes navigation panel 55 Host name details dashboard 65 Hosts dashboard 65
F
feedback 17 filtering alarms Outstanding Alarm(s) view 65 Foglight
Index
77
real-time details monitoring 65 Hosts dashboard 59 Alarms column 65 CPU, Memory, Disk, Network columns 65 Host name 65 monitoring hosts 64 starting host-oriented workflows 64 starting points 64 State indicators 65
N
navigation panel Homes 55 next steps after reading this guide 66 configuring browser interface 66 creating custom dashboards 66 creating custom views 66 large environment monitoring 66 performing administrative tasks 66 services monitoring 66 specific domain monitoring 66
I
impact of an alarm 32 installing Foglight Agent Manager 49 Foglight Client 70
O
object group 24, 32 observation 24 Operators Welcome Page starting points 58 Outstanding Alarm(s) for Selected Categories view Alarms column 63 Outstanding Alarm(s) view Alarms column 65 changing alarm perspective 65 changing information categories 65 details popup 65 filtering alarms 65
L
large environment monitoring next steps 66 list 28 list of domains 28 list of subdomains 28 logging in to SupportLink 40
M
Management Server 25 measuring availability on services 24 metric 24 model 23 models topology 23 monitored environment 23 organizing principle for data from 23 relationship between items 23 monitoring data 24 monitoring hosts Hosts dashboard 64
P
performing administrative tasks next steps 66
R
real time range 56 real-time details monitoring 65 registry variable 26 Remote Monitor 50 Reports dashboard 59, 61 rollup of alarms for services 31
78
rule 25
S
service 24, 30 availability 31 subscribing 63 service level 24, 31 service level agreement 25 Service Level Compliance column details popup 63 Service Operations Console 63 Service Operations Console 59 Alarms column 63 Service Level Compliance column 63 starting points 62 viewing the state of services 62 Service Operations Console Customizer 63 services monitoring next steps 66 Setup & Support dashboards Email Configuration 61 severe state components determining compliance levels 63 SLA 25 sparkline values CPU, Memory, Disk, Network columns 65 specific domain monitoring next steps 66 starting Foglight Agent Manager 49 Foglight Client 70 starting host-oriented workflows Hosts dashboard 64 starting points Administrators Welcome Page 60 Hosts dashboard 64 Operators Welcome Page 58 Service Operations Console 62 state 31 viewing for services 62
T
technical support 19 text conventions 18 tier 25
Index
79
tiers 62 time range current (real time) 56 diagnostic (frozen) 56 topology 23 topology object property 24
U
unfreezing the time range 56
V
View Your Enterprise Health page 61 viewing the state of services Service Operations Console 62
W
Welcome Page Administrator 60 Operator 58