User s Guide GC

Transcription

1 Tioli IBM Tioli Monitoring for Databases: Sybase ASE User s Guide GC

2

3 Tioli IBM Tioli Monitoring for Databases: Sybase ASE User s Guide GC

4 Note Before using this information and the product it supports, read the information in Appendix G, Notices, on page 225. First Edition (Oct. 2004) This edition applies to ersion of IBM Tioli Monitoring for Databases: Sybase ASE and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Tables Figures ii About this guide ix Who should read this guide ix What this guide contains ix Publications x IBM Tioli Monitoring for Databases: Sybase ASE library x Prerequisite publications x Related publications x Accessing publications online xi Ordering publications xi Accessibility xii Tioli technical training xii Support information xii Conentions used in this guide xii Typeface conentions xii Operating system-dependent ariables and paths xiii Tioli command syntax xiii Chapter 1. Oeriew of IBM Tioli Monitoring for Databases: Sybase ASE. 1 Features of IBM Tioli Monitoring for Databases: Sybase ASE IBM Tioli Monitoring for Databases: Sybase ASE functions IBM Tioli Monitoring for Databases: Sybase ASE enironment Objects that represent resources User interface options Chapter 2. Resource models About resource models Operational modes for thresholds Controlling statistical thresholding Training modes Chapter 3. How to use IBM Tioli Monitoring for Databases: Sybase ASE. 17 Begin monitoring with preconfigured resource models Examine the monitoring enironment Recoer the operation of a resource Collect data and create reports Modify resource model alues to detect problems 18 Chapter 4. Procedures Discoering resources to monitor Distributing resource models Determining which resource models are monitoring which managed resources Controlling monitoring Specifying a task to run automatically Customizing cycle time Customizing indications and eents Customizing parameters Customizing thresholds Re-training resource model thresholds Logging data for a resource model Creating reports Appendix A. Resource model reference 41 Log Monitor Sybase Aailability Locks RM Data Cache RM Space Usage RM Process Waits RM State RM Traffic RM Appendix B. Task reference Start Sybase Adaptie Serer Stop Sybase Adaptie Serer Start Sybase Backup Serer Stop Sybase Backup Serer Start Sybase Monitor Serer Stop Sybase Monitor Serer Check Sybase ASE Serer Status Configure Eent Serer Create Sybase ASE Serer Object Discoer Manage Tioli Logs Modify Object Properties TBSM Synchronization Appendix C. Eent classes and rules reference Eent classes SybaseAailability_IXB_ApplicationUnaailable 169 NumberOfDeadlocks_IXB NumberOfLockWaits_IXB LockWaitTime_IXB NumberOfAailableLocks_IXB LocksInUse_IXB CacheHitRatio_IXB DBAllocatedSize_IXB DBUsedSize_IXB DBIndexSize_IXB DBUnallocatedSizeInKB_IXB NumberTotalPages_IXB NumberFreePages_IXB NumberUsedPages_IXB PercentFreeSpace_IXB NumberWaitingProcesses_IXB NumberDatabasesOpen_IXB Copyright IBM Corp iii

6 EngineIdleTimeInSeconds_IXB NumberEngineConnections_IXB NumberSererConnections_IXB NumberSererConnectionsAailable_IXB NumberPacketsSentPerSecond_IXB NumberPacketsReceiedPerSecond_IXB Rules for eents Appendix D. Data proiders reference 179 LogMonitor proider LogMonitor configuration file LogMonitor configuration XML DTD Log names Appendix E. Problem determination 191 Built-in problem determination features Problem classification Trace logging Installation and uninstallation trace logs Data proider trace logs Resource model trace logs Task trace logs IBM Tioli Enterprise Console trace logs Installation problem determination Problems and workarounds Discoery problem determination Resource model problem determination Tasks problem determination Eent problem determination Support information Searching knowledge bases Obtaining fixes Contacting IBM Software Support Informational, warning, and error messages Message format IBM Tioli Monitoring for Databases: Sybase ASE Messages IBM Tioli Monitoring Component Serices messages Appendix F. Accessibility Naigating the interface using the keyboard Magnifying what is displayed on the screen Appendix G. Notices Trademarks Index i IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

7 Tables 1. Computation of thresholds example IBM Tioli Monitoring for Databases: Sybase ASE resource models Ways to inoke tasks LogMonitor CIM class LogMonitor properties LogMonitor dependency set LogMonitor parameters ITMException ILT parameters ITMException ILT exceptions for the LogMonitor LogMonitor Configuration XML DTD syntax elements and attributes Installation and uninstallation trace logs and descriptions Data proider trace logs Resource model trace logs Task trace logs IBM Tioli Enterprise Console trace logs General problems and solutions for installation Installation problems and solutions for Tioli Data Warehouse General problems and solutions for uninstallation Discoery problems and solutions General resource model problems and solutions Specific resource model problems and solutions Task problems and solutions Eent problems and solutions Copyright IBM Corp. 2004

