Nimsoft Monitor sybase Guidedocs.nimsoft.com/.../Catalog/sybase/4.1/sybase-4.1.pdf · sybase...

sybase Guide v4.1 series

Nimsoft® Monitor™

Legal Notices Copyright © 2012, CA. All rights reserved.

Warranty

The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft LLC disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft LLC shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft LLC and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft LLC as governed by United States and international copyright laws.

Restricted Rights Legend

If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft LLC’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November 1995), as applicable in any technical data.

Trademarks

Nimsoft is a trademark of CA.

Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.

Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.

Java(TM) is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.

Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of the Open Group.

ITIL® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.

All other trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

Contact Nimsoft

For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products.

At http://support.nimsoft.com/, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ Nimsoft Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].

http://support.nimsoft.com/

mailto:[email protected]

Contents 5

Contents

Chapter 1: sybase 4.1 7

sybase Overview........................................................................................................................................................... 7

Chapter 2: sybase Probe Deployment 9

Prerequisites ................................................................................................................................................................ 9

User ID Authorization ............................................................................................................................................ 9

Supported Platforms .................................................................................................................................................. 10

System Requirements ................................................................................................................................................ 10

Software Requirements ............................................................................................................................................. 10

Monitoring System Requirements ............................................................................................................................. 10

Probe Deployment Information ................................................................................................................................. 10

Migration from Previous Releases ............................................................................................................................. 11

Known Issues .............................................................................................................................................................. 11

ASE Configuration for Monitoring Tables Data Collection ......................................................................................... 11

Chapter 3: sybase Configuration 13

Probe Defaults ............................................................................................................................................................ 14

Probe Configuration Interface Installation ................................................................................................................. 14

Probe Configuration ................................................................................................................................................... 14

Setup Tab ............................................................................................................................................................ 14

Connections Tab .................................................................................................................................................. 19

Profiles Tab.......................................................................................................................................................... 22

Templates Tab ..................................................................................................................................................... 27

Status Tab ............................................................................................................................................................ 28

Define New Checkpoint ...................................................................................................................................... 29

Thresholds for Custom Defined Checkpoints ...................................................................................................... 37

Edit Checkpoint ................................................................................................................................................... 40

Thresholds ........................................................................................................................................................... 43

Schedules ............................................................................................................................................................ 45

Checkpoint Metrics ............................................................................................................................................. 45

Checkpoint description ....................................................................................................................................... 46

Chapter 4: QoS Threshold Metrics 51

sybase QoS Metrics .................................................................................................................................................... 51

sybase Alert Metrics Default Settings ........................................................................................................................ 52

6 sybase Guide

Chapter 1: sybase 4.1 7

Chapter 1: sybase 4.1

This description applies to sybase probe version 4.1.

This section contains the following topics:

sybase Overview (see page 7) Documentation Changes (see page 8)

sybase Overview

The Sybase probe will run selected SQL commands to extract vital information about your Sybase servers. The information is presented to the database administrator as alarms and/or as a report showing areas that need attention.

An extensive range of pre-defined alerts is delivered with the sybase probe and these can quickly be extended to meet the needs of specific monitoring requirements.

The probe supports the SLM product-line by sending Quality of Service (QoS) messages.

sybase Overview

8 sybase Guide

Documentation Changes

This table describes the version history for this document.

Version Date What's New?

4.1 November 2012 ■ Added Probe Defaults (Normal text based).

■ Updated checkpoints database_size and database_size_mb for mixed devices.

■ Added functionality to configure key alarms for any specified data column.

■ Inserted Scheduling functionality in Edit Threshold dialog.

4.0 ■ Created custom checkpoints.

■ Configured alarms for each of the data column returned when SQL code is run for a custom checkpoint.

3.5 February 2011 Added support for reading alarm tokens from configuration.

Related Documentation

Documentation for other versions of the sybase probe (../../sybase.html)

The Release Notes for the sybase probe

Getting Started with CA Nimsoft® Probes

Monitor Metrics Reference Information for CA Nimsoft Probes


Chapter 2: sybase Probe Deployment

This section contains the prerequisites, system requirements and deployment information for the sybase probe.


Prerequisites (see page 9) Supported Platforms (see page 10) System Requirements (see page 10) Software Requirements (see page 10) Monitoring System Requirements (see page 10) Probe Deployment Information (see page 10) Migration from Previous Releases (see page 11) Known Issues (see page 11) ASE Configuration for Monitoring Tables Data Collection (see page 11)

Prerequisites

Software: Sybase OCS client 12.5.x or ASE 15.0.x. For advanced monitoring either Sybase Monitoring Server of Monitoring Tables need to be installed and enabled. Sybase libraries have to be in system PATH. Sybase environment variables has to be set i.e $SYBASE, $SYBASE_ASE, and $SYBASE_OCS has to be set.

Sybase: Sybase Monitoring Server has to be up and running.

User ID Authorization

To run the probe in basic mode, access to following tables is needed:

