Concert band transcription of the Stargate SG1 theme. Audio export: http://soundcloud.com/samplers1712/stargate-sg1-concert-band Please visit my website: http://composer1992.wordpress.com/Full description
Full description
List of Equipment from the SG1 RPG
no descriptionFull description
Full description
Descripción: T24 CUSTOMER & ACCOUNT
Full description
T24 CUSTOMER & ACCOUNTDescription complète
to find out the awareness of online food delivery via different portals and also to find the usage of online ordering through these portals
NURSING CARE TO PREPARE FOR ANTICIPATED PRECIPITATE BIRTHFull description
isa pa
As soon as Lucy was born, music made her smile. When she learned to stand, she started bouncing up and down every time she heard a tune. Her parents took her to a toddlers’ dance class, where t...
A software engineering project, which is generally used for pizza delivery system.
AIESEC's new Bucket List of how Value Delivery should workFull description
enterperneurship
Full description
Questionnaire to understand the different types of Alternatives for the Banking Industry in Pakistan. It Provides a simple and easy solutions for the different problems that exists in the Pakist...
common labor and delivery complicationsFull description
Full description
Deskripsi lengkap
Services Delivery Academy - SiteScope For version 11.x Revision A
A College of the HP University Student Guide Book 1 of 2
Services Delivery Academy – SiteScope
Student Guide Book 1 of 2
Revision A
Use of this material to deliver training without prior written permission from HP is prohibited.
This content is provided for use throughout the Learning Solution duration and is the copyrighted work of HP. This content is provided for the sole use of the person accessing the Learning Solution and may not be used by any other person and may not be reproduced, recorded, repurposed, distributed or modified without the written permission of HP. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Services Delivery Academy – SiteScope For version 11.x Revision A Student Guide Book 1 of 2
SiteScope – Supported Platforms You can install SiS as a 32-bit application over 32-bit or 64-bit environments for the supported Windows, Solaris, and Linux operating systems. It can also be installed as a 64-bit application over a 64-bit environment for the supported Windows, Solaris, and Linux operating systems. VMware environments are supported in SiS according to the tested configurations (VMware ESX 3.0, VMware VirtualCenter 3.0, and vSphere 4.1). The following 64-bit environments are supported in SiS: •
Microsoft Windows Server 2003 SP2 Standard/Enterprise Edition
•
Microsoft Windows Server 2008 SP2 Enterprise Edition
•
Microsoft Windows Server 2008 R2 Enterprise Edition (both on Windows Server 2008 R2 host with Hyper-V enabled, and on Windows Server 2008 SP2 64-bit guests on this host and on hosts without Hyper-V)
•
Solaris 10
•
Linux 5.5
•
Oracle Enterprise Linux 6.0
1-3
Module 1 - Installing SiteScope
SiteScope – Server System Requirements for Windows Platforms – Use the following system requirements for installing SiS on Windows platforms:
5
Computer/Processor
800 MHZ or higher
Operating System
Microsoft Windows 2003 Standard/Enterprise Service Pack (SP)1, SP2 Microsoft Windows Server 2003 Enterprise R2 SP1, SP2 Microsoft Windows Server 2008 Standard Enterprise SP2
SiteScope – Server System Requirements for Solaris Platforms – Use the following system requirements for installing SiS on Solaris platforms: Computer/Processor
Sun 400 MHz UltraSparc II Processor or higher
Operating System
Sun Solaris 9 or 10 (with latest recommended patch cluster)
SiteScope – Client System Requirements The SiS client is supported by the following: – All Microsoft Windows-based operating systems (including Microsoft Windows 7) using Microsoft Internet Explorer 7.x/8.0 – Firefox 3.0x (certified on clients running on Windows environments only)
Certified Configuration Example – The following configuration has been certified in a high load environment for an installation of SiS to be integrated with HP BSM.
Certified Configuration Example The configuration on the slide has been certified in a high load environment for an installation of SiS that was integrated with BSM. This configuration replaces the recommended configuration that appears in the SiS Deployment Guide.
1-8
Module 1 - Installing SiteScope
Review Questions What is the recommendation for memory and free disk space for installing an SiS server on a Windows platform? a. 1 GB or more for memory and 5 GB or more for free hard disk
space
b. 2 GB or more for memory and 10 GB or more for free hard
disk space
c. 4 GB or more for memory and 20 GB or more for free hard
disk space d. 3 GB or more for memory and 15 GB or more for free hard disk space
Review Questions (Cont.) How much total physical memory has been certified in a high load environment for a SiS installation to be integrated with HP BSM? a. 10 GB b. 16 GB c. 20 GB d. 15 GB
SiteScope Server Sizing – The foundation of a successful monitoring deployment is the proper sizing and planning of the server where SiS is to run. – Server sizing is determined by a number of factors, such as: • The number of monitor instances to be run on a SiS machine • The frequency of the monitors to be executed • The types of protocols and applications to be monitored • The amount of monitor data needed to be retained on the server for reporting
SiteScope Server Sizing SiS Monitor capacity and velocity can be significantly impacted by numerous factors including, but not limited to, the following: •
SiS server hardware, operating system, patches, and third-party software
•
Network configuration and architecture
•
Location of the SiS server in relation to the servers being monitored
•
Monitor types and distribution by type
•
Monitor frequency and execution time
•
Business Availability Center integration
•
Database logging
Knowing the number of servers in the environment, their respective operating systems, and the application to be monitored is the starting point for estimating the number of monitors that might be needed.
1-12
Module 1 - Installing SiteScope
SiteScope Capacity Calculator – The SiS Capacity Calculator is a tool that makes recommendations for system requirements, helps you predict system behavior, and perform capacity planning for SiS – Open the SiS Capacity Calculator from the link in the Home page of the SiS Documentation Library or from: \tools\SitecopeCapacityCalculator.xls
SiteScope Capacity Calculator While the default SiS configuration permits running thousands of monitors, sizing the server where SiS is installed might be necessary to achieve optimum performance. Since each configuration is different, you should use the SiS Capacity Calculator to verify whether your configuration requires sizing. You can enter the CPU and memory details of the system on which SiS is running and the number of monitors of each type and the frequency in which they are to run in the SiS Capacity Calculator. The calculator then displays the expected CPU usage and memory usage for each monitor type, and the recommended system requirements for the given workload. This enables you to determine whether your configuration requires tuning. Note: The SiS Capacity Calculator is supported in SiSs that are running on Windows versions and are 32-bit only.
To use the SiS Capacity Calculator, perform the following steps: 1. Navigate to \tools and open the SiS Capacity Calculator: a. For SiS 32-bit, SiteScopeCapacityCalculator_32_bit.xls b. For SiS 64-bit, SiteScopeCapacityCalculator_64_bit.xls 2. In the Monitor Usage tab, enter the following information in the Requirements section: a. Average % CPU usage b. CPU type c. Memory heap size (in megabytes) 3. In the Monitors section, enter the number of monitors for each type, and the update frequency for each monitor. The results and recommendations are displayed in the Results and Recommendations section. A difference of 30% – 40% between the expected results and the actual results should be considered as acceptable.
1-14
Module 1 - Installing SiteScope
SiteScope Server Sizing Recommendations – To ensure optimal sizing, HP strongly recommends the following guidelines to be ensured in a SiS deployment: • SiS runs as a standalone server • Only one instance of SiS exists and it runs on a single server • SiS failover needs to be identical in size to the primary SiS server
SiteScope Server Sizing Recommendations While the default SiS configuration allows you to run thousands of monitors, sizing the server where SiS is installed might be necessary to achieve optimum performance. Since each configuration is different, you should use the SiS Capacity Calculator to verify if your configuration requires sizing. Proper sizing of the server where SiS is configured to run is the foundation of successful monitoring deployment. To ensure optimal sizing, HP strongly recommends the following SiS server environment: •
SiS runs as a standalone server. For best results, SiS should be the only program running on a server. BSM, LoadRunner, databases, Web servers, and so forth should not be on the SiS server.
•
Only one instance of SiS exists and it runs on a single server. Running multiple instances of SiS on a single server can cause severe resource problems.
•
SiS Failover needs to be sized just like the primary SiS server.
1-15
Module 1 - Installing SiteScope
SiteScope Capacity Limitations – When SiS is integrated with BSM, performing high load operations might cause problems in SiS. – A few guidelines to follow are: • Do not run the Publish Template Changes Wizard for over 3,000 monitors at once • Do not run the Monitor Deployment Wizard to (MDW) to create over 3,000 monitors at once • Do not copy/paste over 3,000 monitors in a single action • Do not perform a Global Search and Replace to modify a Business Service
– SiS can manage integration properties for over 2,500 monitors at one time.
SiteScope Capacity Limitations SiS Capacity Calculator helps you predict system behavior and perform capacity planning for SiS. It also assists you with planning a proper grouping strategy and the number of monitors required and SiS servers needed for implementing a stable monitoring solution.
Sources to Download SiteScope – Download an evaluation copy of SiS software from the following url: www.hp.com/go/hpsoftwaresupport – Alternatively: 1. Navigate to Products → HP SiteScope software 2. Click the HP SiteScope11.10 Evaluation link 3. To log in, enter your HP Passport user ID and password or register with the HP Software Downloads Center
Sources to Download SiteScope SiS is available as a self-extracting executable file and packages folder that you can download from the HP web site. It is also available on DVD. SiS is installed on a single server and runs as a single application on Windows platforms, or as a single application or various processes on Solaris or Linux platforms.
Download SiteScope 11.12 SiS 11.12 must be installed on top of SiS 11.10 or higher. It should be installed on standard SiS installations only (not on non-standard installations, such as System Health or SiS Failover Manager). SiS 11.12 patch can be downloaded from http://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_SIS_00167. For information on features added in SiS 11.11, including EMS Common Event Flow, VMware Monitor Enhancements, VMware Capacity Management Solution Template, Amazon CloudWatch Metrics Integration, and Classic SiS Failover Solution, refer to the SiS 11.11 Documentation Updates PDF, available from SiteScope installation directory: sisdocs\pdfs\SiteScopeDocUpdates.pdf.
Installation Procedure for SiteScope 11.1x Before installing the SiS patch, you should back up your current SiS installation directory and all of the subdirectories within the directory. Stop all SiS processes and services. If installing SiS on an Oracle Enterprise Linux environment, you must manually configure the environment before performing the installation. You can upgrade SiS 10.x or later versions directly to SiS 11.10 by exporting SiS configuration data using the Configuration Tool, and then installing the 11.1x patch on it. For versions of SiS earlier than 10.00, you must first upgrade to SiS 10.x. For versions of SiS earlier than 9.x, you must first upgrade to SiS 9.x.
1-20
Module 1 - Installing SiteScope
Installing SiteScope11.10 – After downloading the SiS zip file, unzip it to a temporary directory on the server machine.
Installing SiteScope11.10 You must install SiS11.12 on top of SiS11.10 or higher. It should be installed on standard SiS installations.To install SiS 11.12 using a silent installation, run the installer from the command line with -i silent flag. (The oviinstallparams.ini (answers) file is not required, unlike in a regular installation.) For Windows, HPSiS1112_11.12_setup.exe -i silent For UNIX, HPSiS1112_11.12_setup.bin -i silent
1-21
Module 1 - Installing SiteScope
Installing SiteScope11.10 (Cont.) – The installation requires the following input: • Install directory • Installation type (HP SiteScope, HP Sitescope Failover, HP SiteScope for load testing) • Port number • Administrator e-mail • Valid HP Software license Note: It is not necessary to enter licensing information at this point to use SiS during the free evaluation period.
Installing SiteScope11.10 – Step #1 The SiS 64-bit version consumes up to 3 times more memory than the SiS 32-bit version. Accordingly, if you are using the SiS 64-bit version you should increase the Java Virtual Machine (JVM) heap size on the server manually using the Configuration Tool available in the SiS server.
Installing SiteScope11.10 – Step #2 The Choose Locale screen is displayed. Select OK to continue with the installation. The Initialization screen is displayed. If the Installer detects any anti-virus program running on your system, it prompts you to examine the warnings before you continue with the installation. Read the warnings, if any, that appear in the Application requirement check warnings screen and follow the instructions as described in the screen. Select Continue to proceed with the installation.
Installing SiteScope11.10 – Step #4 The SiS license agreement is displayed. Read the agreement and accept the terms of the agreement. Select Next to continue.
Installing SiteScope11.10 – Step #5 Select the SiS setup type in the Product Customization screen. The following SiS setup types are displayed: •
HP SiS – This setup type is the standard SiS installation.
•
HP SiS Failover Manager – This setup type enables you to use a backup SiS server to monitor infrastructure availability if a SiS server fails.
•
HP SiS for Load Testing – This setup type is used with an HP LoadRunner or HP Performance Center installation only. It enables you to define and use SiS monitors on a LoadRunner or Performance Center application. SiS provides additional monitoring that complements the native LoadRunner and Performance Center monitors.
Installing SiteScope11.10 – Step #7 The Choose the folders screen opens. Accept the default directory location or click Browse to select another directory. If you select another directory, the installation path must not contain spaces in its name and must end with a folder named SiS (the folder name is case sensitive). To restore the default installation path, select Reset. Select Next to continue.
Installing SiteScope11.10 – Step #8 The Install Checks screen opens and runs verification checks. Select Next after the free disk space verification is completed successfully. If the free disk space verification is not successful, then you need to do the following: 1. Free the disk space, for example by using the Windows Disk Cleanup utility. 2. Try again.
Installing SiteScope11.10 – Step #9 In the Pre-Install Summary screen, select Install. The installer selects and installs the required SiS software components. Each software component and its installation progress are displayed on your screen during installation. The installer installs the Microsoft Visual C++ 2005 Redistributable, if required, and resumes SiS installation.
Installing SiteScope11.10 – Step #10 After installing the SiS components, the Introduction screen of the SiS Installation Wizard opens. Select Next to continue.
Installing SiteScope11.10 – Step #11 The Settings screen of the SiS Configuration Wizard opens. Enter the required configuration information and select Next to continue: •
Port — If the port number is already in use (an error message is displayed), enter a different port. If necessary, you can change the port later using the Configuration Tool. The default port is 8080. Note: If you plan to use SiS Failover to monitor multiple primary SiSs from a single Failover machine, each primary SiS installation must be configured to answer on a unique port number. You can check the ports used by the SiS server using the SiS Configuration Wizard.
•
License file — Enter the path to the license file or click Select and then select the SiS license key file. A license must be purchased if you intend to use SiS beyond the 60day trial period. It is not necessary to enter license information at this point to use SiS during the free evaluation period.
•
Use local system account — By default, SiS is installed to run as a Local System account. This account has extensive privileges on the local computer, and has access to most system objects. When SiS is running under a Local Systems account, it attempts to connect to remote servers using the name of the server.
•
Use this account — Select to change the user account of the SiS service. You can set the SiS service to log on as a user with domain administration privileges. This gives SiS access privileges to monitor server data within the domain. Enter an account and password (and confirm the password) that can access the remote servers. Note: When SiS is installed to run as a custom user account, the account used must have Log on as a service right.
1-33
Module 1 - Installing SiteScope •
Service name — The name of the SiS service. If the machine has a previous version of SiS installed, enter another name for the SiS service. The default service name is SiS.
•
Start SiS service after install — Automatically starts the SiS service after the installation is complete. For installing the SiS 11.12 patch, ensure to uncheck this check box.
Installing SiteScope11.10 – Step #12 The Import Configuration screen opens, enabling you to import existing SiS configuration data to the new SiS installation. Select one of the following options and then select Next to continue: •
Do not import configuration data
•
Use the existing exported configuration file — This enables you to use SiS data, such as templates, logs, monitor configuration files, and so forth, from an existing exported configuration file. SiS data is exported using the Configuration Tool, and is saved in a ZIP format. Click the Select button and navigate to the user data file that you want to import.
•
Import from the following SiS installation — Click the Select button and navigate to the SiS installation folder from which you want to import configuration data.
•
Include log files — This enables you to import log files from the selected SiS installation folder.
Installing SiteScope11.10 – Step #13 The Install HP Operations Agent screen opens. The Operations agent is required if SiS is integrated to send events and metrics to an Operations Manager (OM) or BSM Gateway server. Select one of the following options and then select Next to continue: •
Do not install HP Operations Agent — The HP Operations agent is not installed.
•
Install HP Operations Agent — Select to install the HP Operations agent on the SiS server. The agent enables SiS to send events and act as data storage for metrics data when SiS is integrated with an Operations Manager or BSM Gateway server.
Installing SiteScope11.10 – Step #14 The Summary screen opens. Check that the information is correct and select Next to continue, or Back to return to previous screens to change your selections.
Installing SiteScope11.10 – Step #15 The Done screen opens. To access the SiS user interface, click the connection address for this installation of SiS. Select Finish to close the SiS Configuration Wizard.
Installing SiteScope11.10 – Step #16 When the installation finishes, the Installation Complete window opens displaying a summary of the installation paths used and the installation status. If the installation was not successful, review the installation log file for any errors by clicking the View log file link in the Installation Complete window. The log file opens in a web browser. For more information about the installed packages, select the Details tab. Select Done to close the installation program. If the installation program determines that the server must be restarted, it prompts you to restart the server. After the server is restarted and you log in, the installation wizard performs other required setup procedures.
Installing SiteScope11.12 – Step #1 As discussed earlier, we need to install SiS11.12 on top of SiS11.10 or higher. It should be installed on standard SiS installations. Hence, once you install SiS 11.10, you then need to install the SiS 11.12 patch. The screen on the slide shows the patch being installed.
Installing SiteScope11.12 – Step #3 The SiS license agreement is displayed. Read the agreement and accept the terms of the agreement. Select Next to continue.
Installing SiteScope11.12 – Step #5 The Post-Install screen is displayed, which automatically goes to the installation steps. The Installation screen appears and proceeds to the subsequent screens.
Installing SiteScope11.12 – Step #6 When the installation is complete, the Installation Complete window is displayed, as shown in the figure on the slide. It shows the summary of the installation paths used and the installation status. If the installation was not successful, review the installation log file for any errors by clicking the View log file link to view the log file in a web browser. For more information about the installed packages, click the Details tab. Select Done in the Installation Complete screen.
Installing SiteScope11.12 – Step #7 To verify that Sitecope is running successfully, perform the following steps: 1. Execute Services.msc from Start Run menu and ensure that the SiS service is running. If it is not running, start the service. 2. Go to Start All Programs Sitescope Open HP SiteScope. The SiS GUI opens in Internet Explorer.
1-46
Module 1 - Installing SiteScope
Review Question Which of the following SiS setup type is used with an HP LoadRunner or HP Performance Center installation only? a. SiteScope b. SiteScope Failover Manager c. Sitescope for Load Testing d. HP System Health
SiteScope Failover High Availability (HA) Solutions – SiS Failover provides the following benefits: • Automated monitoring of the availability of multiple, primary SiS machines by the Failover Manager, and the automatic backup of a single SiS instance during failover • Failover mechanism is based on shared storage between the primary and failover servers
– There are two types of HA solutions in SiS 11.1x: • SiS Failover using Failover Manager • Classic SiS Failover solution
SiteScope Failover High Availability (HA) Solutions HP SiS Failover is a special version of SiS that includes automated failover functionality. It enables you to implement failover capability for infrastructure monitoring by making sure that a failed SiS machine is automatically and quickly replaced by a different machine with little service disruption. A failover is a backup operation that automatically switches the functions of a primary system to a standby server if the primary system fails or is temporarily taken out of service. Provisioning for a failover is an important fault tolerance function for mission-critical systems that require high availability. Ideally, a failover system automatically and transparently transfers the service provided by the failed system to the backup system. SiS 11.00 introduced a new failover mechanism by using a Failover Manager to manage and provide backup monitoring. Previous versions of SiS had a classic failover solution available, which were discontinued in SiS 11.00. The classic SiS Failover solution was reinstated in SiS 11.11 as an alternative to using the SiS Failover Manager solution for providing automated failover functionality. This enables you to choose the failover solution that best suits your needs. SiS Failover Manager is freely included with your regular SiS installation.
1-49
Module 1 - Installing SiteScope
SiteScope Failover Using Failover Manager – SiS Failover with a new solution includes the following features: • SiS Failover uses a Failover Manager to manage and provide backup monitoring. • Failover Manager is installed on a local machine with access to the installation folder of the primary SiS it is monitoring, avoiding gaps in measurement data or offset in the frequency intervals of monitors between the primary and failover SiS. • Failover Manager can monitor multiple, primary SiS simultaneously.
SiteScope Failover Using Failover Manager The SiS Failover Manager solution provides the following benefits: •
•
On SiS Configuration sharing: •
SiS is installed on a shared resource that is accessible to the failover machine.
•
When a primary SiS is down, the SiS Failover process activated by SiS Failover Manager continues monitoring from the exact point where the primary SiS was left off.
•
No data loss in reports.
•
No configuration copying (configuration changes between primary and failover servers are transparent).
•
Configuration changes made on SiS Failover Manager are available on the primary SiS.
On SiS Failover Manager installation: •
Standalone management application with no user interface that is responsible for managing primary and failover instances. It is installed on a local disk, not on the shared resource.
•
SiS Failover Manager can monitor multiple primaries simultaneously from a single Failover Manager machine and provide automatic backup for a single SiS instance during failover.
•
The data storage requirements for SiS Failover are significantly less than for a primary SiS. This is because the function of SiS Failover is to provide temporary monitoring continuity if a primary SiS fails.
1-50
Module 1 - Installing SiteScope
SiteScope Failover Using Failover Manager (Cont.) – SiS Failover consists of the following components: • SiS Failover Manager server • Shared resources • Primary SiS server
The SiteScope Failover Solution Architecture SiS Failover consists of the following components: •
SiS Failover Manager Server manages and provides backup monitoring for multiple SiS instances when a primary SiS goes down. It is installed on a machine with access to the installation folder of the primary SiSs it is monitoring.
•
The Failover Manager creates a failover service (for Windows) or process (for UNIX) for each monitored SiS. When it detects that a primary SiS is down, it starts the service or process while continuing to monitor the other primary SiSs.
•
Shared Resource is a dedicated shared storage resource for the SiS installation folder. By placing the SiS installation folder on a shared resource, both the primary SiS and the SiS Failover use the same SiS configuration, log, and data files. This enables the Failover Manager to access and monitor the primary SiS. Multiple SiS installations can be stored on one or multiple shared resources.
•
Primary SiS server is a server with a typical SiS installation. The SiS installation has two run modes: •
Primary – Used when SiS is running normally
•
Failover – Used to support SiS Failover when the primary SiS goes down
Each mode writes data to a different heartbeat file on the SiS installation on the shared SiS installation.
The SiteScope Failover Implementation Process The figure on the slide illustrates the SiS Failover architecture with multiple SiS installations stored on one shared resource. The SiS failover process: •
Primary system is operational – Failover Manager monitors the availability of SiSs registered in the configuration file. It does this by checking for activity in the primary_heartbeat.log file in the \heartbeat folder on the shared resource for each SiS.
•
The primary SiS writes heartbeat events to the log according to a defined frequency (the default setting is every 15 seconds). This is the heartbeat indicator that the primary systems are running. You can modify the heartbeat frequency by changing the heartbeatFrequencyInSec value in the configuration files: On primary SiS: \conf\ha\primaryHAConfig.properties On Failover Manager: \ha\managerHAConfig.properties
•
Primary system goes down – Failover Manager reads the heartbeat events in the primary_heartbeat.log file to determine if the primary SiS is up or down. If no changes are detected in the last 5 minutes (the default setting), it determines that the primary server is down.
1-52
Module 1 - Installing SiteScope
•
Failover Manager is activated – After determining that a primary SiS is down, Failover Manager activates SiS Failover to run from the installation folder of the monitored primary SiS on the shared resource. This enables SiS Failover to act as a backup to the primary SiS, using the existing configurations from the primary SiS to monitor the environment. When the failover system is active, heartbeat events are written to the failover_heartbeat.log file which is created in the \heartbeat directory.
•
Primary system becomes operational again – When SiS Failover Manager detects that the primary SiS is ready to start, it disables the failover service/process and returns to standby mode. After the failover process has stopped, the primary SiS is started, and SiS Failover Manager reverts back to monitoring the availability of the primary SiS. While the SiS Failover Manager is freely available out-of-the-box, it still requires a separate Failover license in case the general license is node locked on the primary SiS server. This license is applied on the SiS Failover Manager when the primary SiS server is down.
1-53
Module 1 - Installing SiteScope
SiteScope Failover Using Failover Manager (Cont.) Monitoring Primary Availability
Monitoring Primary Availability The figure on the slide illustrates the concept of the automated failover operation. The figure represents normal operation with the primary SiS providing monitoring of the IT infrastructure and the failover in standby mode (monitoring the primary SiS heartbeat).
1-54
Module 1 - Installing SiteScope
SiteScope Failover Using Failover Manager (Cont.) Failover Transition
Failover Transition When SiS Failover Manager detects that a primary SiS is unresponsive, it activates the failover service. This enables backup monitoring using the existing configuration from the primary SiS.
1-55
Module 1 - Installing SiteScope
SiS Failover Using the Classic SiS Failover Solution – The SiS Classic Failover solution option is a special SiS build designed to mirror a primary SiS configuration to a failover machine.
– It requires two separate installations of SiS: • Primary • Secondary, running a special Failover build with a Failover license
SiS Failover Using the Classic SiS Failover Solution The classic SiS Failover solution was reinstated in SiS 11.11 as an alternative to using the SiS Failover Manager solution for providing automated failover functionality. To change SiS to classic SiS Failover mode, perform the following steps: 1. Open the SiS Configuration Tool (Start Programs HP SiteScope Configuration Tool). 2. In the Introduction screen, select the Change to classic SiS Failover mode check box, and then select Next. 3. The Change to classic SiS Failover mode screen opens. Select Next to complete the change to classic SiS Failover operation. 4. Open a web browser and direct it to open the SiS Failover instance. For example, http://localhost:8080/SiteScope. 5. In the left panel, select the Preferences context menu. 6. Select General Preferences. 7. In the Licenses section, click Select and then select SiS Failover (High Availability) license key file. 8. In the Preferences menu section, select Failover Preferences. 9. The Failover Preferences page opens. Enter the name or IP address and port of the primary SiS server and the login credentials. 10. Select Mirror Configuration Now to continue. SiS copies all the files over from the primary machine and restarts when the mirroring operation is complete.
1-56
Module 1 - Installing SiteScope 11. After the failover has restarted, refresh your web browser or redirect your browser to the SiS Failover address. If there are SiS user names and passwords defined on the primary SiS, enter the same user names and passwords to access the failover.
1-57
Module 1 - Installing SiteScope
SiS Failover Using the Classic SiS Failover Solution SiS Failover Internals
SiteScope Failover Internals To use SiS in classic SiS Failover mode, a valid SiS Failover license file is required. If you do not have a valid license file, you can submit a request to renew or upgrade your license using the HP License Key Delivery Service site. Note: Classic SiS Failover provides support for OM metrics integration. SiS Failover reports metrics to its Operations agent (not to the primary's agent). To enable classic SiS Failover support for OM event integration, perform the steps provided in How to Enable SiS to Send Events to HPOM or BSM in Using SiS in the SiS 11.10 online help, both for the primary SiS and for the SiS Failover.
SiteScope Configuration Tool – It is a convenient utility for making configuration changes to an existing deployment or moving configuration data from one SiS installation to another. – It can export SiS data, such as templates, logs, monitor configuration files, scripts, server certificates, and so forth from your current SiS for later import into SiS. – It can use this wizard to optimize SiS’s performance by making sizing changes in the Windows Registry keys, to change the ports assigned to SiS, and to install and uninstall the HP Operations Agent.
SiteScope Configuration Tool The Configuration Tool is available with SiS on Windows, Solaris, and Linux platforms. You can run the Configuration Tool using a command line or console mode in console mode in Solaris or Linux platforms. You must stop the SiS service before exporting or importing the data, and restart the service after exporting or importing the data. When moving configuration data from one SiS installation to another, make sure that SiS server from which you are taking configuration data is in the same time zone as the SiS server to which the data is being imported. When importing configurations to the same version of SiS, you must rename or delete all template example containers so as to import the new template examples. Support for including server certificates and scripts when exporting data was added to the Configuration Tool in SiS 11.10.
Running the Configuration Tool on Windows Platforms To run the configuration tool on the Windows platform, perform the following steps: 1. On the SiS server, select Start All Programs HP SiteScope Configuration Tool. The SiS Configuration Wizard opens. 2. Select the actions that you want to perform, and then select Next to continue: a. If you selected the Sizing option, the Sizing screen opens. The screen lists the parameters in the Windows Registry. Make the necessary changes. b. If you selected the Change ports option, the Change Ports screen opens. Make the necessary changes. c. If you selected the Import Configuration option, the Import Configuration screen opens. Make the necessary changes. d. If you selected the Export Configuration option, the Export Configuration screen opens. Make the necessary changes. e. If you selected the HP Operations Agent option, the Install/Uninstall HP Operations Agent screen opens. Make the necessary changes. The Summary screen opens, displaying the configuration status.
1-61
Module 1 - Installing SiteScope
SiteScope API – SiS API helps in managing dynamic enterprise environment SiS Object
SiteScope API SiS includes an API that supports the actions listed on the slide. Each API call can be run from a command line on a Windows or UNIX platform. To help manage dynamic large environments, such as those that exist in private clouds, SiS introduced an extended SOAP-based API that supports the actions listed below. Sample Java code for utilizing the API is available. Each API call can be run from the command line on a Windows or UNIX platform. SiS APIs enable you to run various scenarios automatically without using the SiS user interface. For example, you can create and deploy templates; enable and disable monitors, groups, and alerts; and delete monitors, groups, and remote servers. SiS Configuration API is a SOAP API that can be invoked by any known Web Services invocation framework, such as Axis or WSIF, or by any client application. Using an SiS login name and password, you can call APIs and perform configuration changes and various other actions. Some API operations can be disabled on the server. This supports a read-only mode, such that the configuration cannot be changed remotely using the API. SiS API examples are available from the
1-62
Introducing SiteScope Licensing – You should have a valid SiS license from HP Software to use SiS. – You can install SiS using a general license, or use the 60-day evaluation license that is available with each new installation of SiS. – You can also purchase extension licenses to enable the use of SiS solution templates and optional monitors.
Introducing SiteScope Licensing SiS licensing controls the number of monitors that can be run and, in some cases, the types of monitors that can be used. Unlike software that is sold based on the number of sites, seats, or users, SiS licensing is based on the monitoring requirements. This provides an efficient and flexible way to scale SiS to your environment. Purchasing an SiS license and registering your copy of SiS gives you important rights and privileges. Registered users can access technical support and information on all HP products and are eligible for free updates and upgrades. You are also given access to the HP Software Support Web site. Note: Not all monitors included in the Evaluation license are included when upgrading to a General license. After the evaluation period expires or the license is upgraded, monitors and solution templates that are not included in the General license are no longer available.
1-64
Module 1 - Installing SiteScope
License Types Different types of SiS licenses are: – General license – Evaluation license – OS Instance license – Failover license – Extension license
License Types The different types of SiS licenses are: •
General license – Enables the standard functionality of SiS, based on the number of monitor points included as part of the license. It does not include monitors that require an extension license. This license type can be temporary (time-based) or permanent.
•
Evaluation license – During the free evaluation period, enables the standard functionality of SiS and use of the following additional monitors — Microsoft Exchange (via the solution templates), SAP, Siebel, Web Script, WebSphere MQ Status. License type has fixed trial period of up to 60 days. Note: The trial period terminates immediately once a permanent or time-based license is purchased.
•
OS Instance license – System monitors can be licensed by the OS instance instead of points. This license type can be temporary (time-based) or permanent.
•
Failover license – While SiS Failover is freely available out-of-the-box, it still requires a separate Failover license in case the general license is node locked on the primary SiS server. This license is applied on the SiS Failover when the primary SiS server is down. This license type can be temporary (time-based) or permanent.
•
Extension license – Each extension license enables a specific solution template or an optional monitor type.
1-65
Module 1 - Installing SiteScope
Point System – The product license point system is used to enable the use of the different monitor types available in SiS. – The number of points purchased determine the total number of monitor instances and specific system performance metrics or counters you can monitor. – The number of points required vary according to monitor type and to the number of measurements being made per monitor instance.
Point System Licensing for monitor types is based on a point system. A permanent SiS license provides a number of points that you use to activate a combination of monitor types. The number of SiS monitors that you can create is based on two factors: •
Total number of monitor points you have purchased
•
Types of SiS monitors you want to use
The monitor types are divided into categories based on how many points you need to activate them.
1-66
Module 1 - Installing SiteScope
Purchasing Monitor Points – SiS monitor points are sold in sets of 50, 100, 500, and 2000 point blocks to provide flexibility in the deployment of monitors – For example, a block of 100 points enables you to set up various monitoring options: • 10 application monitors to watch five performance metrics each (10 x 5 = 50 points) • A combination of two URL sequence monitors that traverse 10 transaction steps each (2 x 10 = 20 points) • 30 1-point network service or server monitors (30 x 1 = 30 points)
Purchasing Monitor Points The same block of 100 points can also be used to set up: •
10 application monitors watching one metric each (10 x 1 = 10 points)
•
One URL Sequence monitor with five steps (5 points)
•
85 Network Service or Server monitors (85 points)
When you install SiS, it includes a free evaluation license. To use SiS beyond the evaluation period, you must request and activate a general license key for your copy of SiS.
1-67
Module 1 - Installing SiteScope
SiteScope 11 Licensing Highlights – – – – – –
License are managed by AutoPass Existing licenses need to be replaced with new ones License node locking issued by default New license-type, called the OS-based license, introduced Provides the best host selection algorithm Easy access to license usage report
SiteScope 11 Licensing Highlights SiS version 11 switched to the standard HP licensing technology AutoPass that provides customers quicker and automated license fulfillment using Webware. License keys from previous versions of SiS are not compatible with this version, so existing customers cannot reuse their license keys with this version. Instead, customers must replace their existing license keys and must get updated ones using Webware. License key delivery can be fulfilled automatically through http://webware.hp.com. Node-locking licenses are issued by default. It locks the license to a particular host, which prevents using the license on another server. SiS Version 11 introduced a new license-type, called the OS-based license. The idea is that with this license the user can monitor one server with select monitor types and an un-limited number of monitors. This is an 18-pack of system monitors (CPU, Memory, and other kinds of Windows Resource monitors). A user with one OS-based license can monitor one server with an unlimited number of instances of those monitors. This license is not based on points, therefore it does not consume any points. Also, those points are returned for the sake of other application-based monitors that are not on the list of 18. For customers who purchase OS Instance Advanced, a dedicated OS license key is provided. SiS allows unlimited system monitoring for the number of OS Instances licensed. This license is associated with the OS Instance Advanced SKU (Stock-Keeping Unit), which is shared between SiS and the OM agent.
1-68
Module 1 - Installing SiteScope The best host selection algorithm gives the customer the most value with the new OS license. SiS applies the available OS Instance Advanced licenses to the busiest servers, the ones with the greatest number of points consumed by supported monitors on the server. Points consumed by those monitor instances are freed, and can be used by other monitors that are not covered by the OS license. Point-based and OS-based licenses can coexist on the same SIS instance. You can apply both of them and SIS selects the best hosts for the OS-licenses, by selecting the hosts that are the most heavily-monitored, based on points. For example, if you have 2 hosts and one is using 10 points of monitors and the other has 5 points, SIS auto-selects the host with 10 points and applies the OS-based license to it. Also, the 10 points should be used only for the following: They should appear in the pointsusage reports but they should not count toward the customer’s total number of allowed points (assuming they are also using a points-based license, of course). So in addition to applying the OS-based license, SIS also auto-deducts 10 points from the number used. The License usage report is located under General Preferences. Here you can see all the hosts using the license-type, plus the points required, consumed and saved.
1-69
Module 1 - Installing SiteScope
OS Instance Advanced License – System monitors can be licensed according to OS Instances instead of points for the number of monitors used – SiS automatically applies the available OS Instance Advanced licenses to the busiest servers – To view details of the OS Instance license used, go to Preferences General Preferences Licenses
OS Instance Advanced License When an OS Instance Advanced license expires or is removed, all monitors belonging to hosts that had used the OS License start consuming points. This can lead to a situation where the number of license points used by SiS monitors exceeds the number of points available. In this event, SiS sends a message that it will shut down within 7 days. To avoid a SiS shutdown, you should add more license points or reduce the number of monitors being used. To add more points, contact the HP License Key Delivery Service, and request a new license.
1-70
Module 1 - Installing SiteScope
Adding SiteScope Licenses 1. From a Web browser, open the SiS instance you want to modify 2. Select Preferences General Preferences, and expand the Licenses pane 3. Enter the path to your SiS license file in the License file box 4. Click on the Import button 5. Restart SiS for the license to take effect
Adding SiteScope Licenses After you install SiS, you can add to your licensing at any time. For information on how to obtain a new or additional monitoring licenses, visit the HP License Key Delivery Service site (https://webware.hp.com/Welcome.asp). When you receive your license file from HP, import the license keys into SiS using the browser interface. After licenses have been successfully imported, information about the imported licenses is displayed in the licenses report table. This includes the license type, description, expiration date, and the total number of monitor points permitted by the license – for an OS Instance license you can also see the monitored host(s) the licenses are applied to and the number of points saved.
1-71
Module 1 - Installing SiteScope
SiteScope License Reports SiS General Preferences – Licenses
SiteScope License Reports Navigate to General Preferences in the SiS UI to view the License information. Note the 2 tables in the screenshot: •
The first table is the license table with basic information, such as license type and expiration date.
•
The second table shows any OS licenses and how many points saved. The OS license is applied to the most heavily-used hosts, which results in the greatest savings in points, which is one of the value adds of the new OS license.
1-72
Module 1 - Installing SiteScope
Review Questions Which type of SiS license enables the standard functionality of SiS and usage of the additional monitors, such as Microsoft Exchange (via the solution templates), SAP, Siebel, Web Script, WebSphere MQ Status? a. Failover License b. OS Instance License c. Evaluation License d. Extension license
Review Questions (Cont.) What is the correct path for viewing the details of the OS Instance license ? a. Licenses General Preferences Preferences b. Licenses Preferences General Preferences c. Preferences General Preferences Licenses d. General Preferences Licenses Preferences
Review This module covered the following topics: – SiS server and client system requirements for the Windows platform – SiS server sizing recommendations – SiS Capacity Calculator tool – Installation of SiS on windows-based machines – SiS Failover HA Solution – SiS Licenses • License Types • Point System • Purchasing Monitor Points • OS Instance Advance Licence • Adding SiS Licenses and License Reports
Module 1 - Installing SiteScope This page intentionally left blank.
1-78
Module 2 — Overview of the SiteScope GUI Objectives At the end of this module, you will be able to: •
Navigate through the SiS interface
•
Identify the various menus and tabs in the SiS interface
2-1
Module 2 - Overview of the SiteScope GUI
Accessing SiteScope – To access SiS, enter the SiS address in a web browser. – The default address is, http://localhost:8080/SiteScope – On a Windows platforms, you can also access SiS from the Start menu by clicking: Start Programs HP SiteScope Open HP SiteScope – The first time SiS is deployed, there is a slight delay during the initialization of the interface elements. – SiS opens the Dashboard view first, by default.
Accessing SiteScope The administrator account is the default account used when accessing SiS. This means that anyone requesting the server address and port number where SiS is running is, by default, logged in on the administrator account. To restrict access to this account and its privileges, edit the administrator account profile to include a user login name and password. SiS then displays a login dialog before SiS can be accessed. When viewing SiS from another machine, it is recommended to use a machine that has Java Runtime Environment 1.6.0_14 or later installed.
2-2
Module 2 - Overview of the SiteScope GUI
SiteScope User Interface Common Toolbar Context Toolbar Context Tree
SiteScope User Interface When you connect to an SiS, the SiS opens to the Dashboard view as shown in the slide. If you entered a user name to log on to SiS, it is displayed on the upper-right side of the window. The SiS window contains the following key elements: •
SiS common toolbar – Provides access to page options, documentation, and additional resources. This toolbar is located on the upper part of the window.
•
SiS context toolbars – Contains buttons for frequently-used commands in the selected SiS context.
•
SiS context tree – Enables you to create and manage SiS objects in a tree structure.
•
SiS context buttons – Provide access to the SiS Monitors, Remote Servers, Templates, Preferences, Server Statistics, and Diagnostic Tools.
2-3
Module 2 - Overview of the SiteScope GUI
SiteScope Common Toolbar UI Element
Description Enables you to select the following page options: • Add to Favorites – Enables you to add the current SiS view to your list of favorites in your browser. • Save Layout to User Preferences – Enables you to save the current view as the default layout for the specific SiS user. Enables you to access SiS Help. You can also see descriptions of user interface elements in most pages or dialog boxes. To activate this feature, click the Quick Help button in the specific page or dialog box, and rest the mouse pointer on the element box to display a ToolTip description. Click the Quick Help button again to make this feature unavailable. Logs you out of your SiS session.
SiteScope Common Toolbar The SiS common toolbar provides access to page options, documentation, and additional resources. This toolbar is located on the upper part of the window. You can customize your view of the monitor tree to list only those SiS elements with which you are working. You can also assign search/filter tags to your groups, monitors, reports, and alerts to further refine your selection. SiS enables you to change monitor configurations across multiple monitors, groups, or multiple SiSs using Global Replace.
2-4
Module 2 - Overview of the SiteScope GUI
SiteScope Context Toolbar Description New – Adds SiS objects (groups, monitors, alerts, remote servers, and templates) to the relevant tree. The objects that you can add depend on the context. Test – Tests the connection to the server. Note: Available in the remote server tree toolbar only. Detailed Test – Runs a test that displays the results of running commands on the remote server. This enables you to check the permissions for the defined user. Note: Available in the remote server tree toolbar for UNIX servers only Cut – Moves the selected object to another location in the tree. Copy – Makes a copy of the selected object. Paste – Copies or moves an object to the selected location in the tree. Delete – Deletes the selected object from the tree.
SiteScope Context Toolbar SiS context toolbars contains buttons for frequently-used commands in the selected SiS context. The tree toolbars enable you to perform common functions in the different SiS views. To access the toolbar, select the Monitors/Remote Servers/Templates context. The tree toolbar is displayed above the upper left pane. Note: The monitor tree represents the organization of systems and services in your network environment. The tree includes containers and objects within your infrastructure. The shortcut menu options include descriptions of the context menu options available for each object in the monitor tree.
2-5
Module 2 - Overview of the SiteScope GUI
SiteScope Context Toolbar (Cont.) Description Filter – Filters the monitor tree to display only those SiS objects that meet the criteria that you define. Select a filter option. – New Filter – Opens the New Filter dialog box, which enables you to create a filter. – Clear Filter – Clears the filter settings. – – Displays a list of existing filters. The following options are available: • Apply applies the filter to the left tree pane. • Edit opens the Edit Filter dialog box, which enables you to edit the filter. • Delete removes the filter from the filter list.
Note: Available in the monitor tree toolbar only.
Manage Monitors and Groups – Enables you to perform an action (copy, move, delete, run monitors, enable/disable monitors, enable/disable associated alerts) on multiple groups and monitors in the monitor tree. You can also filter the list of objects in the monitor tree. Note: Available in the monitor tree toolbar only.
SiteScope Context Toolbar (Cont.) Description Refresh – Refreshes the data in the tree. Collapse All – Collapses all branches in the tree. Note: Available in the monitor and template tree toolbar only. Expand All – Expands all branches in the tree. Note: Available in the monitor and template tree toolbar only. Show/Hide Pane – Shows or hides the tree, and expands or contracts the right pane. Click to configure the context button display – The following options are available: –Show More Buttons – Click to show the next highest ranking SiS context button in the left pane. This button is available only if not all the context buttons are displayed. –Show Fewer Buttons – Click to hide the lowest ranking SiS context button from the left pane. This button is available only if at least one context buttons is displayed. –Option – Choose the order in which the SiS context buttons are displayed. Use the Move Up and Move Down buttons to rearrange the order. To hide a button from the left pane, clear the check box for the context. By default, all the context buttons are selected (displayed in the left pane). –Add or Remove Buttons – Shows the show/hide status of the context buttons. 8
Description Enables you to create and manage SiS groups and monitors in a hierarchy represented by a monitor tree. Enables you to set up the connection properties so that SiS can monitor systems and services running in remote Windows and UNIX environments. Enables you to use templates to deploy a standardized pattern of monitoring to multiple elements in your infrastructure. You can use a preconfigured SiS solution template or create and manage your own templates. Enables you to configure specific properties and settings related to most of the administrative tasks within SiS. Enables you to view key SiS server performance metrics. Displays diagnostic tools that can help you troubleshoot problems in SiS and facilitate monitor configuration.
SiteScope Context Buttons SiS context buttons provide access to the SiS Monitors, Remote Servers, Templates, Preferences, Server Statistics, and Diagnostic Tools. SiS has the following contexts that are available from the left pane: •
Monitors
•
Remote Servers
•
Templates
•
Preferences
•
Server Statistics
•
Tools
2-8
Module 2 - Overview of the SiteScope GUI
Monitor Tree – The monitor tree represents the organization of systems and services in your network environment. – The tree includes containers and objects within your infrastructure. – The shortcut menu options include descriptions of the various context menu options that are available for each object in the monitor tree.
Monitor Tree The root node of the tree is the SiS container. Only one SiS node exists in the monitor tree. You add all other elements to the tree under the SiS node. You can search for objects in the monitor tree by selecting a node and typing the characters you want to search. You can perform mass operations on SiS objects using the Manage Groups and Monitors feature. It enables you to perform move, copy, delete, run monitors, enable/disable monitors, and enable/disable associated alert actions on multiple SiS objects in the monitor tree. You can also use the Filter options to create a filtered list of groups and monitors based on a filter criteria. Using the Manage Monitors and Groups dialog box, you can select one or more groups and monitors from an expandable hierarchical view of the organization, and select the action you want to perform.
2-9
Module 2 - Overview of the SiteScope GUI
SiteScope Monitor Tree Objects UI Element Description Represents an individual SiS server Parent – Enterprise node or container Add to tree by – Importing or adding an empty SiS profile Represents the SiS monitor group or subgroup (with enabled monitors/with no monitors or no enabled monitors). If an alert has been set up for the monitor group or subgroup, the alert symbol is displayed next to the group icon If a Management report has been set up for the monitor group or subgroup, the report symbol is displayed next to the group icon. Parent – SiteScope or SiteScope group Add to tree by – Creating, or importing with an SiS with defined groups.
SiteScope Monitor Tree Objects The monitor tree represents the organization of systems and services in your network environment. The tree includes containers and objects within your infrastructure. The shortcut menu options include descriptions of the context menu options available for each object in the monitor tree.
2-10
Module 2 - Overview of the SiteScope GUI
SiteScope Monitor Tree Objects (Cont.) UI Element Description Represents the SiS monitor (enabled/disabled). If an alert has been set up for the monitor, the alert symbol is displayed next to the monitor icon. If a Management report has been set up for the monitor, the report symbol is displayed next to the monitor icon. Parent – SiteScope group or subgroup, template, or solution template. Add to tree by — Creating, or importing with SiteScope that has monitors configured. Represents the collection of available health monitors that are deployed to check proper functioning of SiS monitors. Parent – SiteScope Add to tree by – Automatically added with SiS object.
SiteScope Remote Server Tree – The remote server tree represents the remote servers configured in your network environment. – The shortcut menu options include descriptions of the various context menu options that are available for each object in the remote server tree.
SiteScope Remote Server Tree Objects UI Element Description Represents the Windows/UNIX remote server container in the remote server view Represents a Windows/UNIX remote server Parent – Windows/UNIX Remote Server container Add by – Created in the Windows/UNIX Remote Server container or template tree
SiteScope Remote Server Tree Objects User interface elements for the Remote Servers Shortcut Menu Options are described in the following table:
Menu Item (A-Z)
Description
New Microsoft Windows/UNIX Remote Server
Opens the New Server window, which enables you to define a new Microsoft Windows or UNIX server.
Copy to Template
Copies the remote server to a template group.
Delete
Deletes the remote server.
Detailed Test
Enables you to test the running commands on the remote host and check the permissions for the defined user. Available for UNIX servers only.
Test
Enables you to test the connection to the remote server.
2-13
Module 2 - Overview of the SiteScope GUI
SiteScope Template Tree – The template tree represents the SiS solution template sets, template examples, Monitor Deployment Wizard templates, and user-defined templates that are available for deployment to monitor groups. – The shortcut menu options include descriptions of the various context menu options that are available for each object in the template tree.
SiteScope Template Tree Objects Description Represents a solution template container (available/unavailable). Only licensed solution templates that have the available icon are configurable solution templates. Parent – SiteScope. Represents a template container. A template container is used to organize configuration deployment templates. Parent – SiteScope. Add to template tree by – Creating or importing with SiS that has template containers defined. Represents a template configuration for deploying SiS objects. Parent – Template container. Add to template tree by – Creating. Represents a variable used as placeholder to prompt for input when deploying a template. Parent – Template. Add to template tree by – Creating.
SiteScope Template Tree Objects The SiteScope Template tree represents the SiS solution template sets, template examples, Monitor Deployment Wizard templates, and user-defined templates that are available for deployment to monitor groups. The Shortcut Menu Options include descriptions of the context menu options available for each object in the template tree.
Preferences Menu – The Preferences menu represents the preference types that enable you to configure specific properties and settings related to most of the administrative tasks available within SiS.
Preferences Menu The following are the preference types in SiS: •
General Preferences – Perform various post-configuration tasks, such as enter standard and optional SiS license keys, control display functions, and set security options
•
Infrastructure Preferences – Define the values of global settings that determine how SiS runs
•
Integration Preferences – Configure SiS as a data collector for BSM
•
Log Preferences – Control the accumulation and storage of monitor data logs
•
Email Preferences – Define email server settings and profiles for SiS email alert and status reports.
•
Pager Preferences – Configure settings and additional pager profiles that SiS uses for sending Pager alerts
•
SNMP Trap Preferences – Define settings that are used by SiS SNMP Trap alerts when sending data to management consoles
•
Common Event Mappings – Create event mapping instances between SiS runtime data and the event attribute values that are sent to the HPOM/BSM server
•
Schedule Preferences – Customize the operation of SiS monitors and alerts to run only at specific times or during specific time periods
•
User Management Preferences – Define and manage user login profiles that control how others access SiS
•
Credential Preferences – Create and manage credentials for SiS resources
2-17
Module 2 - Overview of the SiteScope GUI •
Search/Filter Tags – Manage the Search/Filter tags defined in SiS. You can assign tags to one or more items in the context trees and preference profiles, and then use the tags as an object for a filter.
•
Certificate Management – Add and remove server certificates and reload the key store, without having to restart SiS after each certificate change operation
2-18
Module 2 - Overview of the SiteScope GUI
Server Statistics Menu – The Server Statistics menu enables you to view an overview of several key SiS server performance statistics. – This includes: • The load on the SiS server • A list of currently running and recently run monitors as well as status data • The process manager summary and statistics for the pools • The SSH statistics and connection summary • The Telnet statistics and connection summary, and SiS log files
Server Statistics Menu To access the server statistics menu, select the Server Statistics context. The Server Statistics menu options are displayed in the left pane. Only an administrator, or a user granted the View server statistics permissions, can view the monitor performance data pages.
Server Statistics Page The following are the available monitor performance data options in SiS: •
General – Displays SiS server statistics, including the load on the SiS server (number of running monitors, waiting monitors, monitor runs per minute), and a list of running monitors by type
•
Running Monitors – Displays a list of which SiS monitors are running, and which monitors have run recently, at what time, and what was the returned status
•
Perfex Processes Pool – Displays the process manager summary, and pool statistics and status tables for each pool
•
SSH Connections – Displays Secure Shell (SSH) statistics and a summary of SSH connections when using SSH to connect to remote UNIX or Windows servers
•
Telnet Connections – Displays telnet statistics when using telnet to connect to remote UNIX or Windows servers
•
Log Files – Displays the list of log files in SiS that are useful for understanding SiS performance issues, for troubleshooting monitor and alert problems, and for reviewing SiS management actions
2-20
Module 2 - Overview of the SiteScope GUI
Tools Menu – Displays a list of diagnostic tools that can help you to troubleshoot problems in SiS and facilitate monitor configuration.
Tools Menu To view or use the tools in the Tools context in the left pane, you must be an administrator in SiS, or a user granted Use tools permissions. Some tools are also available when configuring or editing specific monitors (provided you are an administrator in SiS, or a user granted Use monitor tools permissions). If a tool is available when configuring or editing a monitor, you can access the tool by: •
Clicking the Use Tool button in the new monitor dialog box when configuring a new monitor, or in the monitor Properties tab when configuring an existing monitor.
•
Clicking the Tools button in the SiS Dashboard toolbar when running the test tool for an existing monitor. This opens and runs the tool with the monitor's existing data as its input, and displays test results in the Results pane.
To avoid character set problems when the SiS client uses a multibyte locale different from the SiS server, set the value in the master.config file for the _httpCharset setting to UTF8. By default, the _httpCharset value is empty, which means that the default server locale is used.
2-21
Module 2 - Overview of the SiteScope GUI
Review Questions Which key element in the SiS window provides access to the SiS monitors, remote servers, templates, preferences, server statistics, and diagnostic tools? a. SiS common toolbar b. SiS context toolbars c. SiS context buttons d. SiS context tree
Review Questions (Cont.) Which option of the SiS context toolbar runs a test that displays the results of running commands on the remote server? a. Manage Monitors and Groups b. Test c. Detailed Test d. Filter
Review Questions (Cont.) What enables you to view an overview of several key SiS server performance statistics? a. SiS Template Tree objects b. Preferences Menu c. Tools menu d. Server Statistics Menu
Review This module covered the following topics: – Accessing SiS and navigating the SiS user interface – Identifying various menus and tabs in the SiS interface, such as : • Common toolbar • Context toolbar • Context buttons • Monitor Tree Objects • Remote Server Objects • Template Tree Objects • Preference Menu • Server Statistic Menu • Tool Menu
Creating a Group The monitor tree represents the organization of systems and services in your network environment. The tree includes containers and objects within your infrastructure. The shortcut menu options include descriptions of the context menu options available for each object in the monitor tree. You can create groups according to the monitor hierarchy which you want to implement. For example, you can create groups of locations, server types, network resources, and so on. To access, select the Monitors context. The monitor tree is displayed in the left pane. The root node of the tree is the SiS container. Only one SiS node exists in the monitor tree. You can add all other elements to the tree under the SiS node. To create a new group, perform the following steps: 1. Select the Monitors context. 2. In the monitor tree, right click the SiS container or an existing monitor group, and select New Group. The New SiS Group dialog box enables you to define a new group for SiS, or a subgroup for an existing monitor group.
3-2
Module 3 - Monitoring Basics
Creating a Group (Cont.) New SiteScope Group – Add the Group name and Group description, as shown in the following figure:
New SiteScope Group Group name is a mandatory field here so you must enter a valid name. URL links can be added to Group description field, which is optional. You can add additional information to describe a group and include HTML tags for hyperlinks to enable you to access URLs from the SiS Dashboard. To add a hyperlink, perform the following steps: 1. Select a group, from the right hand side pane. It opens the Properties tab for the selected group. 2. In the New SiS Group window, expand the General Settings pane and enter the URL in the Group description field. For example, Advantage SiteScope. In SiS Dashboard, a URL is displayed in the Description field for the selected group. To open the URL, click the group’s Description field, and then click the link.
3-3
Module 3 - Monitoring Basics
Adding a Monitor 1. Right click the SiteScope Server group. 2. Choose New Monitor.
Adding a Monitor Monitor instances that you create must be added within a SiS monitor group container. You can use group containers to help you organize the monitor instances that you create. To create a new monitor instance, right-click the group into which you want to add the monitor instance and select New Monitor.
3-4
Module 3 - Monitoring Basics
Adding a Monitor (Cont.) New Monitor Page – Choose New Service monitor.
New Monitor Page Select the monitor you want to add from the New Monitor dialog box, and configure the settings for the specific monitor. The New Monitor dialog box displays two columns; first column displays all the monitor type names and the second displays the monitor category. By default, the monitor names are displayed in alphabetical order and if you click on the dropdown box on the second column heading, it lists all the available monitor categories. Once you select a category, it displays only the monitors belonging to that category.
3-5
Module 3 - Monitoring Basics
Adding a Monitor (Cont.) New Service Monitor – In the New Service Monitor page, enter the name spooler, choose the service Print Spooler, and click the Verify &Save button.
New Service Monitor Each monitor instance must have a name associated with it. The name describes the element or system being monitored. You should use a useful naming convention for all monitors to make creating view filters and category assignments more effective. Example: or You can also have additional information to describe a monitor. This can include the most common HTML tags for text styling, such as , , and . The description is displayed only when viewing or editing the monitor’s properties in the SiS Dashboard. Select the target server on which the monitoring is to be done from the dropdown box and enter other required details.
3-6
Module 3 - Monitoring Basics
Adding a Monitor (Cont.) Monitor Verification – The following dialog box should appear. Verify that the status is Good and click the OK button.
Monitor Verification The Verify & Save button verifies the correctness of the monitor configuration locally and on the remote server to be monitored, before saving the settings. If SiS fails to connect to the remote server, or if there is an invalid property in the configuration settings, verification fails and an error message is displayed. Performance is not as fast if you use Verify & Save instead of Save, because SiS needs to establish a connection to the remote server to verify the settings.
Run Time Settings After creating the monitor instance, if you want to change the configuration settings of the monitor, it can be done through the Properties tab. To do this, perform the following steps: 1. Select the Monitors context. 2. In the monitor tree, expand the group folder that contains the monitor, and select the monitor. 3. In the right pane, click the Properties tab, and select Monitor Run Settings. The following are the three monitor run settings displayed: •
Frequency – How often SiS attempts to run the action defined for the monitor instance. Each monitor run updates the status of the monitor. Use the drop down list to specify increments of seconds, minutes, hours, or days.
•
Error frequency – Monitoring interval for monitors that have reported an error condition. For example, you might want to run the monitor every 10 minutes normally, but as often as every 2 minutes if an error has been detected. When the monitor’s status is no longer in error, the monitor reverts to the run interval specified in the Frequency setting.
•
Verify error – Automatically runs the monitor again if it detects an error. It runs the monitor immediately after the regular run returned an error to make sure that the first error was not a false alert. If the error is returned again, it is reported as a result of the monitor run, and the next run takes place according to the monitor schedule.
3-8
Module 3 - Monitoring Basics Note: The status returned by the Verify error run of the monitor replaces the status of the originally scheduled run that detected an error. The data from the verify run may be different than the initial error status, causing the loss of important performance data. After making the monitor configuration settings, the changes need to be saved by clicking the Save button.
3-9
Module 3 - Monitoring Basics
Configuring an Alert 1. Right click on the Service Monitor you have just created. 2. Choose New Alert.
Configuring an Alert Alerts created for a specific monitor or group are displayed in the object’s Alerts on Monitor/Group list. Targeted monitors or groups are displayed in the Alerts Associated with Monitor/Group list. You can create a new alert or copy an existing alert into any group or monitor container in the SiS tree. To create a new alert, right-click the container to which you want to associate the alert, and select New Alert. If an alert has been set up for the monitor, the alert symbol is displayed next to the monitor icon.
3-10
Module 3 - Monitoring Basics
Configuring an Alert (Cont.) New Alert – Creating Alert Actions 1. Enter the name spooler failure and click on new action 2. Choose Action Type as Script.
New Alert – Creating Alert Actions In the New Alert dialog box:
1. Enter a name for the alert 2. Select the targets to trigger the alert 3. Configure an alert action (in the Alert Actions pane, click New Alert Action to start the Alert Action wizard).
For each alert scheme, you can create one or more alert actions. The user interface elements are as follows:
•
Name – Name for this alert definition. This name is used to identify this alert definition in the product display.
•
Alert Description – Description of the alert. This description does not appear in any other context. It appears only when editing the alert.
Use the Alert Action dialog box to define the settings that are specific to the alert type and to configure actions to be taken when an alert is triggered. In the Alert Actions section of the New/Edit Alert dialog box, click the New Alert Action button.
3-11
Module 3 - Monitoring Basics
Configuring an Alert (Cont.) Alert Action Settings
Alert Action Settings The Alert Action dialog box consists of three panes: •
Action Type Settings – The Action Type settings vary according to the type of alert action you selected in the Action Type Dialog Box.
•
Status Trigger – Use the Status Trigger pane to select the status of the object type that triggers an alert action. Alerts are triggered when the status changes from one state to another. Select the category that triggers the alert action.
•
Trigger Frequency – Use the Trigger Frequency pane to select the trigger frequency. The available options vary according to what you chose in the Status Trigger Pane.
Alert Settings The New Alert dialog box shows the name of the alert, alert target details, and the alert actions associated with the alert. An alert can have multiple actions associated with it. To save the alert, click the OK button.
Viewing the Dashboard SiS monitoring provides a real-time picture of system availability and performance. You can configure SiS monitors to collect metrics from a range of infrastructure components, including web, application, database, and firewall servers. The status and metrics are then aggregated for presentation in SiS Dashboard. The Dashboard is linked to the SiS monitor tree hierarchy. The data displayed in the Dashboard represents the selected context in the monitor tree. The highest level is the SiS node and any applicable monitor groups. The lowest-level element for display in a Dashboard view is an individual SiS monitor and its measurements. The Dashboard includes functions that you can use to customize the display of monitor information. This includes defining named filter settings to limit the display of data to those matching a defined criteria. You can also select various data display options. The Dashboard also includes hyperlinks and menus that you can use to navigate through the hierarchy of monitor elements, manually run a monitor, disable monitors, and access alert definitions.
3-14
Module 3 - Monitoring Basics
Creating a Report 1. Right click on the Spooler monitor. 2. Choose Reports Quick.
Creating a Report SiS can create reports for monitors or monitor groups that display information about how the servers and applications you are monitoring have performed over time. SiS offers a variety of reports from quick monitor reports to detailed management reports. Reports enable you to track trends and operational performance and to troubleshoot problems. To create a report: 1. Right-click the group or monitor container in which you want to create a report. Click Reports. Alternatively, you can create a new report from the Reports tab. 2. Select the report type you want to add or generate (only the Management report is added; all other reports are ad hoc and are not saved in SiS).
Quick Report Settings Quick reports are generated on an ad-hoc basis and are not saved to the SiS configuration data. To access the Quick Report settings, perform the following steps: 1. Select the Monitors context. 2. In the monitor tree, right-click the SiS node, a monitor group, or a monitor, and select Reports Quick. 3. Configure the report properties, and click Generate Report. Alternatively, you can create a report using preconfigured settings by selecting a monitor and clicking the Quick Report button in the SiS Dashboard.
3-16
Module 3 - Monitoring Basics
Quick Report Search the report for the following: – Service uptime – Current license capacity – Time in error
Quick Report This report displays the summary and specific details of infrastructure availability and performance data for monitors and monitor groups over a given period of time. Quick reports are generated on an ad-hoc basis and are not saved to the SiS configuration data.
3-17
Module 3 - Monitoring Basics
Review Questions How do you create a new monitor instance? Answer: To create a new monitor instance, right-click the group into which you want to add the monitor instance, and select New Monitor.
Review Questions (Cont.) What is the purpose of the Verify and Save button on the New Service Monitor page? Answer: The Verify and Save button verifies the correctness of the monitor configuration locally and on the remote server to be monitored, before saving the settings.
Review Questions (Cont.) How do you create a new alert? Answer: To create a new alert, right-click the container to which you want to associate the alert, and select New Alert.
Review Questions (Cont.) How do you create a report? Answer: To create a report, right-click the group or monitor container in which you want to create a report, and click Reports, or create a new report from the Reports tab. Select the report type you want to add or generate.
Review Questions (Cont.) What is a Quick report? Answer: Quick reports are generated on an ad-hoc basis and are not saved to the SiteScope configuration data. This report displays a summary and specific details of infrastructure availability and performance data for monitors and monitor groups over a given period of time.
Review This module covered the following topics: – Creating a group – Adding a monitor – Configuring an alert and taking a corrective action – Working with the dashboard – Generating a report
Activity Scenario 1: Creating a Group and a Monitoring with an Alert In this module, you create a group and a service monitor to monitor the Print Spooler service. You also need to create an alert along with the monitor to trace the status. When the Print Spooler service is not running, the monitor is triggered and the status is updated on the dashboard.
Monitoring Methodology Workflow Having a consistent methodology is essential for effective system monitoring. However, it is not always obvious how to approach, develop, and deploy an enterprise monitoring solution. The solution needs to consider the role of the IT infrastructure and how it contributes to the success of the organization. System monitoring is a tool used to ensure the availability and function of services used by the organization to meet its key objectives.
4-2
Module 4 - Planning and Designing a Monitoring Strategy
Business System Infrastructure Assessment – Gather technical and business requirements: • Identify business applications, servers and network devices, and heartbeat components
– Identify stakeholders and key deliverables for the monitoring activities: • Identify reports to generate, alert actions to take, and user access
– Identify the constraints of the monitoring system: • Identify restrictions on protocols and network traffic, and user authentication requirements
Business System Infrastructure Assessment You should gather technical and business requirements before making architectural and deployment decisions. Actions for this stage include: •
Develop a list of all business applications to be monitored. This task should consider end-to- end services, such as order processing, account access functions, data queries, updates, and reporting.
•
Develop a list of servers that support the business applications. This task must include servers supporting front-end web interfaces, back-end databases, and applications servers.
•
Develop a list of network devices supporting the business applications. This task includes network appliances and authentication services.
•
Identify heartbeat elements to be monitored. Heartbeat elements are services that act as foundational indicators of the availability of a particular business system or resource.
•
Outline templates of monitors. These templates represent the resources to be monitored for each system.
•
Identify stakeholders and key deliverables for the business system monitoring activity. Deliverables include: •
What reports should be generated
•
What alert actions should be taken when events are detected
•
To whom should the alerts be sent
•
What users require access to view and manage SiS
4-3
Module 4 - Planning and Designing a Monitoring Strategy
•
•
What SiS elements need to be accessible to which stakeholders
•
What are the thresholds for any Service Level Agreements (if applicable)
Understand the constraints within which the system monitoring function must operate. This task includes restrictions on the protocols that can be used, user authentication requirements, access to systems with business sensitive data, and network traffic restrictions.
4-4
Module 4 - Planning and Designing a Monitoring Strategy
Plan for System Monitoring What to monitor? – What should you monitor? • Individual server components • Individual software elements • Key services and processes • Transactions and business processes
– Sources of information: • System architecture diagrams • Schematics – Physical and logical implementation diagrams • Details of service names, port numbers, protocols, log file locations and signatures/patterns of error conditions
Plan for System Monitoring What to Monitor? Effective enterprise system management uses a multi-tiered monitoring approach. SiS gives you the tools to implement this. At one level, you want to monitor individual hardware elements in the infrastructure to see that they are running and available. You want to add to this monitoring of key services and processes on these systems. This includes low level operating system processes as well as processes indicating the health and performance of key applications. On top of this, you want to create transactional monitoring of business processes to see that key applications and services are available and function as expected.
4-5
Module 4 - Planning and Designing a Monitoring Strategy
Plan for System Monitoring (Cont.) Monitor Thresholds – What determines a failure? • Threshold-based metrics on the system or business process you are monitoring • The appearance of a line in a log file • The absence of a process or a service
Pick a signal that is the most reliable and consistent indicator of a problem. Eliminate false-positives. – Sources of Information: • System-level tolerances, as defined by your organization • Application resource thresholds from developers • Signatures/patterns of errors in log files from developers
Monitor Thresholds The threshold is based on the nature of the system or business process you are monitoring. For instance, if you are monitoring a CPU, acceptable thresholds are 60%-90%, which means that a utilization of under 60% results in a Good status, anything above 60% but lower than 90% results in a Warning status, and whenever the CPU gets to over 90%, set its status to Error. The availability and performance of information systems is critical to enterprise business success. The correct threshold set on different conditions like error, warning, or normal make the monitors set their status accordingly and take subsequent actions on it like triggering the alerts. Also, based upon the threshold set on the monitors only, the status color indication is reflected on the dashboard, which gives a quick glance on the current system status.
4-6
Module 4 - Planning and Designing a Monitoring Strategy
Plan for System Monitoring (Cont.) Monitor Schedule – How often must the system be checked? • Every day, every hour, every 10 minutes, and so on
Frequency of monitoring depends upon the entity being monitored and the tolerance level associated with its failure. Select the largest tolerable interval. – Sources of Information: • SLA documents • Implied user commitments • Application requirements documents
Monitor Schedule How often you have a system checked can be as important as the event threshold you set. The availability of mission critical information systems should be checked regularly during the periods that these are to be accessible. In many cases, systems need to be available 24 hours a day, 7 days a week. You can control how often SiS checks a system with the frequency setting for each monitor. Avoid too high a frequency that overloads the system. For instance, there is no need to frequently check the size of disks of a system with low I/O activity. Set the frequency of the Disk Monitor to once every couple of hours. On the other hand, avoid too low a frequency that delays the detection of problems. For instance, frequently check the responsiveness of your e-commerce web site because it is critical to the profitability of the business you are monitoring.
4-7
Module 4 - Planning and Designing a Monitoring Strategy
Plan for System Monitoring (Cont.) Monitor Actions – What actions are to be taken when an event is detected? • When corrective
action is possible, SiS attempt must be made to rectify the problem • Use SiS e-mail or pager alerts, script alerts, and SNMP traps for notifications
– Sources of information: • Developers: – Corrective action for application tiers • System administrators: – Corrective action for system issues • Database administrators: – Corrective action for database issues
Monitor Actions As a monitoring application, SiS provides you with the tools to detect problems. You use SiS alerts to send timely notifications when an event threshold has been triggered. An email notification is a commonly used alert action. SiS includes other alert types that can integrate with other systems. You can develop an alert escalation scheme by defining multiple alert definitions with different alert trigger criteria. You can use the alert configuration for alerts to customize the relation between detected events and alert actions. Another event action used might be to disable monitoring and alerting for systems that depend on a system that has become unavailable. You can use SiS group and monitor dependency options to avoid a cascading series of alerts. When problems are detected, an automated response to resolve the problem is ideal. While this is not possible for all systems, the SiS Script Alert type does provide a flexible and powerful tool for automating corrective actions for a variety of situations. You should consider what problems can arise in your environment that could be addressed with an automated response. You can use SNMP traps to provide integration with external systems. You can use SiS SNMP trap alerts to update an SNMP server for the network events. So you can use this method to provide integration with other HP Software products or third-party systems, such as Tivoli.
4-8
Module 4 - Planning and Designing a Monitoring Strategy
Set Up Heartbeats and Dependencies – Heartbeat: • A key monitor that verifies the availability of a business system or resource: – Example: • Lightweight monitor, such as Ping or Port • Low execution frequency • Prevents a flood of alerts when access to the resource fails: – Example: • Consider an App Server with multiple monitors. If the server goes offline, all monitors fail triggering a flood of alerts. • Set up a heartbeat monitor, such as a Ping monitor, which disables all other App Server monitors when it fails and triggers just one alert.
Set Up Heartbeats and Dependencies To prevent redundant alerting from multiple monitors that are monitoring different aspects of a single system, select one monitor to check the basic availability of the system and then activate other monitors that perform more detailed tests of that system. This creates a dependency relationship that enables you to make the running of a monitor group dependent on the status of a selected monitor. For example, a port monitor, which ensures the availability of the oracle communication port, can be used as a dependency monitor to run an oracle database monitor. You can use the Depends On option to make the running of one monitor dependent on the status of another monitor. This can be used to prevent redundant alerting from multiple monitors that are monitoring different aspects of a single system. You can create a simple system monitor to check the basic availability or heartbeat of a system and then create other monitors that perform more detailed tests of that system. This helps the monitoring team to handle alert flooding.
4-9
Module 4 - Planning and Designing a Monitoring Strategy
Set Up Heartbeats and Dependencies (Cont.) – Dependency: • The ability to control the execution of a monitor or a group of monitors is based on the state of another monitor or group of monitors. • Dependencies are used together with heartbeats to help prevent monitor error floods and alert floods.
You can make a monitor depend on the status of another monitor by using the Depends on option in the monitor configuration setting. It helps to select the status category or condition that the Depends on monitor should have for the current monitor to run normally. The status categories include: •
Good
•
Error
•
Available
•
Unavailable
The monitor being configured is run normally as long as the monitor selected in the Depends on box reports the condition selected in this box. If you have selected Unavailable and the Depends on monitor reports this status, the current monitors are not disabled. For example, by selecting Good, this monitor is only enabled as long as the monitor selected in the Depends on box reports a status of Good. The current monitor is automatically disabled if the monitor selected in the Depends on box reports a category or condition other than the condition selected for this setting.
4-10
Module 4 - Planning and Designing a Monitoring Strategy
Develop a Grouping Model – A Grouping Model is the approach used to create hierarchies of groups, monitors, alerts, and the dependencies that link them. – Best practice recommendations: • Understand what needs to be monitored and who to notify in the event of a failure • Leverage guidelines for creating an effective grouping model • Implement a top-level grouping model, heartbeats, and dependencies
Develop a Grouping Model A group is a collection of one or more monitors. It might contain several of one type of monitor, such as URL monitors, or several different monitors that track a specific part of your web environment, such as a Web server, URL, and network parameters related to a specific transaction. You create group containers to manage the deployment of monitors and associated alerts for your environment and organization. It is also useful to group monitors that should generate similar alerts. A proper grouping strategy minimizes the number of top-level groups and helps to manage the alerts as per the organizational structure. Each SiS monitor instance that you create must belong to a SiS group, either a top-level group or a subgroup nested within other group containers. While creating a grouping model, adhere to the following principles: •
The model is extensible in the sense that it easily accommodates the addition of new groups and monitors.
•
The model represents logical parent-child relationships between the monitored assets.
•
The model implements a well-defined naming convention for groups, subgroups, monitors, and any other monitoring objects.
•
The complexity of the grouping hierarchy decreases when moving from the top level to lower levels.
4-11
Module 4 - Planning and Designing a Monitoring Strategy
Top-level Grouping Advantages – The top-level grouping model accomplishes the following: • Alerts are sent to the right system and business owners • The SiteScope Dashboard is well organized and easy to navigate: – Offers few top-level groups – Displays pyramid-like structure • Problem areas and root causes are identified more easily • Easier incremental addition of groups and monitors
A well designed grouping model reduces alert flooding and sending the alert to non-intended stake holders and owners. Usually the grouping structure is in accordance with the organizational structure and hierarchy.
4-12
Module 4 - Planning and Designing a Monitoring Strategy
Top-level Grouping Model Example The figure on the slide shows an example of a grouping model with three top-level groups: Application Monitors, Server Monitors, and Heartbeat Monitors. The Server Monitors group contains four subgroups for different types of servers. These subgroups contain individual monitors for the server and a child group for shared services. The child group contains the applicable monitors for the targets to be monitored. The three top-level groups represent a logical organization of monitors implemented in the given SiS installation. These groups are organized as: •
Application Monitors – Contains monitors and groups targeting the high-level business applications and services of the organization.
•
Server Monitors – Groups specific types of server resource monitors organized by platform or vendor.
•
Heartbeat Monitors – Contains key processes and services that indicate the availability and health of a larger set of systems and services.
4-13
Module 4 - Planning and Designing a Monitoring Strategy
Review Questions Which task in the Monitoring Methodology workflow comes after “Set up SiteScope alerts” task? a. Configure your servers for the monitoring environment b. Set up and organize your SiS monitors c. Determining alerting expectations and media d. Identify your reporting requirements
Module 4 - Planning and Designing a Monitoring Strategy
Review Questions (Cont.) ___________ is a key monitor that verifies the availability of a business system or resource? a. Shared b. Heartbeat c. Server d. Application
Module 4 - Planning and Designing a Monitoring Strategy
Review Questions (Cont.) A ___________ is the approach used to create hierarchies of groups, monitors, alerts, and the dependencies that link them? a. System Monitoring b. Grouping Model c. Dependencies d. Business System Infrastructure Assessment
Module 4 - Planning and Designing a Monitoring Strategy
Review Questions (Cont.) Which of the following is included in the “Gather technical and business requirements before making architectural and deployment decision” while doing Business System Infrastructure Assessment? a. Generate a repot b. Develop a list of network devices supporting the business
applications c. Alert actions to be taken when events are detected d. Develop list of SiS elements to be accessible to stakeholders
Module 4 - Planning and Designing a Monitoring Strategy
Review This module covered the following topics: – Overview of the monitoring methodology workflow – Assessment of the business system infrastructure – Planning for system monitoring, which involves the following: • What to monitor? • Monitor thresholds • Monitor Schedule • Monitor Actions
– Setting up heartbeats and dependencies – Overview of developing a grouping model and best practice recommendations
Module 4 - Planning and Designing a Monitoring Strategy This page is intentionally left blank.
4-20
Module 5 — Configuring Groups and Monitors Objectives At the end of this module, you will be able to:
• • • •
Create and configure groups Work with groups Describe SiS Monitors Work with monitors to: • Configure remote servers • Configure monitor settings • Use baselines
Groups – Overview – Groups contain monitored assets – Groups can be added within other groups to form a hierarchy – Working with groups involves the following tasks: • Creating a group • Adding monitors to a group • Configuring alerts for a group • Setting up group reports • Copying/moving a group • Deleting a group
Groups – Overview A group is a collection of one or more monitors. A group can contain several similar types of monitors, such as URL monitors, or several different monitors that track a specific part of your web environment, such as a Web server, URL, and network parameters related to a specific transaction. For example, if you intend to monitor a large number of processes running on your system, you might want all of them to be in a single group named Processes. If you are monitoring processes on several machines using remote monitors, you could create a primary group called Processes with several subgroups named after each of the remote machines that you are monitoring. When you add a new monitor, you either add it to an existing group, or you must first create a group for it. You can add groups individually to SiS, or you can deploy groups along with multiple monitors by using templates.
Creating a Group You can create groups according to the monitor hierarchy which you want to implement. For example, you can create groups of locations, server types, network resources, and so on. To create a new group, right-click the SiS or group container in which you want to create the group and select New Group.
Creating a Group – Group Details Page The New SiteScope Group dialog box enables you to define a new group for SiS, or a subgroup for an existing monitor group. The following elements are found throughout the New SiteScope Group dialog box: •
Group Name – The name that describes the content of the group. The group name is case sensitive. This means that you can have more than one group with the same name provided they each have a different case structure. Note: The Group name cannot be SiteScope or contain any of the following characters: ‘ ; & | < > / \ + =.
•
Group Description – Additional information to describe a group, including HTML tags for hyperlinks to enable you to access URLs from the SiS Dashboard. The description is displayed only when viewing or editing the group’s properties in the SiS Dashboard.
•
Source Template – The path of the source template if the group was created from a template. If you are using deployed templates created in older versions of SiS, it enables you to manually associate the root groups with the source template by entering the path of the source template.
•
Depends On – The monitor on which you want to make the running of this monitor group dependent. You can set group dependencies to make the running of monitors in this group dependent on the status of another monitor.
•
Depends Condition – The condition that the Depends on monitor should have for the current monitor group to run normally. If the selected condition is not satisfied then the monitor selected in the Depends on box is automatically disabled.
5-5
Module 5 - Configuring Groups and Monitors The conditions are:
•
•
Good
•
Error
•
Available
Search/Filter Tags – Keyword tags used to search and filter SiS objects (groups, monitors, remote servers, templates, and preference profiles). If no tags have been created for the SiS, this section appears but is empty. If tags have been created, they are listed here and you can select them as required.
5-6
Module 5 - Configuring Groups and Monitors
Working with Groups – You can copy or move existing groups to new locations within the SiS tree. – You can delete groups from the SiS tree. Note: You cannot delete a monitor group if it has dependent alerts or reports at the container level.
Working with Groups In addition to creating groups, you can copy or move existing groups to a new location within the SiS tree. Copying or moving a group duplicates the configuration settings for the group and all monitors within the group. After copying or moving a group, you need to edit the group and the configuration properties for each individual monitor within the group to direct the monitors to a unique system or application. Otherwise, the monitors in the group duplicate the monitoring actions of the original group. To create a group by copying or moving an existing group: 1. Right-click the group you want to copy or move and select Copy or Cut. 2. Right-click the location in the monitor tree where you want to copy or move the group container, and select Paste. Note: Instead of copying groups, which can lead to redundant monitoring, it is recommended that you use templates to more efficiently replicate common group and monitor configuration patterns. Using templates for monitor replication is helpful in avoiding redundant monitoring You cannot delete a monitor group if it has dependent alerts or reports at the container level. To delete a monitor group with dependencies, you must remove the monitor group from Alert Targets and Report Targets for each dependency, and then delete the monitor group. You can delete monitor groups that have dependencies at the child level.
SiteScope Monitors — Overview – SiS monitors are tools used for automatic connections and querying of various systems and applications. – SiS monitors are grouped into categories that reflect their functions. – SiS monitors are also grouped into classes that reflect their capabilities depending on the deployed license. – SiS monitor instances created must be added to a SiS monitor group container.
SiteScope Monitors – Overview SiS monitors are tools for automatically connecting to and querying different kinds of systems and applications used in enterprise business systems. The different monitor types provide the generic capabilities for performing actions specific to different systems. You can create one or more instances of a monitor type to instruct SiS how to monitor specific elements in your IT infrastructure. For example, you can create 100 monitor instances that instruct the SiS CPU Monitor type to connect to and measure CPU utilization on remote servers. Each monitor instance contains a different setting defining which remote server is to be monitored and how often. SiS is then configured to automatically monitor the CPU utilization on 100 servers at regular intervals. Monitor instances that you create must be added within a SiS monitor group container. You can use group containers to help you organize the monitor instances that you create. SiS monitor categories are grouped according to classes that indicate their availability and category that reflect their function. When you select to add a new monitor to a SiS agent, the list of available monitor types for that agent are displayed both alphabetically and divided by category in the product interface. The availability of the monitor category is dependent on the class of monitor. The various monitor categories are: •
Standard Monitors – Represents the monitor types available with a general SiS license. These monitors include many of the general purpose monitors.
•
Integration Monitors – This group of optional monitor types are used to integrate HP products with other commonly used Enterprise Management systems and applications. These monitor types require additional licensing and may only be available as part of another HP product.
5-10
Module 5 - Configuring Groups and Monitors •
Solution Template Monitors – These monitor types are a special class of monitors that enable new monitoring capabilities for specific applications and environments.
5-11
Module 5 - Configuring Groups and Monitors
Solution Template Monitors – SiS solution templates are preconfigured monitor set templates designed to monitor popular enterprise applications and network systems. – SiS solution templates help in rapidly deploying a combination of standard SiS monitor types and solution-specific monitors. – SiS solution templates are set to optimize the monitoring of the availability, performance, and health of the target application or system: • For example, the solutions for Microsoft Exchange monitoring include performance counter, event log, and Exchange application-specific monitor types.
Solution Template Monitors Solution template monitor types enable new monitoring capabilities for specific applications and environments. As part of a solution template, these monitor types are deployed automatically together with other, standard monitor types to provide a monitoring solution that incorporates best practice configurations. These monitor types are controlled by option licensing and can only be added by deploying the applicable solution template. After they have been deployed, you can edit or delete them using the same steps as with other monitor types. The monitor types using solution templates include: •
Active Directory (with and without Global Catalog)
•
HP Service Manager
•
Microsoft Exchange
•
Microsoft IIS Server
•
Microsoft Lync Server
•
Microsoft SQL Server
•
Microsoft Windows Resources
•
Oracle Database
•
SAP Application Server
5-12
Module 5 - Configuring Groups and Monitors •
Siebel Application/Gateway/Web Server (for UNIX and Windows)
•
UNIX Resources
•
VMware Host CPU/Memory/Network/State/Storage
•
WebLogic and WebSphere Application Server
5-13
Module 5 - Configuring Groups and Monitors
Monitoring Remote Servers – To monitor certain server-level parameters on a remote server using the network file system services, you must create a remote server profile. – The remote server profiles contain the address and connection information that SiS requires to perform its activities. – The remote connection profile is then used to set up monitors for monitoring the remote servers.
Monitoring Remote Servers Some SiS monitors use Internet protocols to test web systems and applications. Other SiS monitors use network file system services and commands to monitor information on remote servers. Monitoring remote Windows servers requires: •
SiS for Windows XP/2000/2003/2008. In general, SiS for UNIX cannot monitor remote Windows servers.
•
The SiS service must run in a user or administrative account that has permission to access the Windows Performance registry on the remote servers to be monitored.
To monitor certain server-level parameters on a remote server using the network files system services, you must create a remote server profile. A table of server profiles is listed on the Microsoft Windows/UNIX Remote Server page in the remote server view. The remote server profiles contain the address and connection information that SiS needs to make a remote connection. After creating remote server profiles, set up monitors to use the remote connection profile. The requirements for monitoring services and applications that are running on remote servers vary according to the application and network policies in your environment. Note: To add a Microsoft Windows remote server, right-click the Microsoft Windows Remote Servers container, and select New Microsoft Windows Remote Server. To add a UNIX remote server, right-click the UNIX Remote Servers container, and select New UNIX Remote Server.
Creating a Monitor – Monitor Types Select the monitor you want to add from the New Monitor Page, and configure the settings for the specific monitor. You can enter a monitor name in the Quick Search box to find a specific monitor type. SiS monitor categories are grouped according to classes that indicate their availability and category that reflect their function. When you select to add a new monitor to an SiS agent, the list of available monitor types for that agent are displayed both alphabetically and divided by category in the product interface. The availability of the monitor category is dependent on the class of monitor.
Creating a Monitor – New Monitor Page The New Monitor dialog box enables you to define a new monitor in a monitor group. To access New Monitor dialog box, select the Monitors context: •
For new monitors: In the monitor tree, right-click a group, select New Monitor, and select a monitor from the New Monitor dialog box.
•
For existing monitors: In the monitor tree, expand the group folder that contains the monitor, and select the monitor. In the right pane, select the Properties tab. You can configure the properties that affect the monitor instance through this page.
5-17
Module 5 - Configuring Groups and Monitors
Modifying Monitor Settings The Properties tab of the monitor page has: – General settings – Monitor run settings – Dependencies – Threshold settings – Enable/Disable monitor – Enable/Disable associated alerts – Baseline settings – Search/Filter tag – HP Integration Settings
Modifying Monitor Settings The common monitor settings enable you to configure settings for a new monitor. The available sections in the Properties tab are: •
General Settings – Create a name and description for the monitor instance
•
Monitor Run Settings – Configure settings for the monitor to run
•
Dependencies – Create a dependency relationship that enables you to make the running of this monitor dependent on the status of another monitor.
•
Threshold Settings – Set conditions that determine the reported status of each monitor instance. The status result is based on the results or measurements returned by the monitor action on the target system during a specified period of time.
•
Enable/Disable Monitor – Sets the status (enabled/disabled) for the selected monitor
•
Enable/Disable Associated Alerts – Set the status (enabled/disabled) for associated alerts
•
Search/Filter Tag – Adds a new search/filter tag, and assigns the tag to objects in the context tree and preference profiles
•
Baseline Settings – Displays the baseline status for the selected monitor
•
HP Integration Settings – Control what data a monitor forwards to the applications integrated with SiS
5-18
Module 5 - Configuring Groups and Monitors
Modifying General Settings – The General Settings pane enables you to create a name and description for the monitor instance. – The user interface elements of the General Settings pane are as follows: • Name – Enter the name of the monitor. • Monitor description – Enter a description for the object that appears only when editing or viewing its properties. • Report description – Additional description of the monitor that appears on reports and in the monitor popup information (optional).
Modifying General Settings The General Settings pane enables you to create a name and description for the monitor instance. The user interface elements in this pane are: •
Name – Enter a name that describes the element or system being monitored. Use a useful naming convention for all monitors to make creating view filters and category assignments more effective. Example : or
•
Default Value – SiS creates a default name based on the host, system, and/or URL being monitored or the default name defined for the monitor type.
•
Monitor Description – Additional information to describe a monitor. This can include the most common HTML tags for text styling, such as , , and . The description is displayed only when viewing or editing the monitor’s properties in the SiS Dashboard.
•
Report Description – Optional description for this monitor to make it easier to understand what the monitor does. This description is displayed on each bar chart and graph in Management Reports.
5-19
Module 5 - Configuring Groups and Monitors
Monitor Run Settings – The user interface elements of the Run Settings are as follows: • Frequency – How often SiteScope attempts to run the action defined for the monitor instance • Error frequency – Monitoring interval for monitors that have reported an error condition. • Verify error – Automatically runs the monitor again if it detects an error. • Monitor schedule – Range schedule if you want the monitor to run only on certain days or on a fixed schedule. • Show run results on update – Whenever a change is made to a monitor’s configuration settings, the monitor is run.
Monitor Run Settings The user interface elements in this pane are:
•
Frequency – Describes how often SiS attempts to run the action defined for the monitor instance. Each monitor run updates the status of the monitor. Use the drop-down list to specify increments of seconds, minutes, hours, or days. Default value – 10 minutes Minimum value – 15 seconds Note: When configuring this setting in a template, the variable value can only be in time units of seconds.
•
Error frequency – Monitoring interval for monitors that have reported an error condition. For example, you might want to run the monitor every 10 minutes normally, but as often as every 2 minutes if an error has been detected. When the monitor’s status is no longer in error, the monitor reverts to the run interval specified in the Frequency setting. Note: Increasing the monitor run frequency affects the number of alerts generated by the monitor. When configuring this setting in a template, the variable value can only be in time units of seconds.
•
Verify error – Automatically runs the monitor again if it detects an error. It runs the monitor immediately after the regular run returned an error to make sure that the first error was not a false alert. If the error is returned again, it is reported as a result of the monitor run, and the next run takes place according to the monitor schedule.
5-20
Module 5 - Configuring Groups and Monitors Note: You should use this option in small monitoring environments only. Significant monitoring delays can result if multiple monitors are rescheduled to verify errors at the same time. The status returned by the Verify error run of the monitor replaces the status of the originally scheduled run that detected an error. The data from the verify run may be different than the initial error status, causing the loss of important performance data.
•
Monitor schedule – Range schedule if you want the monitor to run only on certain days or on a fixed schedule. The range schedules created in Schedule Preferences appear in the drop-down list. Default value – every day, all day Note: If you select a threshold schedule in the Threshold Settings, at least one threshold schedule must coincide with the monitor run schedule (at least one minute of the monitor run schedule must be covered by one of the threshold schedules).
•
Show run results on update – When a change is made to a monitor’s configuration settings, the monitor is run. Displays the results of that monitor run in a popup dialog box. Note: The updated run results are always displayed in the applicable Dashboard views for the monitor.
5-21
Module 5 - Configuring Groups and Monitors
Editing Monitor Dependencies – The Dependencies pane enables you to create a dependency relationship, where running of a monitor depends on the status of another monitor.
Editing Monitor Dependencies The Dependencies pane enables you to create a dependency relationship that enables you to make the running of this monitor dependent on the status of another monitor. User interface elements of dependencies are: •
Depends on
•
Depends condition
5-22
Module 5 - Configuring Groups and Monitors
Editing Monitor Dependencies – Depends On Dependency relationship
Editing Monitor Dependencies – Depends On You can use this option to make the running of a monitor depend on the status of another monitor. This can be used to prevent redundant alerting from multiple monitors that are monitoring different aspects of a single system. You can create a simple system monitor to check the basic availability or heartbeat of a system and then create other monitors that perform more detailed tests of that system. You can make monitors depend on the status of the heartbeat monitor by selecting that monitor. This means the dependent monitors run as long as the dependency condition is satisfied. If the heartbeat monitor detects that the target system has become unavailable, the dependency relationship automatically disables the other monitors. This has the effect of disabling any alerts that would have been generated by those monitors. You can select the Depends on button to open the Select Depends On Monitor dialog box, and select the monitor on which you want to make the running of this monitor dependent. For example, you can create a system monitor to check the basic availability of a system and then create other monitors that perform more detailed tests of that system. Set the detailed test monitors to be dependent on the status of the monitor checking basic availability. If the system monitor detects that the target system has become unavailable, the dependency relationship automatically disables the other monitors. This also disables any alerts that would have been generated by the dependent monitors. Default value – No dependency is set for a monitor instance.
5-23
Module 5 - Configuring Groups and Monitors
Editing Monitor Dependencies – Depends Condition – The monitor being configured runs normally as long as the monitor selected in the Depends on box reports the condition selected in the Depends condition box. – The status categories include: • Good • Error • Available • Unavailable
Editing Monitor Dependencies – Depends Condition If you make a monitor dependent on the status of another monitor (by using the Depends on setting), you should use this option to select the status condition of the Depends on monitor for the current monitor to run normally. The status categories include: •
Good
•
Error
•
Available
•
Unavailable
The monitor being configured is run normally as long as the monitor selected in the Depends on box reports the condition selected in this box. For example, select Good and this monitor is enabled only when the monitor selected in the Depends on box reports a status of Good. The current monitor is automatically disabled if the monitor selected in the Depends on box reports a category or condition other than Good. You can also enable dependent monitors specifically for when a monitor detects an error. Default value – Good
5-24
Module 5 - Configuring Groups and Monitors
Threshold Settings – Threshold settings are the performance boundaries that enable you to organize performance data in a meaningful way. – Threshold settings allow you to configure logical conditions that determine the reported status of each monitor instance. – Threshold status is based on the results or measurements returned by the monitor action on the target system compared to the thresholds set for the monitor.
Threshold Settings You can use the Threshold Settings section to set logic conditions that determine the reported status of each monitor instance. The status is based on the results or measurements returned by the monitor action on the target system as compared to the thresholds set for the monitor. In the Threshold Settings tab, you can manually set logic conditions that determine the reported status of each monitor instance.
5-25
Module 5 - Configuring Groups and Monitors
Threshold Settings – Status Threshold – You can set status threshold criteria for each monitor instance to determine an Error status, a Warning status, or a Good status. – Each status threshold consists of a measurement parameter, a logic comparison operation, and a measurement value that you can specify. – Parameters and the value of the status threshold depends on the monitor type: • For example, the measurement parameter for a CPU monitor is CPU utilization (%).
Threshold Settings – Status Thresholds You can set the status threshold criteria for each monitor instance to determine an Error status, a Warning status, and a Good status. Each status threshold consists of a measurement parameter, a logic comparison operation, and a measurement value that you can specify. The parameter and the value depend on the monitor type. For example, the measurement parameter for a CPU monitor is CPU utilization (%). To indicate data volatility, where current monitor readings significantly deviate from monitor previous runs, set status thresholds using a baseline. You can set up one or more status threshold criteria for each status condition. Most monitor types include one default setting for each of the three status conditions. Default thresholds of the monitor are displayed when you first configure the monitor. In addition, for dynamic (VMware Host) monitors, you can display thresholds for all regular expression patterns that are translated to actual current counters.
5-26
Module 5 - Configuring Groups and Monitors
Threshold Settings – Status Impact – Changes in the monitor threshold status can have the following impact: • Signals an event and acts as a trigger for alerts • Affects the state of a dependency between monitors • Affects the status of a monitor in the SiteScope Dashboard
Threshold Setting – Status Impact A change of status signals an event and acts as a trigger for alerts associated with the monitor or the group to which the monitor belongs. For example, if the monitor detects that the system has become unavailable; the status change from Good to Error is used to trigger an alert on error. A change of status can also affect the state of a dependency between monitors. For example, a monitor that detects a change that results in an Error status might be a trigger to disable one or more monitors that depend on the system. The threshold setting also affects the status of the monitor in the SiS Dashboard. When viewing SiS data in the Current Status tab of Dashboard, you can drill down in the monitor tree to view monitor and measurement status and availability. The status is displayed by color and a status icon in the SiS Dashboard.
Threshold Settings – Threshold Settings Page In the Threshold Settings tab, you can manually set logic conditions that determine the reported status of each monitor instance. The user interface elements of the Threshold Settings page are as follows: •
If unavailable – Status assignment for when the monitor is not available, choose from the following options: •
Set monitor status according to thresholds
•
Set monitor status to Good
•
Set monitor status to Warning
•
Set monitor status to Error Note: A monitor instance can have a status of Unavailable as well as a status of Good, Warning, or Error.
•
Default status – Monitor status (Good, Warning, or Error) if the threshold criteria for the monitor instance are not met. Default value – Good
•
On internal error – Monitor status assignment if a configuration or internal error occurs, choose from the following options: •
Set monitor status according to Thresholds
•
Set monitor status to Error
•
Set monitor status to Warning
5-28
Module 5 - Configuring Groups and Monitors •
Set monitor status to Good
•
Set monitor status to Unavailable
•
Add Default Thresholds – Adds default threshold settings to the monitor instance, for the applicable status categories. Default thresholds are indicated by the (default) label. Default thresholds are editable only after selecting a condition from the Condition field (the default condition can be selected). After any criteria of the default threshold are changed, the (default) label is removed.
•
Remove Default Thresholds – Deletes the default threshold settings from the monitor instance. Default settings that were added and were subsequently modified, are not removed.
5-29
Module 5 - Configuring Groups and Monitors
Threshold Settings – Condition Fields – Condition: • Measurement parameter for determining the status of a monitor instance
– Operator: • Measurement operator for determining the status of a monitor instance • The following operators are available: – Value – The value applicable to the measurement parameter. – Schedule – Time range used to define the status of the monitor instance during which the monitor result is compared to the threshold.
Threshold Settings – Condition Fields The condition fields are: •
Condition – Measurement parameter for determining the status of this monitor instance. The list of measurements is dynamically updated based on the type of monitor you are configuring. Default measurements exist for many monitor types and differ per monitor type. For many default measurements, there are corresponding defaults for the operator and value boxes that are not editable.
•
Operator – Measurement operator for determining the status of this monitor instance. The following operators are available: •
>= Greater than or equal to
•
== Equals
•
!= Not the same as
•
<= Less than or equal to
•
< Less than
•
contains the value entered
•
!contains Does not contain the value entered
5-30
Module 5 - Configuring Groups and Monitors •
Schedule – You can select a schedule to determine the status of the monitor instance if you want to define when to check the monitor run result against the threshold. This is useful if you want to restrict checking the monitor run results against the threshold to certain days or hours only. For example, you might want the monitor status to be based on results gathered during business hours only. At times outside the threshold schedule period, the monitor is assigned the predefined status in the Default status box. By default, monitor run results are checked against the threshold on an everyday – all day schedule.
5-31
Module 5 - Configuring Groups and Monitors
Threshold Settings – Multiple Conditions – The individual threshold criteria results are combined as logical OR relationships where more than one threshold condition is defined for any of the three settings. – If one or more of the conditions are met for a status setting, the monitor status is set to the corresponding status condition. – If status conditions are met for more than one status condition, the status of the monitor is set to the highest value of the status condition.
Threshold Settings – Multiple Conditions The individual threshold criteria results are combined as logical OR relationships when more than one threshold condition is defined for any of the three settings. When one or more of the conditions (for example when two conditions for Error if setting) are met for a status setting, the monitor status is set to the corresponding status condition. If status conditions are met for more than one status condition setting, the status of the monitor is set to the highest valued status condition. For example, if one condition is selected as Error if and another condition selected as Warning if are met, the status would be reported as an Error, with Error being the highest value, Warning the next highest, and Good as the lowest value.
5-32
Module 5 - Configuring Groups and Monitors
Enabling/Disabling a Monitor – The Enable/Disable Monitor pane enables you to set the status (enabled/disabled) for the selected monitor.
Enabling/Disabling a Monitor The Enable/Disable Monitor pane enables you to set the status (enabled/disabled) for the selected monitor. To access the Enable/Disable Monitor pane, perform the following steps: 1. Select the Monitors context. In the monitor tree, expand the group folder that contains the monitor, and select the monitor. 2. In the right pane, select the Properties tab, and select Enable/Disable Monitor. The user interface elements of the Enabling/Disabling a Monitor are: •
Enable monitor – Enables the monitor if the monitor was previously disabled. Its default value is Selected.
•
Disable monitor – When a monitor has been disabled, SiS continues to schedule the monitor to run based on the Frequency setting for the monitor but the monitor action is not run. SiS records a monitor data log entry for the monitor when it was scheduled to be run but reports the monitor status as disabled in the place of metrics data.