8 i IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

9 Figures 1. Percent CPU utilization against I/O Read Ops/Second Distribution histogram for CPU utilization oer a one week period CPU utilization oer a one week period Queries/minute oer a one-week period 13 Copyright IBM Corp ii

10 iii IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

11 About this guide Who should read this guide The IBM Tioli Monitoring for Databases: Sybase ASE User s Guide proides information about using IBM Tioli Monitoring for Databases: Sybase ASE after installation and setup. See IBM Tioli Monitoring for Databases: Sybase ASE Installation and Setup Guide for complete information about installing the software and setting it up. This guide is for system administrators who use IBM Tioli Monitoring for Databases: Sybase ASE to monitor and manage Sybase ASE resources. Readers should be familiar with the following topics: Tioli management software Tioli application software What this guide contains UNIX-based operating systems Microsoft Windows operating systems Tioli Data Warehouse (optional) IBM Tioli Enterprise Console IBM Tioli Business Systems Manager (optional) This guide contains the following chapters: Chapter 1, Oeriew of IBM Tioli Monitoring for Databases: Sybase ASE, on page 1 Proides an introduction to IBM Tioli Monitoring for Databases: Sybase ASE. Chapter 2, Resource models, on page 5 Proides conceptual information about resource models and thresholding. Chapter 3, How to use IBM Tioli Monitoring for Databases: Sybase ASE, on page 17 Proides a list of purposes to achiee when using the product, and a list of procedures for achieing each purpose. After completing the tasks in the Installation and Setup Guide and becoming familiar with the information in Chapters 1 and 2 of this guide, this chapter proides information about how you can use the product. Chapter 4, Procedures, on page 21 Proides procedural information about setting up, monitoring, and controlling resources, including information about how to customize monitoring to match the needs of your Sybase ASE monitoring enironment. Appendix A, Resource model reference, on page 41 Proides detailed information about each resource model that you can use with IBM Tioli Monitoring for Databases: Sybase ASE, including the default settings. Appendix B, Task reference, on page 131 Proides detailed information about the tasks proided with IBM Tioli Monitoring for Databases: Sybase ASE. Appendix C, Eent classes and rules reference, on page 169 Copyright IBM Corp ix

12 Describes the eent classes and rules for IBM Tioli Monitoring for Databases: Sybase ASE. Appendix D, Data proiders reference, on page 179 Proides a list of the MOF files for IBM Tioli Monitoring for Databases: Sybase ASE and the metrics for the LogMonitor data proider. Appendix E, Problem determination, on page 191 Proides information about troubleshooting the arious components of IBM Tioli Monitoring for Databases: Sybase ASE, information about log files and messages, and information about working with IBM Software Support. Appendix F, Accessibility, on page 223 Proides information about the accessibility features in IBM Tioli Monitoring for Databases: Sybase ASE. Appendix G, Notices, on page 225 Proides IBM and Tioli notices and trademark information as it applies to IBM Tioli Monitoring for Databases: Sybase ASE. Publications This section lists publications in the IBM Tioli Monitoring for Databases: Sybase ASE library and any other related documents. It also describes how to access Tioli publications online, how to order Tioli publications, and how to submit comments on Tioli publications. IBM Tioli Monitoring for Databases: Sybase ASE library Prerequisite Related The IBM Tioli Monitoring for Databases: Sybase ASE library contains the following publications: IBM Tioli Monitoring for Databases: Sybase ASE Installation and Setup Guide Proides information about installing and setting up IBM Tioli Monitoring for Databases: Sybase ASE. IBM Tioli Monitoring for Databases: Sybase ASE User s Guide Proides conceptual, procedural, and reference information about how to monitor and manage resources with IBM Tioli Monitoring for Databases: Sybase ASE. This guide also proides troubleshooting information about the arious components of IBM Tioli Monitoring for Databases: Sybase ASE, as well as information about log files and informational, warning, and error messages. publications To use the information in this book effectiely, you must hae some knowledge of IBM Tioli Monitoring, which you can get from the following books: IBM Tioli Monitoring User s Guide Proides an oeriew of IBM Tioli Monitoring, especially of resource models. It also describes how to use the user interface. Tioli Management Framework User s Guide Proides information about how to use the Tioli graphical user interface (GUI) publications The following documents also proide useful information: Tioli Enterprise Installation Guide Tioli Management Framework Reference Manual x IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