■ sysdatabases

■ spt_values

■ sysusgaes

■ sysprocesses

■ syscurconfigs

■ sysconfigures

Note: To run the probe in advanced mode using Monitoring Tables, the user ID requires 'mon_role' authorization. To run the probe in advanced mode using Monitoring Server API, 'sa' user ID needs to be used.

Supported Platforms

10 sybase Guide

Supported Platforms

The sybase probe supports the same set of operating systems and databases as supported by the Nimsoft Server solution. Please refer to the Nimsoft Compatibility Support Matrix for the latest information on supported platforms.

System Requirements

The sybase probe should be installed on systems with the following minimum resources:

■ Memory: 2-4 GB of RAM. This probe OOTB configuration requires 256 MB of RAM.

■ CPU: 3 GHz dual-core processor, 32-bit or 64-bit

Software Requirements

The sybase probe requires the following software environment:

■ Nimsoft Monitor Server 5.1.1 or later

■ Nimsoft Robot 5.23 or later

■ Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and above)

Note: For SOC functionality, NM Server 5.6 or later and UMP 2.5.2 or later is required.

Monitoring System Requirements

The Nimsoft sybase probe constantly monitors the internal performance and space allocation throughout the Sybase server. The information is presented to the database administrator as alarms and/or as a report showing areas that need attention.

Probe Deployment Information

There are two ways to distribute archive packages. You can distribute the package within Infrastructure Manager or use the standalone Nimsoft Distribution application.

See Probe Deployment for more information on deploying probes.

http://support.nimsoft.com/downloads/doc/Compatibility_SupportMatrix_current.pdf

http://support.nimsoft.com/downloads/doc/Compatibility_SupportMatrix_current.pdf

http://docs.nimsoft.com/prodhelp/en_US/Probes/GettingStarted/1931642.html

Migration from Previous Releases


Migration from Previous Releases

If you migrate from previous releases, the probe will migrate the old configuration file (sysbase_monitor.cfg) into a release 3 configuration file (sysbase_monitor_v3.cfg). Every instance from V2 will be converted into one connection and one monitoring profile in V3. Every profile starts one thread for SQL queries and one process as Monitor Server data collector.

Known Issues

With Sybase OCS 12.5.0 and 15.0 the Sybase Monitoring Server API can end in a CPU loop if the probe agent does not have the possibility to close connection properly. This issue is solved by applying Sybase maintenance (12.5.3 or higher, 15.0.2 or higher).

ASE Configuration for Monitoring Tables Data Collection ■ buf_cachehit_ratio: enable monitoring = 1

■ lock_requests, lock_requests_db, lock_requests_granted_db, lock_requests_waited_db: enable monitoring = 1, per object statistics = 1, object lockwait timing = 1

■ total_disk_io: enable monitoring = 1

■ stp_cachehit_ratio: enable monitoring = 1

■ locked_users (advanced, with sql text): enable monitoring = 1, max SQL text monitored = 1024 or more, SQL batch capture = 1, sql text pipe active = 1, sql text pipe max messages = 256 or more (depends on interval length and server activity)


Chapter 3: sybase Configuration

The sybase probe allows you to extract and monitor the following information:

■ Server uptime

■ Local and/or remote monitoring of Sybase Servers

■ Amount of free log-file space

■ Data file size for each database.

■ Data and log-file cache hit ratio.

■ Reports the number of:

■ Active users

■ Databases available

■ Users currently logged onto the servers

■ Granted and waited page and table locks

■ Transactions and deadlocks pr. second

■ Database page reads/writes pr. second

■ Disk IO, disk reads and disk writes

■ Committed transactions

For details, refer section Checkpoint description.

Initial configuration of the sybase probe is done by using the UI, defining connections and profiles for monitored instances. The probe may be running locally on the database server or it may be configured to run as a remote client. Every profile will run in its own thread and start, if necessary one monitoring server data collector as separate process.

All windows containing lists are resizable.


Probe Defaults (see page 14) Probe Configuration Interface Installation (see page 14) Probe Configuration (see page 14)

Probe Defaults

14 sybase Guide

Probe Defaults

At the time of deploying a probe for the first time on robot, some default configuration will get deployed automatically. These probe defaults could be Alarms, QoS, Profiles and so on which save time to configure the default settings. These probe defaults will be seen on a fresh install, that is no instance of that probe is already available on that robot in activated or deactivated state.

Probe Configuration Interface Installation

The probe configuration interface is automatically downloaded and installed by the Nimsoft Infrastructure Manager when the probe is deployed on a robot.

Probe Configuration

This section contains specific configuration for the probe.

Setup Tab

The Setup tab contains two sub tabs - General and Message pool. By default, the General sub tab is selected.

Probe Configuration


General Tab

This property sheet will set the general run-time parameters regarding the sybase probe.

The fields in the above tab are explained below:

Generate status only

Instructs the probe to only generate status and not to issue an alarm when a threshold is breached. Select the Status tab to see the status for the different checkpoints.

Alarm severity filter

Sets a "filter" on which severity levels to be considered as alarms.

The sybase probe is capable of checking many areas of the Sybase databases. Some events that are generated are vital and key to the performance and availability of the database. As a database administrator, you may want to pass the important events on to the operations center or helpdesk so the event can trigger pagers and email. The Alarm severity filter will consider the events matching the selected severity level and higher as alarms and pass these on whenever the Generate status only option is unchecked.

For example, if you set this to major, only messages with severity major and upward are considered as alarms.

Status Auto-Update

Allows you to automatically update the status after defined time.

Probe Configuration

16 sybase Guide

Log Size

Sets the size of the probe’s log file to which probe-internal log messages are written. The default size is 100 KB. When this size is reached, the contents of the file are cleared.

Log Level

Sets the level of details written to the log file. Log as little as possible during normal operation to minimize disk consumption.

Message Pool Tab

The Message Pool tab contains a list of all alarm messages available. You select messages from this list when editing the properties for a checkpoint.

Right-click in the list to add, edit, copy, or delete messages.

Probe Configuration


Define Message and Use Message Pool

This functionality allows you to use the Message pool and define a new message.

Follow these steps:

1. Select the Message pool tab, right-click in the list and select New.

The New message dialog appears.

2. Specify a name in the New message dialog.

Probe Configuration

18 sybase Guide

Note: Use the name of the checkpoint for which you create the alarm message as name. That makes it easier to find the alarm message when selecting an alarm message in the properties dialog for the checkpoint.

3. Select the checkpoint for which you create the alarm message in the drop-down list and all variables available for that checkpoint will be listed in the right part of the dialog.

4. Type the message and pick the variables you need.

5. Click OK when finished.

The new message should now appear in the message pool.

Probe Configuration


Connections Tab

This list will be populated with the various connections to servers that the sybase probe will monitor. You need to specify user name, password, and service name you want to use to connect to the instance. The password information is encrypted and placed into the configuration file. A connection can be used by more than one profile.

The list contains one predefined connection, which you may modify to your preferences. You may add, edit delete and copy connections.

Probe Configuration

20 sybase Guide

Edit Connection Dialog

Selecting the connection and choose Edit from the right pop-up menu, opens the Edit Connection dialog for editing.

The fields in the above dialog are explained below:

Advanced monitoring

Provides an option for enabling / disabling advance monitoring from the probe.

Monitor Option

Specifies monitoring tables / monitoring server for advance monitoring.

Description

Provides short description of the connection.

User ID

Defines the user-Id with authorization to read v$… views.

Password

Defines the valid password.

Server name

Specifies the server name as defined in the interface files.

Probe Configuration


Monitoring server

Defines the monitoring server name. This field becomes visible when monitoring option is set to monitoring server.

Retry attempts

Specifies the number of attempts the probe should try to repeat connection in case of failure. "0" means only the initial connection will be done.

Retry delay

Specifies the time for which the probe will wait between two connection attempts.

Timeout

Indicates the connection timeout.

Test button

Tests if the connection can be made. In positive case, it will return the instance name and its version number, in negative case the Sybase error message. The button will test first the Sybase server then the Monitoring server connection.

Probe Configuration

22 sybase Guide

Profiles Tab

The list contains a sample profile that you may modify to your preferences. Every profile will run as a separate thread. More than one profile can be used to monitor one instance. If the selected checkpoints need data from the Monitoring server, every profile will start its own data collector, which will run as a separate process. This way the probe can be configured to deploy available resources in best way and allows independent monitoring of several instances simultaneously.

Icons in the Profile List

■ Green icon in the profile line means the profile is active and running

■ Yellow icon means the profile is active but suspended (the ‘suspend’ /’resume’ button in the profile properties dialog allows stopping / starting profile monitoring dynamic, without deactivating /activating the probe).

■ Black icon shows the profile is inactive.

You may add, edit delete and copy profiles.

Probe Configuration


Edit Profile Dialog

Select the profile and choose Edit from the right pop-up menu to open the Edit Profile dialog for editing.

The Suspended /Resumed commands allow stopping / starting profile monitoring dynamic without deactivating /activating the probe.

The upper part of the window shows general profile properties and defaults and the lower portion displays a list of available checkpoints. The fields are explained below:

Active

Activates the profile.

Description

Provides short description of the profile.

Probe Configuration

24 sybase Guide

Heartbeat

Defines the interval in which all profile checkpoints schedules will be tested and trigger eventual checkpoint execution. This number should be common denominator to all used check interval values. The higher the value the lower is the profile overhead.

Connection

Defines the connection used in this profile. It has to be defined in Connections dialog before creating a profile.

Check Interval

Indicates the default value for check interval in the profile. Will be used if nothing else is defined in the checkpoint and overwrites the default checkpoint list setting.

Clear message

Defines the message name for clear alarm.

SQL Timeout