13 IBM Tioli Enterprise Console Adapters Guide IBM Tioli Enterprise Console Eent Integration Facility User s Guide IBM Tioli Enterprise Console Reference Manual IBM Tioli Enterprise Console Rule Builder s Guide IBM Tioli Business Systems Manager product documentation IBM Tioli Monitoring product documentation Installing and Configuring Tioli Data Warehouse IBM Tioli Monitoring Component Serices, Version 5.1.3, Guide for Warehouse Pack, Version , using Tioli Data Warehouse 1.2 Tioli Data Warehouse product documentation IBM Tioli Monitoring Resource Model Builder User s Guide The Tioli Software Glossary includes definitions for many of the technical terms related to Tioli software. The Tioli Software Glossary is aailable, in English only, at Accessing publications online The documentation CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. Ordering IBM posts publications for this and all other Tioli products, as they become aailable and wheneer they are updated, to the Tioli software information center Web site. Access the Tioli software information center by first going to the Tioli software library at the following Web address: Scroll down and click the Product manuals link. In the Tioli Technical Product Documents Alphabetical Listing window, click M to access all of the IBM Tioli Monitoring product manuals. Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper. The IBM Software Support Web site proides the latest information about known product limitations and workarounds in the form of technotes for your product. You can iew this information at the following Web site: publications You can order many Tioli publications online at the following Web site: publications/cgibin/pbi.cgi You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, see the following Web site for a list of telephone numbers: About this guide xi

14 Accessibility Accessibility features help users with a physical disability, such as restricted mobility or limited ision, to use software products successfully. With this product, you can use assistie technologies to hear and naigate the interface. You can also use the keyboard instead of the mouse to operate most features of the graphical user interface. Tioli technical training For additional information, see the Accessibility Appendix in the user s guide for this product. For Tioli technical training information, refer to the following IBM Tioli Education Web site: Support information Support information on page 206 describes the following options for obtaining support for IBM products: Searching knowledge bases on page 206 Obtaining fixes on page 206 Contacting IBM Software Support on page 207 Conentions used in this guide Typeface This guide uses seeral conentions for special terms and actions, and operating system-dependent commands and paths. conentions This guide uses the following typeface conentions: Bold Italic Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) Keywords and parameters in text Words defined in text Emphasis of words (for example, Use the word that to introduce a restrictie clause. ) New terms in text (except in a definition list) Variables and alues you must proide Monospace Code and other examples xii IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

15 File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Operating system-dependent ariables and paths The publications in this library use the UNIX conention for specifying enironment ariables and for directory notation. When using the Windows command line, replace $ariable with %ariable% for enironment ariables and replace each forward slash (/) with a backslash (\) in directory paths. The names of enironment ariables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equialent to $tmp in UNIX. Note: If you are using the bash shell on a Windows system, you can use the UNIX conentions. Tioli command syntax The following special characters define Tioli command syntax: [ ] Identifies elements that are optional. Required elements do not hae brackets around them.... Indicates that you can specify multiple alues for the preious element. Separate multiple alues by a space, unless otherwise directed by command information. If the ellipsis for an element follows a closing bracket, use the syntax within the brackets to specify multiple alues. For example, to specify two administrators for the option [ a admin]..., use a admin1 a admin2. If the ellipsis for an element is within the brackets, use the syntax of the last element to specify multiple alues. For example, to specify two hosts for the option [ h host...], use h host1 host2. Indicates mutually exclusie information. You can use the element on either the left or right of the ertical bar. { } Delimits a set of mutually exclusie elements when a command requires one of them. Brackets ([ ]) are around elements that are optional. In addition to the special characters, Tioli command syntax uses the typeface conentions described in Typeface conentions on page xii. The following examples illustrate the typeface conentions used in Tioli command syntax: wcrtpr [ a admin]... [ s region] [ m resource]... name The name argument is the only required element for the wcrtpr command. The brackets around the options indicate they are optional. The ellipsis after the a admin resource option means that you can specify multiple administrators multiple times. The ellipsis after the m resource option means that you can specify multiple resources multiple times. wchkdb [ o outfile] [ u] [ x] { f infile i object...} The f, i, and object elements are mutually exclusie. Braces that surround elements indicate that you are including a required element. If you specify the object argument, you can specify more than one object. About this guide xiii

16 xi IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