Every checkpoint query run asynchronously. In case the query reaches the SQL timeout, the checkpoint processing will be terminated and the next checkpoint will be started. Alarm is issued.

Message

Specifies the message name used for SQL timeout alarm.

Profile Timeout

Defines the maximum processing time for all checkpoints in the profile. If this timeout is reached, the interval processing is finished and the probe waits for next heartbeat to evaluate any checkpoint schedules. Alarm message is issued.

Message

Specifies the message name used for profile timeout alarm.

Timeout severity

Specifies the severity for timeout messages.

Suspended/Resumed

Diode that indicates if the profile is running (green) or suspended (red).

Alarm Source

Provides the possibility to change the source for issued alarms. If not used, default is assumed (robot IP).

Probe Configuration


Checkpoint Types

You can use two different strategies to handle checkpoints in a profile while defining a profile.

■ Template: You can decide to use checkpoint templates dynamic, which means that the checkpoints are defined globally (under the Templates tab) and represent the default settings. Every time you change the template value, it will reflect on all profiles using dynamic templates strategy.

■ Static: If you want to have specific settings valid just for one profile, you should right-click the checkpoint in the list and select Change to static.

Probe Configuration

26 sybase Guide

Now you can double-click the checkpoint to modify the properties and the settings will be valid for this profile only.

Note: If attempting to modify a template checkpoint in the Profile dialog without changing it to static as described above, you will get a warning as shown below:

There can be both template and static checkpoints mixed in one profile. If a checkpoint is managed as static, the checkpoint name will appear in the list with a blue color, and it will be marked as static in the column Type.

Types of Checkpoints

■ Static

To manage the properties for a checkpoint locally, change the checkpoint to static in your profile before modifying it. When modified, the new settings will be valid for this profile only.

■ Template

To edit the properties for a checkpoint template, double-click the checkpoint in the profile list or Templates tab. When modified, the new settings will be valid for all profiles, unless overruled by static settings in the profile.

Refer section Edit Checkpoint (see page 40) for a description of the checkpoint properties.

When deciding which checkpoints to activate/deactivate for a profile, see the section Checkpoints description for a description of the different checkpoints.

Probe Configuration


Templates Tab

The Templates tab contains a list of predefined set of checkpoints that you may use in your profiles. These checkpoints can be modified to your preferences.

By default, most checkpoints are active with a reasonable default threshold value. The checkpoint properties may be used in a profile, either dynamic (using the template values) or they can be added to the profile and managed statically in the profile.


Probe Configuration

28 sybase Guide

Status Tab

The status is presented in a hierarchal fashion with a profile name node and one or more checkpoint nodes (only active checkpoints are considered here). The highest status is propagated. Select the checkpoint in the navigation tree (to your left) to bring up the corresponding events.

The properties for an individual checkpoint object can also be modified here. Select a profile and a monitored checkpoint in the left pane. Then double-click an object in the right pane.

If the object belongs to a template object, you will be warned that a modification will make the checkpoint static for the selected profile.

Probe Configuration



Define New Checkpoint

You can define a new checkpoint using this functionality.

Follow these steps:

1. Select the Templates tab, right-click on the checkpoint list and select Create new.

The Add New User Template dialog pops up.

Probe Configuration

30 sybase Guide

2. Enter a name for the new checkpoint and click OK.

The Edit template checkpoint dialog opens.

3. By default, the General tab opens. Click the Query tab.

The difference to regular edit checkpoint dialog is the additional Query tab. SQL query is the data source and therefore the central piece for every checkpoint. It is recommended to test the query first with Sybase Central (or other tool) before you start to create new checkpoint.

The query has to return at least one numeric column, which will be used as threshold object name when creating thresholds (all numeric formats are supported). If the query returns more than one row, the probe needs unique identification per row which will be used as part of suppression key and QoS definition. The row key can be created by concatenating several columns in the checkpoint definition. Additional columns can be retrieved to be used in generated messages.

Note: Use rtrim and ltrim functions to remove leading and trailing blanks from string variables. Use explicit column names for manipulated values, avoid generated names, such as Col0 and Col1.

Queries are stored in separate files and not in the configuration file itself.

Probe Configuration


4. If you want to create new checkpoint, perform one of the following:

■ Select a connection from the Connection drop-down list, copy & paste the query in the query field and enter the query file name where you want the query to be stored. The query file name can contain full path, otherwise the file will be stored in the probe work directory.

■ Create the file first, use the button Read and then select a connection from the Connection drop-down list for change/test of the query.

5. On selecting the Interval modus check box, the variable $interval_value.i is added to the Message variables text box. The interval_value variable can be configured using the Raw Configure dialog box.

Probe Configuration

32 sybase Guide

6. Click Test to validate the connection settings. You can either test the query using a new connection or after editing an existing connection you can click the Test button to test the query.

Note: The connection information (i.e. User ID, Password, Server name etc) defined in this form must be same as defined in the Sybase profile.

You have to run a successful test every time you want to make any change to the query itself. The query test is also necessary for the probe to have all information about retrieved columns to be able to define all checkpoints variables.

7. Click the Edit button in the Message variables line to define checkpoints variables by.

A new window opens with a list of all available columns and their possible usage. You have to define their use and format.

Numeric columns can be used as:

■ Value – candidate for checkpoint checking with standard formatting

■ Value size – candidate for checking, formatted as file size (B, KB, MB, GB or TB)

■ Value int – candidate for checking, formatted as integer number

■ Information – no checking, standard formatting (if available 2 digits after comma)

Probe Configuration


Character columns:

■ Row key – candidate for row identification, string formatting.

■ Information – string formatting.

8. If your query returns more than one line, you need to define unique row key. To see which variables you can use you need to type the sign "$" into the Row identification line and a sublist with all suitable variables will appear.

Probe Configuration

34 sybase Guide

9. When the interval modus field is selected then the column metric type is assumed to be count instead of gauge.

10. Set the Interval modus check box.

■ If you check Interval modus, the probe will always subtract the variable value at the beginning of an interval from the value at the end of the interval and use the result for checking and QoS.

■ If you do not check the Interval modus check box, the value of variable as it returned from the query will be used for checking and QoS.

Probe Configuration


11. Define the rest of the checkpoint processing settings in the General tab, which are as follows:

■ Interval value

■ Sampling

■ Scheduling

■ Thresholds

■ Messages

■ QoS definitions

Probe Configuration

36 sybase Guide

12. Create a hint text in the Hint Editor tab, but it is not mandatory.

13. Save the definition and restart the probe to start using this new checkpoint.

Probe Configuration


Thresholds for Custom Defined Checkpoints

Every checkpoint needs to have at least one threshold but you can also define additional thresholds. The threshold values may be defined by modifying checkpoints in the respective profile. You can define several schedules per checkpoint and use the Scheduling functionality.

Alarms for a checkpoint can be configured in two ways:

■ Key alarms: These are the key specific alarms for any data column that are generated if the alarm condition matches the specified key value.

■ Default alarms: These are the default alarms for any data column that are generated based on the following two conditions:

■ When no key specific alarm is configured for the specified data column.

■ When there is a key specific alarm configured for that data column but it does not match the alarm condition.

The threshold identification consists of an object name, such as tablespace name, userid, and a threshold ID, which is numbered from 0. Threshold values have to be descending or ascending, depending on condition used in a checkpoint, starting with the highest severity threshold condition.

Probe Configuration

38 sybase Guide


Threshold object name

Defines the monitoring object name.

Condition

Specifies the comparison operator used for threshold evaluation.

Threshold value

Defines the value used for threshold evaluation.

Severity

Specifies the alarm severity.

Probe Configuration


Message

Defines the name of message used for threshold alarm.

Message text

Provides the text of the message, containing variables, which will be replaced in run time. If the message text is changed from a profile list, you will be forced to create new message.

Clear Message

Specifies the clear message to be sent.

Variables

Provides the list of variables available in the checkpoint.

Key Column Name

Specifies the column name for which you can generate a key specific alarm.

Key Column Value

Defines the key value on which an alarm condition would be compared for the specified column name. If the condition matches, the alarm will be generated.

Scheduling

Lets you select how to use the Schedules settings, if any.

rules

Selecting rules means to run according the rules described in the Schedules settings.

exceptions

Selecting exceptions means to run except the rules described in the Schedules settings.

Schedules

Refer section Schedules (see page 45).

Probe Configuration

40 sybase Guide

Edit Checkpoint

The checkpoint properties may be used in a profile either dynamic using the template values or they can be added to the profile and managed static in the profile.

■ Static

To edit the properties for a checkpoint locally for a profile, right-click the profile in the Checkpoints list in the profile dialog and change it to static. Then double-click the checkpoint to modify it. When modified, the new settings will be valid for this profile only.

■ Template

To edit the properties for a checkpoint template, double-click the checkpoint in the profile list or Templates tab. When modified, the new settings will be valid for all profiles, unless overruled by static settings in the profile.

The properties for checkpoints are described below:

Probe Configuration


The upper part of the window contains general checkpoint settings and the lower part contains two lists with threshold and schedule settings. The fields in the above dialog are explained below:

Description

Provides a short description of the purpose of the checkpoint.

Condition

Provides information describing how the threshold values are evaluated.

Clear severity

Specifies severity used for message issued in normal state.

Probe Configuration

42 sybase Guide

Send Quality of Service

Activates QoS values being sent into the QoS database. If not available in a checkpoint, check box is disabled.

Check Interval

Specifies the interval value used for this checkpoint. Every checkpoint can have a different check interval value. Default is taken from the profile definition, if not defined than from the default checkpoint list.

Clear message

Defines the message name used for clear alarm message.

Scheduling

Lets you select how to use the schedules settings, if any.

rules


exceptions


Threshold/Schedules