17 Chapter 1. Oeriew of IBM Tioli Monitoring for Databases: Sybase ASE IBM Tioli Monitoring for Databases: Sybase ASE proides you with the capability to monitor Sybase ASE, and to perform basic actions with Sybase ASE. This chapter proides a description of the features and functions of IBM Tioli Monitoring for Databases: Sybase ASE, and a description of the IBM Tioli Monitoring for Databases: Sybase ASE enironment. Features of IBM Tioli Monitoring for Databases: Sybase ASE The IBM Tioli Monitoring component software identifies, notifies you of, and corrects common problems with the application that it monitors. The software includes the following features: Discoery of resources Monitoring Eent management Operations management Data gathering and reporting The discoery process searches your application enironment and adds the resources in that enironment to the Tioli monitoring enironment to ensure that you are managing all aailable resources. In a Tioli enironment, a resource is a hardware, software, or data entity that is managed by Tioli software. A managed resource is a database object that represents a system or network resource and is goerned by policies. The monitoring of resources occurs through resource models. The aailability resource model periodically checks the status of your application resources to ensure that they are operational. You can configure this resource model to match the monitoring needs of your application enironment. You can also run a task to check the aailability of a resource. Log monitoring resource models monitor the logs associated with the application to detect key errors and eents affecting aailability or performance of the serices. Other resource models collect performance data for the application. These resource models contain thresholds that cause eents to be sent when these are not in the expected ranges. They also log data that can be iewed in the IBM Tioli Monitoring Web Health Console. In addition to the resource models proided with IBM Tioli Monitoring for Databases: Sybase ASE, you can use the IBM Tioli Monitoring resource models. You can also configure resource models proided with other IBM Tioli Monitoring component software that you are using. IBM Tioli Monitoring for Databases: Sybase ASE functions on page 2 contains a description of each type of monitoring for IBM Tioli Monitoring for Databases: Sybase ASE. When resource models detect that resources are not operating as desired, they create eents that they forward to the IBM Tioli Enterprise Console serer. You can manage the eents through IBM Tioli Enterprise Console or through IBM Tioli Business Systems Manager if you hae installed these applications. Copyright IBM Corp

18 Tasks enable you to manage your application resources on a daily basis, for example, you can use tasks to start resources and stop resources manually or automatically. When you run a task manually, you initiate the task. When you run a task automatically, a resource model initiates the task. When you enable data logging, the resource models gather data that you can iew in the IBM Tioli Monitoring Web Health Console and Tioli Data Warehouse. Then, you can run reports on that data. Reports enable you to analyze the health and performance of your Sybase ASE resources oer a period of time. You can also use reports to predict resource usage and diagnose potential problems before they occur. With Tioli Data Warehouse, you can create the following types of reports: application aailability, system resource consumption, and process resource consumption. IBM Tioli Monitoring for Databases: Sybase ASE functions contains a description of each type of report for IBM Tioli Monitoring for Databases: Sybase ASE. IBM Tioli Monitoring for Databases: Sybase ASE functions IBM Tioli Monitoring for Databases: Sybase ASE proides the following functions: Aailability and resource monitoring Monitor serer and process aailability. Monitor resource usage of processes associated with Sybase ASE, including CPU and memory used. Emit indications when processes become unaailable and when resource usage is not within the range allowed by the threshold alues. Lock Monitoring Monitor number of deadlocks. Emit indications when the number of deadlocks is not within the range allowed by the threshold alues. Monitor lock waits and emit indications when the lock wait times is not within the range allowed by the threshold alues. Monitor aailable locks and locks in use. Emit indications when aailable locks and locks in use are not within the range allowed by the threshold alues. Cache Effectieness monitoring Monitor cache effectieness as demonstrated by the ratio of cache hits as a percentage of retrieal attempts. Emit indications when the percentage of hits is not within the range allowed by the threshold alues. Space Log Wait monitoring Monitor space usage for each database. Identify the database size, how much space has been allocated, how much space is being used, how much space the indexes consume and how much space has not been allocated for each database. Emit indications when any of the sizes are not within the range allowed by the threshold alues. Monitor space usage for all segments is all databases. Identify the total segment size, how much space is free and how much space is being used. Emit indications when any of the sizes are not within the range allowed by the threshold alues. Monitoring Monitor the Sybase ASE log file for for certain messages. Emit indications for each message found in the log file. Monitoring Monitor how many processes are waiting and generate an indication when the number of waiting processes is not within the range allowed by the threshold alues. 2 IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