Refer section Thresholds (see page 43) and Schedules (see page 45).

Probe Configuration


Thresholds

The list contains the predefined set of monitoring profiles that you may use in your profiles and that you can modify to your preferences. By default, most profiles are active with a reasonable default threshold value. The threshold values may be defined by modifying checkpoints in the respective profile. Every checkpoint has to have at least one threshold, but there can be additional thresholds defined. You can also define several schedules per checkpoint and use the Scheduling functionality.

The threshold identification consists of an object name (if applicable), such as tablespace name, userid etc. and a threshold ID, numbered from 0. Threshold values have to be descending or ascending, depending on condition used in a checkpoint, starting with the highest severity threshold condition.

Probe Configuration

44 sybase Guide


Threshold object name

Monitoring object name, if applicable or default. Some special checkpoints have a second threshold called ‘count" (e.g. "locked_users").

Threshold value

Defines the value used for threshold evaluation.

Current interval value

Defines the severity used for message issued in normal state.

Severity

Specifies the alarm severity.

Message

Defines the name of message used for threshold alarm.

Message text

Provides the text of the message, containing variables, which will be replaced in run time. If the message text is changed from a profile list, you will be forced to create new message.

Variables

Provides the list of variables available in the checkpoint.

Scheduling

Lets you select how to use the Schedules settings, if any.

rules


exceptions


Schedules

Refer section Schedules (see page 45).

Probe Configuration


Schedules

If the schedules list is empty, the checkpoint will be executed in interval matter 24 hours a day. Additional to it there can be defined number of schedules per checkpoint, which can define additional rules to the check interval or exceptions of it. The rules and exceptions cannot be mixed in one checkpoint.

In principle, a schedule is a definition of an execution period (or execution break if exceptions used) with specified days, time from/to and date from/to values. Additionally, if only Date from and Time from is defined, first execution can be defined. Run once will cause the checkpoint run only once a day in the defined period (unlike multiple times if Run interval used).

Checkpoint Metrics

The following are the checkpoints metrics for this probe:

■ Count: Absolute number of events in the interval. It is calculated as delta between count at the beginning of the interval and at the end. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the instance".

■ Gauge: Absolute number, describing the actual state of the system.

■ Ratio: Calculated percentage, using interval counts. In the first interval, it is calculated from total counts (as the interval count cannot be calculated).

■ Average: Calculated using interval counts. In the starting interval, it is calculated from absolute counts.

■ Status: Absolute value like ‘ONLINE’ etc.

Probe Configuration

46 sybase Guide

Checkpoint description

■ Active_users – count: Monitors number of users, having at least one active transaction at the moment of the snapshot.

Source – query.

Table: sysprocesses, status = 'running'.

■ Buf_cachehit_ratio – ratio: Monitors buffer affectivity in interval. Calculated as (1 – (physical reads / logical reads)) *100

Source: API.

Item: SMC_NAME_DATA_CACHE_HIT,

SMC_NAME_DATA_CACHE_MISS

■ Check_dbalive – status: monitors Sybase server (connection and query execution).

Source: query.

select isnull(@@servername,'not available')+':'+@@version

■ Check_msalive – status: Monitors Monitoring server availability (connect).

Source: API (connect).

■ Commited_transactions – count: Monitors number of transactions committed in interval.

Source: API.

Item: SMC_NAME_XACT.

■ Database_count – count: Monitors number of databases in server.

Source: query.

Table: sysdatabases.

■ Database_size – ratio: Monitors free space in database and log files in %. It also monitors the free space available in database for mixed devices with both data and log files in %.

Source: query.

Table: sysusages.

■ Database_size_mb – count: Monitors free space in database and log files in MB. It also monitors the free space available in database for mixed devices with both data and log files in MB.

Source: query.

Table: sysusages.

■ Dead_locks – ratio: Monitors number of deadlocks per second in interval in database.

Source: API.

Probe Configuration


Item: SMC_NAME_DEADLOCK_CNT.

■ Lock_requests – ratio: Monitors total number of lock requests per second in interval.

Source: API.

Item: SMC_NAME_LOCK_CNT.

■ Lock_requests_db – ratio: Monitors number of lock requests per second per database in interval.

Source: API.

Item: SMC_NAME_LOCKS_GRANTED_IMMED,

SMC_NAME_LOCKS_GRANTED_WAITED,

SMC_NAME_LOCKS_NOT_GRANTED.

■ Lock_requests_granted_db – ratio: Monitors number of granted locks per second per database in interval.

Source: API.




■ lock_requests_waited_db – ratio: Monitors number of lock request waits per second per database in interval.

Source: API.




■ login_count – count: Monitors number of users currently logged to the server.

Source: query.

Table: sysprocesses.

■ Page_locks – ratio: Monitors number of page lock requests per second per database in interval.

Source: API.


■ Server_startup – count: Monitors number of days the Sybase server is up.

Source: query.

DATEDIFF(dd,crdate,getdate())).