19 State Monitoring Monitor the number of databases open and emit indications when the number is not within the range allowed by the threshold alues. Monitor the state, idle time and number of connections for each engine. Emit indications when the idle time or the number of connections are not within the range allowed by the threshold alues. Traffic Monitoring Monitor packets sent and receied. Emit indications when the number of packets sent or receied are not within the range allowed by the threshold alues. Monitor connections aailable and in use. Emit indications when the number of connections aailable or in use are not within the range allowed by the threshold alues. CPU Usage Report Proides a resource usage report that shows the maximum CPU used per day by the processes associated with the monitored product. Serer Aailability Report Proides an aailability report that shows the percent of time the serer processes were aailable each day. All processes defined for monitoring by Aailability monitoring are reported. Memory Usage Report Proides a resource usage report that shows the maximum and aerage memory used per day by the processes associated with the database serer. IBM Tioli Monitoring for Databases: Sybase ASE enironment After you install and set up IBM Tioli Monitoring for Databases: Sybase ASE as described in the IBM Tioli Monitoring for Databases: Sybase ASE Installation and Setup Guide, you hae an enironment that contains the following components: Base software Tioli Management Framework IBM Tioli Monitoring IBM Tioli Monitoring Component Serices IBM Tioli Monitoring for Databases: Sybase ASE Required patches or fix packs Other optional applications that are integrated with IBM Tioli Monitoring for Databases: Sybase ASE IBM Tioli Enterprise Console (one eent serer for each Tioli management region) IBM Tioli Business Systems Manager IBM Tioli Monitoring Web Health Console Tioli Data Warehouse Basic monitoring components Authorization roles that enable product actiities in the Tioli enironment Managed nodes and endpoints that are running A policy region that contains a profile manager A profile that contains resource models (See Appendix A, Resource model reference, on page 41 for descriptions of the resource models.) Objects that represent the resources that the application manages Resource models that are running on managed resources (objects) Chapter 1. Oeriew of IBM Tioli Monitoring for Databases: Sybase ASE 3

20 Task libraries that contain tasks (See Appendix B, Task reference, on page 131 for descriptions of the tasks.) Objects that represent resources Tioli objects that represent Sybase ASE resources are registered in the Tioli management region and monitored by the IBM Tioli Monitoring for Databases: Sybase ASE resource models. You use tasks to take actions on these objects. The following objects represent the resources you monitor with this software: SybaseASESerer_IXB User interface options Installation of the base software and other integrated applications proides the following interfaces that you can use to work with your resources and data: Tioli desktop Traditional Tioli graphical user interface (GUI) Command-line interface (CLI) UNIX command line or the bash shell on a Windows operating system, from which you can perform system operations instead of using the Tioli desktop IBM Tioli Enterprise Console Eent management application IBM Tioli Business Systems Manager Application for examining how resources affect a business function, and for managing these resources. IBM Tioli Monitoring Web Health Console Also referred to as the Web Health Console, a Web-based graphical interface that enables you to iew the health of resources on an endpoint and to iew real-time or historical data Tioli Data Warehouse Centralized data store where historical data gathered by IBM Tioli Monitoring for Databases: Sybase ASE can be stored, aggregated, and correlated so you can create reports 4 IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

21 Chapter 2. Resource models About resource models Resource models are the key IBM Tioli Monitoring component that proides the monitoring function in IBM Tioli Monitoring for Databases: Sybase ASE. This chapter contains conceptual information about resource models and the parts of resource models that you can customize to monitor your resources. Some resource models hae thresholds that are goerned by parameters. This chapter contains an extensie explanation of this type of thresholding. The following additional information about resource models is also located in this user s guide: Chapter 4, Procedures, on page 21 contains procedural information about customizing resource models as well as setting up and monitoring resources. Appendix A, Resource model reference, on page 41 contains detailed information about the settings for each of the resource models included with IBM Tioli Monitoring for Databases: Sybase ASE. The IBM Tioli Monitoring User s Guide also contains additional information about resource models With IBM Tioli Monitoring for Databases: Sybase ASE you can use preconfigured resource models to monitor essential resources, and you can customize the preconfigured resource models to monitor your resources. A resource model accesses specific performance data from the system at runtime. (For example, the Process resource model gathers data about processes running on the system.) The resource models process the data they collect using an algorithm that determines whether or not the system is performing according to expectations. This enables you to detect bottlenecks and other potential problems and define automatic recoery actions from critical situations affecting your resources. This ability frees system administrators from manually scanning extensie performance data. This monitoring software integrates with other Tioli Aailability solutions, including IBM Tioli Business Systems Manager and IBM Tioli Enterprise Console. You can either use the default alues for a resource model to collect performance data or customize a resource model to match specific requirements in your enironment. Distributing resource models using default alues enables you to begin monitoring immediately to obtain useful data concerning your enterprise. As you become more familiar with the monitoring process and feedback, you might choose to customize the resource model information. In addition to customizing preconfigured resource models in IBM Tioli Monitoring for Databases: Sybase ASE, you can deelop new resource models using IBM Tioli Monitoring Resource Model Builder. See the IBM Tioli Monitoring Resource Model Builder User s Guide for information about how to deelop a new resource model. You can customize a resource model by modifying the following elements of the resource model configuration: Cycle time Copyright IBM Corp