■ Table_locks – ratio: Monitors number of table lock requests per second per database in interval.

Probe Configuration

48 sybase Guide

Source: API.


■ Total_disk_io – ratio: Monitors total number of I/O per second per device in interval.

Source: API.

Item: SMC_NAME_DEV_IO.

■ Total_disk_reads – ratio: Monitors number of read I/O per second per device in interval.

Source: API.

Item: SMC_NAME_DEV_READ.

■ Total_disk_writes – ratio: Monitors number of write I/O per second per device in interval.

Source: API.

Item: SMC_NAME_DEV_WRITE.

■ stp_cachehit_ratio – ratio: Monitors stored procedure cache efficiency in interval. Calculated as (1 – (physical reads / logical reads)) *100.

Source: API.

Item: SMC_NAME_STP_LOGICAL_READ,

SMC_NAME_STP_PHYSICAL_READ.

■ total_memory – count: Monitors total size of memory in kb/Mb, Sybase server has allocated at the moment of snapshot.

Source: API.

Item: SMC_NAME_MEM_CODE_SIZE

SMC_NAME_MEM_KERNEL_STRUCT_SIZE

SMC_NAME_MEM_SERVER_STRUCT_SIZE

SMC_NAME_MEM_PAGE_CACHE_SIZE

SMC_NAME_MEM_PROC_BUFFER

SMC_NAME_MEM_PROC_HEADER.

■ buffer_memory – count: Monitors size of memory in kb/Mb, Sybase server has allocated to data cache at the moment of snapshot.

Source: API.

Item: SMC_NAME_MEM_PAGE_CACHE_SIZE.

■ stp_memory – count: Monitors size of memory in kb/Mb, Sybase server has allocated to stored procedure cache at the moment of snapshot.

Source: API.

Probe Configuration


Item: SMC_NAME_MEM_PROC_BUFFER

SMC_NAME_MEM_PROC_HEADER.

■ log_contention – ratio: Monitors the percentage of times, of the total times when a user log cache was flushed into the transaction log, that it had to wait for the log semaphore in interval.

Source: API.

Item: SMC_NAME_LOG_CONTENTION_PCT.

■ locked_users – ratio: Monitors number of users waiting for a lock in interval.

Source: query.

Table: sysprocesses.

■ log_size – ratio: Monitors free space (%) in the log-file of a database.

Source: query.

Table: sysusages, sysdatabases.

■ db_device_size – ratio: Monitors free space (%) in database devices.

Source: query.

Table: sysdevices, sysusages, sysdatabases.

■ tempdb_device_size – ratio: Monitors free space (%) in temporary database devices.

Source: query.


■ device_size– ratio: Monitors free space (%) in devices.

Source: query.


■ active_connection_ratio - ratio: Monitors the ratio of active to available connections.

Source: Query

Table: sysprocesses, syscurconfigs, sysconfigures


Chapter 4: QoS Threshold Metrics

Many Nimsoft Monitor probes ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds.


sybase QoS Metrics (see page 51) sybase Alert Metrics Default Settings (see page 52)

sybase QoS Metrics

This section contains the QoS metrics for the sybase probe.

Monitor Name Unit Description

QOS_SYBASE_CHECK_BSALIVE Available Sybase Backup Server Availability

QOS_SYBASE_MONITOR_CONFIG % Sybase Configuration Parameter

QOS_SYBASE_DB_DEVICE_SIZE Percent Sybase Database Device Size Free in %

QOS_SYBASE_LOG_SIZE Percent Sybase Database Log Size Free in %

QOS_SYBASE_DATABASE_SIZE Percent Sybase Database Size Free in %

QOS_SYBASE_DATABASE_SIZE_MB Megabytes Sybase Database Size Free in MB

QOS_SYBASE_DEVICE_SIZE Percent Sybase Device Size Free in %

QOS_SYBASE_LOCKED_USERS Users Sybase Locked Users

QOS_SYBASE_LOGIN_COUNT Users Sybase Login Count

QOS_SYBASE_SERVER_CPU % Sybase Server CPU Usage

QOS_SYBASE_SERVER_IO % Sybase Server IO Busy

QOS_SYBASE_TEMPDB_DEVICE_SIZE Percent Sybase Tempdb Device Size Free in %

QOS_SYBASE_ACTIVE_CONNECTION_RATIO % Sybase Active Connection Ratio

QOS_SYBASE_DATABASE_COUNT Databases Sybase Active Databases

QOS_SYBASE_ACTIVE_USERS Users Sybase Active Users

sybase Alert Metrics Default Settings

52 sybase Guide

Monitor Name Unit Description

QOS_SYBASE_CHECK_DBALIVE Available Sybase Availability

QOS_SYBASE_DEVICE_IO % Sybase Device IO Busy

QOS_SYBASE_LOCK_REQUESTS Locks per second Sybase Lock Requests Total

QOS_SYBASE_LOCK_REQUESTS_DB Locks per second Sybase Lock Requests Database