22 Thresholds Parameters Indications Occurrences Holes Sending eents to IBM Tioli Enterprise Console Seerity of eent Clearing eents Tasks Schedule Logging The following information proides brief explanations of the resource model elements that you can customize depending on the resource model: Cycle time When a resource model runs on an endpoint, it gathers data at regular interals, called cycles. The interal between cycles is the cycle time, which is displayed in seconds. A resource model with a cycle time of 60 seconds gathers data eery 60 seconds. Each of the preconfigured resource models has a default cycle time that you can modify. At each cycle, the resource model collects data, analyzes it, generates the eents, and triggers specified tasks. See Customizing cycle time on page 28. Thresholds A threshold is a point that must be reached before a resource model triggers an occurrence. Each threshold has a default numeric alue that you can change. Typically, this alue represents a limit for a satisfactory resource state. If the monitored resource exceeds this limit, an indication occurs. See Operational modes for thresholds on page 9 for a complete explanation of thresholding. See Customizing thresholds on page 32 for complete information about customizing thresholds. Parameters A parameter is a alue that is used to control how a resource model operates. Parameters can represent the instances that you want to monitor or a limit you do not want a resource to exceed. While thresholds can only be numeric alues, parameters can be numeric or string alues. Some resource models hae no parameters, others hae one or more parameters. Aailability types of resource models do not hae any parameters. Data collection types of resource models hae parameters that allow you to customize how the thresholding works for a resource model. The Log Monitor resource model and Parametric Eent Log resource model customize what is monitored. See Customizing parameters on page 31 for information about modifying parameters. Indications An indication occurs when the state of a gien resource meets defined criteria. By itself, an indication does not trigger any specific action. Indications are aggregated to become an eent. 6 IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

23 An eent is a notification of change in the status of a resource. An eent is triggered when an indication occurs and does not occur (referred to as a hole) in a set pattern or a set number of times. When you define an eent, you also specify whether these indications must be consecutie, or whether the sequence can be interrupted by one or more monitoring cycles that do not register any indication (holes). An eent erifies the persistence of an indication by eliminating unrepresentatie peaks and troughs for the indication. For example, a process that generates the Process High CPU indication in one cycle might not threaten other processes if the high usage is not repeated. Howeer, an indication that persists oer seeral cycles is more likely to be a problem. Thus, an eent defines the significant number of consecutie occurrences of the indication. The eent notifies the system administrator about the state of a specific resource. Eents can trigger an action, and, if enabled, send a notification to the IBM Tioli Enterprise Console eent serer, IBM Tioli Business Systems Manager, or the IBM Tioli Monitoring Web Health Console. You can configure indications by specifying the following information: Occurrences Holes Sending eents to IBM Tioli Enterprise Console Seerity of eent Clearing eents Tasks See Customizing indications and eents on page 29. Occurrences and holes Occurrences and holes record whether or not an indication occurs during the cycle for a specific resource model. An occurrence is a cycle during which an indication occurs for a gien resource model. A hole is a cycle during which an indication does not occur for a gien resource model. A hole means none of the conditions that generate an indication were met. IBM Tioli Enterprise Console serer When the settings for an indication include sending eents to the IBM Tioli Enterprise Console serer, you can iew the eents in the IBM Tioli Enterprise Console if you hae compiled and loaded the releant Basic Recorder of Objects in C (BAROC) files on the serer. An eent carries information including the eent class, eent identity, seerity, location (host where the eent originated), and description. This information can help to identify the problem. IBM Tioli Enterprise Console proides tools for the following functions: Receiing eents from arious sources Processing eents using rules Grouping eents and delegating the groups selectiely to administrators Viewing eents from multiple sources at a console Chapter 2. Resource models 7

24 For information about iewing eents, see the IBM Tioli Enterprise Console User s Guide. Clearing eents can also be processed by the IBM Tioli Enterprise Console serer. If the default procedure is used to enable the monitoring of eents, the IBM Tioli Enterprise Console serer uses the clearing eent to close the associated error eent. Seerity A seerity alue is assigned to an eent when it is sent to the IBM Tioli Enterprise Console serer or IBM Tioli Business Systems Manager because there is a problem. An eent can hae one of the following degrees of seerity: fatal, critical, warning, harmless, or minor. Clearing eents A clearing eent is a resource model function that is enabled or disabled when the resource model is deeloped. If enabled, clearing eents allow IBM Tioli Monitoring software to close an eent when the circumstances that caused the eent are no longer present. Clearing eents can be processed by the IBM Tioli Enterprise Console serer and by IBM Tioli Business Systems Manager. Clearing eents hae a seerity of harmless regardless of the seerity of the original eent, but hae the same eent ID as the original eent. For example, if a serice stops, the IBM Tioli Enterprise Console serer receies an eent notifying it of this problem. Until the serice restarts, the problem is still present on the endpoint, but IBM Tioli Monitoring does not send any further eent notifications to the IBM Tioli Enterprise Console serer. If the Clearing Eent function is enabled, as soon as the serice restarts, a clearing eent is sent to the IBM Tioli Enterprise Console serer, thereby closing the original eent. The Clearing Eent itself does not normally appear on the serer, because its only function is to clear the original error eent. When the clearing eent function is enabled for a resource model, eents (carrying a specified eent ID) are sent only the first time the aggregation rule is satisfied. Tasks For any indication, tasks can run automatically. These tasks take positie steps to remedy the situation, or ensure that information about the indication is distributed to the appropriate authorities or entities. You can associate one or more tasks with a specific indication. These tasks are automatically triggered when the eent occurs and, typically, are used for restoring satisfactory system serice leel. Each time an indication occurs, the system proides notification that the indication occurred, triggers a task to restore satisfactory conditions; and if the task is successful, proides notification that the task was performed. Tasks are associated with the execution of a CIM method or the execution of a program. Associate a task with an indication when modifying an existing resource model using this software. If you associate multiple tasks with an indication, they can be called in any order, and all at once. 8 IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

25 Scheduling IBM Tioli Monitoring contains a scheduling feature that enables you to determine a period within which monitoring takes place and specific scheduling rules. The monitoring period is determined by defining a from and a to date. The scheduling rules enable you to define time periods on specific days of the week during which monitoring takes place. Any number of rules can be defined, allowing you to set up a complex pattern of resource monitoring for a profile, coering the time periods important to you. The scheduled times are always interpreted as local times, enabling you to set up a single rule that monitors the same local time period in different time zones. For example, if your region coers seeral time zones, but you want to monitor morning actiities in each time zone, a single rule defining the monitoring period as between 08:00 and 13:00 is interpreted locally in each of the time zones, so that you monitor the same relatie period. All of the times for eents or actiities reported from endpoints or gateways are also logged in the local time of the system where they originated. Logging Resource models support data logging to collect and store monitoring data in a local database. Operational modes for thresholds You can log raw data or aggregated data. If you log raw data, you can also log Tioli Data Warehouse data. You can iew raw, aggregated, and Tioli Data Warehouse data in the IBM Tioli Monitoring Web Health Console. You can only see Tioli Data Warehouse data in the Tioli Data Warehouse application. You can set the interal for aggregation and the amount of data stored in the Endpoint DB. This goerns the amount of disk space used on the endpoint and limits the amount of data you can see in the IBM Tioli Monitoring Web Health Console. See Logging data for a resource model on page 35. Many resource models can be iewed as a collection of rules of the following form: if (metric >= alue) then SendEent(name, properties); These thresholding rules operate by comparing a metric associated with a specific resource to a alue (the threshold) that indicates that the resource is in an unsatisfactory state, such as when a process is consuming an abnormal amount of processor time. The default threshold alues are chosen to bias against the occurrence of false posities, so you might need to adapt the thresholds to the deployment context. Any threshold can be specified as a fixed threshold, a direct stipulation of the alue in the aboe form. This is the traditional methodology for specifying threshold settings. Certain resource models present an additional methodology for specifying thresholds, statistical thresholding, which uses historically gathered obserational data to compute threshold alues. Chapter 2. Resource models 9

26 To change the operational mode of thresholding, you must select the mode for each indiidual threshold as described in Customizing thresholds on page 32. If you want to use only statistical thresholding, you must modify all of the Threshold... calculation method parameters in each of the resource models in a profile. Resource models that are enabled for statistical thresholding can be understood as ealuating a rule of the following form: if (metric >= percentile(p, obserations, conditioning)) then SendEent(name, properties); where: p Percentile leel obserations Set of obserations conditioning Set of temporal and metrical data used to inform the threshold computation Temporal conditioning imposes sensitiity to the current time of day, day of week, or both. You can select temporal conditioning. Metrical conditioning is built into the threshold by the resource model author when a correlation is expected between a drier metric and a drien metric. A drier metric is also known as an index metric. Where this type of thresholding is used, the alue of the index metric is included in the current_index_alue field on the indication. The rest of this section describes the goals and detailed operational principles behind statistical thresholding. The primary goal of statistical thresholding is to learn typical behaior from the obseration of the resource in its deployment enironment in order to minimize the amount of tuning that you are required to do. In order to maximize the applicability of these techniques, the threshold deriation model is based on percentiles. The use of percentiles rather than other summary statistics allows the same framework to apply to all metrics independently of the shape of their distributions. For example, outlier identification based on more than so many standard deiations aboe the aerage works best for metrics with normal distributions, and clumsily on those with heaily skewed or multi-modal distributions. In contrast, a percentile basis can be used to compute a threshold setting from a specified proportion of obserations, allowing a general policy to be stated that declares typical as below the 90th percentile of obserations taken in the training period. Minimum training for this approach is 20 obserations, which generally gies reasonably good results, but more data are usually desirable. Since typical behaior tends to be sensitie to the time of day, the day of week, or both, statistically computed thresholds can be conditioned by the time, the day, or both. This allows the 90th percentile at 14:00 to reflect a workload that is typically heaier than one at 02:00, rather than requiring a threshold to be set for worst-case behaior. This is especially useful when multiple workloads are being sericed by a single computer under the assumption that each load follows a typical timeline. Similarly, certain thresholds proided by the resource models incorporate a relationship between a drier (input or index) metric and a drien (output) metric, allowing a threshold to be conditioned by (the quartile range of) another metric. 10 IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