QOS_SYBASE_LOCK_REQUESTS_GRANTED_DB Locks per second Sybase Lock Requests Granted

QOS_SYBASE_LOCK_REQUESTS_WAITED_DB Locks per second Sybase Lock Requests Waited

QOS_SYBASE_TOTAL_DISK_IO Ops. per sec Sybase Server Disk I/O

QOS_SYBASE_TOTAL_DISK_READS Reads per sec Sybase Server Disk Reads

QOS_SYBASE_TOTAL_DISK_WRITES Writes per sec Sybase Server Disk Writes

QOS_SYBASE_BUF_CACHEHIT_RATIO Percent Sybase Buffer Cachehit Ratio

QOS_SYBASE_DEAD_LOCKS Deadocks per second Sybase Dead-Locks

QOS_SYBASE_STP_CACHEHIT_RATIO Percent Sybase STP Cachehit Ratio

QOS_SYBASE_CHECK_MSALIVE Available Sybase MS Availability

QOS_SYBASE_PAGE_LOCKS Locks Sybase Page-Locks

QOS_SYBASE_TABLE_LOCKS Locks Sybase Table-Locks

QOS_SYBASE_COMMITTED_TRANSACTIONS Transactions/sec Sybase Commited Transactions per sec

QOS_SYBASE_LOG_CONTENTION Contentions/sec Sybase Log Contentions per sec

QOS_SYBASE_TOTAL_MEMORY Kb Sybase total memory

QOS_SYBASE_BUFFER_MEMORY Kb Sybase buffer cache memory

QOS_SYBASE_STP_MEMORY Kb Sybase stp cache memory


This section contains the alert metric default settings for the sybase probe.

Alert Metric

Warning Threshold

Warning Severity

Error Threshold Error Severity Description

active_connection_ratio - - 75 Major Monitors the ratio of active to available connections



Alert Metric

Warning Threshold

Warning Severity


active_users 1 Warning - - Monitors the number of active users

buf_cachehit_ratio - - 100 Major Monitors the buffer cache-hit ratio

buffer_memory 128 Warning - -

Monitors the amount of buffer cache memory allocated by ASE server

check_bsalive - - 1 Major Monitors connectivity to the backup server

check_dbalive - - 1 Major Monitors connectivity to the database server

check_msalive - - 1 Major Monitors connectivity to the monitor server

committed_transactions 1 Warning - - Monitors the number of total committed transactions per sec

database_count 1 Information - -

Monitors the number of active databases

database_size - - 5 Major Monitors free space (%) in the databases and the log-files

database_size_mb - - 10 Major Monitors free space (MB) in the databases and the log-files

db_device_size - - 5 Major Monitors free space (%) in database devices

dead_locks 1 Warning - - Monitors the number of dead-locks per sec in database

device_io - - 50 Major Monitors % of device IO busy by the ASE Server in interval

device_size - - 5 Major Monitors free space (%) in devices

lock_requests 10 Warning - - Monitors the total number of lock requests per second

lock_requests_db 1 Warning - - Monitors the total number of lock requests per database per second

lock_requests_granted_db 1 Warning - -

Monitors the number of lock requests granted per database per second


54 sybase Guide

Alert Metric

Warning Threshold

Warning Severity


lock_requests_waited_db 1 Warning - -

Monitors the number of lock requests waited per database per second

locked_users 0 Information - -

Monitors the number of locked users

log_contention 1 Warning - - Monitors the number of total log contentions per sec

log_size - - 15 Major Monitors free space (%) in the log-file of a database

login_count 1 Warning - - Monitors the number of users currently logged onto the server

monitor_config - - 80 Major Monitors level of static configuration parameter in %

page_locks 1 Warning - - Monitors the number of page-locks in database

server_cpu - - 50 Major Monitors % of CPU usage by the ASE Server in interval

server_io - - 30 Major Monitors % of IO busy by the ASE Server in interval

server_startup 120 Information - -

Monitors the database uptime (in days)

stp_cachehit_ratio - - 75 Major Monitor the stored procedure cache-hit ratio

stp_memory 128 Warning - - Monitors the amount of stp cache memory allocated by ASE server

table_locks 1 Warning - - Monitors the number of table-locks in database

tempdb_device_size - - 5 Major Monitors free space (%) in temporary database devices

total_disk_io 1 Warning - - Monitors the total disk I/O operations per sec per device

total_disk_reads 1 Warning - - Monitors the total number of disk reads per sec

total_disk_writes 1 Warning - - Monitors the total number of disk writes per sec



Alert Metric

Warning Threshold

Warning Severity


total_memory 512 Warning - - Monitors the amount of memory allocated by ASE server

Date post:	14-Feb-2018
Category:	Documents
Upload:	hoangkiet
View:	223 times
Download:	2 times

Nimsoft Monitor sybase Guidedocs.nimsoft.com/.../Catalog/sybase/4.1/sybase-4.1.pdf · sybase...

Documents