27 For example, Figure 1 shows the range of the 10th and 90th percentiles of CPU consumption as a function of the number of read operations per second. Figure 1. Percent CPU utilization against I/O Read Ops/Second For a workload that performs a typical amount of work for each block of data read, this can be an early detector that something has gone awry. If the system is currently experiencing heay CPU consumption but few reads, then it is not performing the work required of it at the expected cost. As this information is correlated with other indications, both root cause and impact analysis can be quickly and efficiently performed to ensure cost-effectie incident triage. This small bit of indirection, specification of the criteria by which a threshold should be computed, rather than the threshold itself, is a powerful mechanism for minimizing the amount of configuration that you are required to do when a single profile is to be distributed to multiple machines of differing capabilities or configurations. For example, a computer with a processor rating of 3GHz will process a certain bit of computational work faster than a computer with a rating of 1GHz, leading to a lower CPU utilization on the faster machine than the slower. Setting a threshold in a manner appropriate for the slower machine will miss performance incidents on the faster computer, which leads to a duplication of configuration effort. If both computers are currently proiding acceptable serice at acceptable cost, then distributing a resource model to both computers that deries its threshold settings automatically from obserations allows a single configuration to apply, reducing both configuration and maintenance costs. The ability to condition a threshold by both the time of day and the alue of another metric gies a powerful mechanism for characterizing normal behaior and detecting problems quickly and efficiently. As a specific example, Figure 2 on page 12 shows a distribution of CPU Utilization readings from a simulated web serer oer a one-week interal, taken at a sampling rate of one reading per minute (for 10,080 readings). Chapter 2. Resource models 11

28 Figure 2. Distribution histogram for CPU utilization oer a one week period Clearly, these data are not normally distributed, because three modes are apparent: a light load (less than 20% utilization), a moderate load (between 30% and 50% utilization), and a heay load (more than 60% utilization). The aerage one-minute utilization is 35%, with a standard deiation of 27%, reflecting the fact that approximately 35% of the readings are below 10% utilization, 60% are below 40% utilization, and 97% are below 80% utilization. Gien these readings alone, settings ranging from 80% to 100% can be justified for a HIGH CPU UTILIZATION threshold. If unconditioned statistical thresholding was employed with a threshold at the 97th percentile, the effectie threshold alue would be 80.6% at all times. Figure 3 shows this same data plotted as a function of time, which reeals additional structure. Figure 3. CPU utilization oer a one week period In particular, a strong correlation between the time of day and the CPU utilization is apparent, with a significant spike in the utilization occurring around 6 P.M. on weekdays. Gien this iew of the data, a fixed threshold might be established at around 70% to indicate that the typical behaior of this serer is to consume less 12 IBM Tioli Monitoring for Databases: Sybase ASE: User s Guide

29 than 70% of the aailable CPU. Alternatiely, the deployment of time-of-day conditioned statistical thresholding with a threshold at the 97th percentile would gie a tighter description of typical, with an effectie threshold ranging from 6% to 99% depending on the time of day. The deployment of day-of-week conditioned statistical thresholding would create effectie thresholds of 82% on Monday through Friday, 69% on Saturday, and 40% on Sunday, automatically. Figure 4 shows another iew of the actiity on this simulated serer: the number of queries per minute sericed. Figure 4. Queries/minute oer a one-week period Although the strong correlation with time remains, the strong positie correlation between queries per minute and one-minute CPU utilization (0.97) suggests conditioning the threshold for HIGH CPU UTILIZATION by the current alue for queries per minute. Resource models that condition certain output (or cost) metrics (like CPU Utilization) by certain input (or workload characterization) metrics (like queries per second) incorporate best monitoring practices by stating an expectation that the input metric and output metrics are correlated. Such thresholds are always statistical in nature. Operationally, the threshold is computed by classifying the input metric into the appropriate quartile (0..25, , , or ) and computing the output metric percentile from the subset of the obserations that contain an input metric alue in the appropriate quartile. That is, if the input metric is drawn from the lowest quartile, the expectation is that the monitored resource is behaing typically if and only if it consumes resources in a way that was preiously demonstrated by examples drawn from the lowest quartile. In the case of the data in Figures 2 4, the thresholds would be computed as shown in Table 1. Table 1. Computation of thresholds example Input Quartile Input Upper Range 97th percentile queries/minute queries/minute queries/minute queries/minute 0.80 Chapter 2. Resource models 13