CA Nimsoft Monitor Snap

Transcription

1 CA Nimsoft Mitor Snap Cfigurati Guide for SQL Server Mitoring sqlserver v4.8 series

2 Legal Notices This line help system (the "System") is for your informatial purposes ly and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written csent of CA. This System is cfidential and proprietary informati of CA and protected by the copyright laws of the United States and internatial treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make e copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reas, it shall be your respsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplicati or disclosure by the United States Government is subject to the restrictis set forth in FAR Sectis , , and (c)(1) - (2) and DFARS Secti (b)(3), as applicable, or their successors. Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belg to their respective companies. Legal informati third-party and public domain software used in the Nimsoft Mitor soluti is documented in Nimsoft Mitor Third-Party Licenses and Terms of Use (

3 Ctents Chapter 1: Overview 7 About This Guide... 7 Related Documentati... 7 Precfigurati Requirements... 8 Supported Platforms... 8 Chapter 2: Cfigurati Details 9 sqlserver Node Checkpoints Node Cnecti-<Cnecti Name> Node Cfigure a Node Create New Cnecti Delete Cnecti Add Checkpoint Delete Checkpoint Add Row Identifier Delete Row Identifier Add Message Variable Delete Message Variable Add Threshold Delete Threshold Add Exclude Pattern Delete Exclude Pattern Add Include Pattern Delete Include Pattern Add QoS Delete QoS Delete Checkpoint Manage Profiles Delete Profile Add Profile Checkpoint Chapter 3: QoS Threshold Metrics 29 sqlserver Alert Metrics Default Thresholds sqlserver QoS Metrics Cfigure Dynamic Alarm Thresholds Ctents 3

4 Chapter 4: Known Issues 39 4 Cfigurati Guide for SQL Server Mitoring

5 Documentati Changes This table describes the versi history for this document. Versi Date What's New? 4.8 September 2013 Initial web-based GUI versi of this probe. (Previous versis of this probe are cfigured using Infrastructure Manager) Documentati Changes 5

6

7 Chapter 1: Overview The Nimsoft Mitor SQL Server probe cstantly mitors the internal performance and space allocati throughout the SQL Server database. The probe feeds essential informati that is based predefined criteria to the Nimsoft Mitor availability manager for the appropriate alert notificati when required. An extensive range of checkpoints can be selected and individually scheduled to meet the needs of specific mitoring requirements. This secti ctains the following topics: About This Guide (see page 7) Related Documentati (see page 7) Precfigurati Requirements (see page 8) About This Guide This guide is for the CA Nimsoft Mitor Administrator to help understand the cfigurati of the SQL Server Mitoring probe. This guide ctains the following informati: An overview of the SQL Server Mitoring probe. The related documentati for previous probe versis, release notes, and so. The cfigurati details of the probe including the informati for the fields that are required to cfigure the probe. The comm procedures that are used in the probe cfigurati. Field informati for the fields, required to cfigure the probe in the first-time deployment of the probe Important! The field descripti for intuitive terms in the GUI has not been included in the document. Related Documentati For related informati that may be of interest, see the following material: Related Documentati The Release Notes for the sqlserver probe (SQL Server Mitoring) Chapter 1: Overview 7

8 Precfigurati Requirements Precfigurati Requirements This secti ctains the precfigurati requirements for the SQL Server Mitoring probe. Supported Platforms Refer to the Nimsoft Compatibility Support Matrix for the latest informati supported platforms. See also the Support Matrix for Nimsoft Probes for the specific informati the sqlserver probe. 8 Cfigurati Guide for SQL Server Mitoring

9 Chapter 2: Cfigurati Details The SQL Server Mitoring probe runs the selected SQLs to extract vital informati about your SQL Servers. The informati is displayed as alarms and/or as a report and is useful to database administrators. The following informati is extracted and mitored out of the box: Database uptime Database state/status Number of databases available The data-file size for each database Log-file size for each database File-group size for each database Table size for each database The buffer cache-hit ratio The log-file cache-hit ratio The number of active users The number of users that are currently logged to the server Number of deadlocks per secd Number of transactis per secd Number of database pages reads/writes per secd Number of flush waits per secd Number of latch requests per secd Number of full scans (table or index) per secds The initial cfigurati of the SQL Server Mitoring probe is de by using the cfigurati tool (GUI), setting up e or more database instance profiles. The probe can run locally the database server or it can be cfigured to run as a remote client. Chapter 2: Cfigurati Details 9

10 sqlserver Node sqlserver Node The sqlserver node ctains the cfigurati details specific to the SQL Server Mitoring probe. In this node, you can view the probe informati and can cfigure the setup properties of the SQL Server Mitoring probe. You can also view a list of all alarm messages that are available in the SQL Server Mitoring probe. Navigati: sqlserver Set or modify the following values that are based your requirement: sqlserver > Probe This secti provides informati about the probe name, probe versi, start time of the probe, and the vendor who created the probe. sqlserver > General Cfig This secti allows you to cfigure the setup properties of the SQL Server Mitoring probe. Suppress All Alarm: Suppresses all the alarms in the SQL Server Mitoring probe, such as checkpoint alarms, profile alarms, SQL timeout alarms, and startup clear alarms. Default: Not selected Clear Alarm Restart: Clears all alarms when the SQL Server Mitoring probe is restarted. Default: Not selected Alarm Severity Filter: Sets a filter where severity levels are csidered as alarms. The SQL Server Mitoring probe is able to check many areas of the databases. Some events that are generated are vital and key to the performance and availability of the database. As a database administrator, you can pass the important events to the operatis center or helpdesk, so the event can trigger pagers and . Default: informati Log Size: Sets the size of the log file where the internal log messages of the probe are saved. Log Level: Specifies the level of details that are written to the log file. Default: 0 - Normal QoS V2 Compatibility: Selects the inserted data in the QoS database. Default: Selected sqlserver > Message pool This secti displays a list of all alarm messages that are available in the SQL Server Mitoring probe. 10 Cfigurati Guide for SQL Server Mitoring

11 sqlserver Node Text: Identifies the message text. i18n_token: Identifies the predefined alarms fetched from the database. sqlserver > Optis ic > Create New Cnecti This secti allows you to create various cnectis to instances that the SQL Server Mitoring probe mitors. You can specify the user ID, password, and server name you want to use to cnect to the instance. Authenticati: Provides the optis through which the probe cnects to the database server. The valid optis are SQL Server Authenticati and Windows authenticati. Default: SQL Server Authenticati Encrypti: Encrypts the communicati between the database and the server. User ID: If the SQL Server authenticati opti is selected, define the username for the SQL server. If the Windows authenticati opti is selected, define the username for the domain. Password: If the SQL Server authenticati opti is selected, define the password for the SQL server. If the Windows authenticati opti is selected, define the password for the domain. Retry attempts: If there is a failure, specify the number of attempts the SQL Server Mitoring probe repeats the cnecti. "0" means ly the initial cnecti is de. Default: 0 Retry delay: Specifies the time the SQL Server Mitoring probe waits between two cnecti attempts. Default: 0 Timeout: Specifies how lg the probe waist for an answer before it aborts the cnecti process. Default: 0 Timeout unit: Specifies the unit for the timeout. Default: sec Chapter 2: Cfigurati Details 11

12 sqlserver Node Checkpoints Node The Checkpoints node allows you to create a checkpoint, which allows you to mitor the SQL Server Mitoring probe. The default checkpoints are visible whereas custom checkpoints are created. Navigati: sqlserver Node > Checkpoints Set or modify the following values that are based your requirement: Checkpoint > Optis ic > Create New Checkpoint This secti allows you to create a checkpoint. Cnecti Name: Specifies the name of the cnecti. Query File: Defines the query file name where you want the query to be stored. Query: Defines the query for creating the checkpoint. 12 Cfigurati Guide for SQL Server Mitoring

13 sqlserver Node <Checkpoint Name> Node The checkpoint name node is used to cfigure Checkpoint cfig, Message Variable, General Cfig, Threshold, and Advance Database Settings. Note: The checkpoint appearing as a child node, under the sqlserver node are user-cfigurable. Hence, these checkpoints are referred as the checkpoint name node throughout this document. Navigati: sqlserver > Checkpoints > checkpoint name Set or modify the following values that are based your requirement: checkpoint name > Checkpoint Cfig This secti allows you to cfigure the checkpoint. Query File: Defines the query file name where you want the query to be stored. Query: Defines the query for creating the checkpoint. Interval Modus/Report Per Secd Metric: Allows the SQL Server Mitoring probe to subtract the variable value being generated at the beginning of an interval from the value that is generated at the end of the interval. checkpoint name > General Cfig This secti allows you to cfigure the general setup parameters of the checkpoint of SQL Server Mitoring probe. Active: Activates the checkpoint. Default: Not selected Cditi: Displays the informati how the informati is transmitted. Default: > = Check Interval: Specifies the default value of the check interval in the checkpoint. Check Interval unit: Specifies the unit of the check interval in the checkpoint. Samples: Specifies the number of samples and calculate an average value. This average value is compared to the alarm threshold specified. Default: 1 Note: Many checkpoints calculate an "interval value", therefore in the first interval there is no value at all (no threshold checking). Clear Severity: Specifies the severity of the message that is issued in normal state. Default: clear Chapter 2: Cfigurati Details 13

14 sqlserver Node SQL Timeout: Every checkpoint query runs asynchrously. If the query reaches the SQL timeout, the checkpoint processing will be terminated and the next checkpoint will be started. An alarm is issued. SQL Timeout unit: Specifies the unit of the SQL timeout. Clear Message: Specifies the message name to be used for the clear message. Use Exclude: Adds the objects to the exclude list of some of the checkpoints. Using excludes, you can define objects that you do NOT want to mitor the checkpoint. Default: Not selected Use Include: Adds the objects that you want to include in the mitoring list of some of the checkpoints. Default: Not selected checkpoint name > Row Identifier This secti allows you to pick the rows as variables to create an alarm message. If the query returns more than e row, the SQL Server Mitoring probe needs a unique identificati for each row. The row identifier is used as part of the suppressi key and QoS definiti. Name: Defines the name of the variable. Note: This secti appears ly in case of custom checkpoints. checkpoint name > Message Variable This secti allows you to pick the columns as variables to create an alarm message. Opens a list of all available columns and their possible usage. Note: This secti appears ly for the custom checkpoints. Name: Defines the name of the variable. Data Type: Specifies the data type of the variable of the new alarm message. Column Use: Specifies the column use of the variable. 14 Cfigurati Guide for SQL Server Mitoring

15 sqlserver Node checkpoint name > Quality of Service This secti allows you to edit and delete QoS definitis for a particular checkpoint. Abbreviati: Defines a descripti of the SQL checkpoint. Metric: Defines a measuring value of the SQL checkpoint. Max value: Defines the SQL value of the SQL checkpoint. checkpoint name > Advance Database Settings This secti allows you to cfigure the advance database settings of the SQL Server Mitoring probe. Ignore Database Snapshots: Allows you to ignore the database snapshots from mitoring that are read-ly copy of some database. Default: Not selected Ignore Database Restoring State: Allows you to ignore the databases from mitoring that are in restoring state. Default: Not selected Ignore Database Created in Last (Days): Allows you to ignore the databases that are created in the mentied days. Default: 1 Note: This secti appears ly for the backup_status checkpoint. checkpoint name > Exclude This secti allows you to add an exclude pattern, which enables you to define objects that you do not want to mitor the checkpoint. Note: This secti appears ly for the custom checkpoints. Exclude Pattern: Defines the exclude pattern. checkpoint name > Include This secti allows you to add an include pattern, which enables you to define objects that you want to mitor the checkpoint. Note: This secti appears ly for the custom checkpoints. Include Pattern: Defines the include pattern. Chapter 2: Cfigurati Details 15

16 sqlserver Node Mitors Node The Mitors node allows you to view the thresholds. You can add and delete the Quality of Service definitis from the SQL Server Mitoring probe. Navigati: sqlserver > Checkpoints > checkpoint name > Mitors Set or modify the following values that are based your requirement: Mitors > Quality of Service This secti allows you to cfigure the QoS for the SQL Server Mitoring probe. Unit: Defines the unit of the QoS. Abbreviati: Defines the abbreviati for the QoS. Metric: Specifies the metric of the QoS. Max value: Specifies the max value for the QoS. Object: Defines the object for the QoS. Mitors > Threshold This secti allows you to edit and delete threshold values for a particular checkpoint. Threshold object name: Defines the name of the threshold object. Cditi: Specifies the cditi of threshold breach. Threshold value: Defines threshold values of a particular checkpoint. Severity: Specifies the level of threshold breach. Message: Defines the type of message to be issued when the probe exceeds threshold values. Message text: Defines the ctent of the message to be issued when the probe exceeds threshold values. 16 Cfigurati Guide for SQL Server Mitoring

17 sqlserver Node Cnecti-<Cnecti Name> Node The Cnecti-cnecti name node displays informati the properties of the cnecti setup. This node also allows you to delete the cnecti setup. Note: The cnecti appearing as a child node, under the sqlserver node are user-cfigurable. Hence, these cnectis are referred as the Cnecti-cnecti name node throughout this document. Navigati: sqlserver > Cnecti-cnecti name Set or modify the following values that are based your requirement: Cnecti-cnecti name > Cnecti Setup This secti allows you to edit the properties of the cnecti setup. Chapter 2: Cfigurati Details 17

18 sqlserver Node <Cnecti Name> Node The cnecti name node allows you to define and modify the properties of the cnecti setup. Note: The cnecti appearing as a child node, under the Cnecti-cnecti name node are user-cfigurable. Hence, these cnectis are referred as the cnecti name node throughout this document. Navigati: sqlserver > Cnecti-cnecti name > cnecti name cnecti name > Cnecti Setup This secti allows you to modify the cnecti setup properties. Authenticati: Provides the optis through which the probe cnects to the database server. The valid optis are: SQL Server authenticati and Windows authenticati. Encrypti: Encrypts the communicati between the database and the server. Default: Not selected Detect domain automatically: Enables the automatic detecti of the domain. Default: Not selected Server Name: Specifies the server in which the database is located. Retry attempts: Specifies the number of attempts of cnecti to the database. Default: 0 Retry delay: Specifies the time interval between two attempts of cnecti to the database. Default: 0 Retry delay unit: Specifies the unit of measuring the time interval between two attempts. Default: 0 Timeout: Specifies the time interval after which the cnecti to the database is declared as failed. Default: 0 Timeout unit: Specifies the unit of measuring the time interval of cnecti failure. Default: sec cnecti name > Optis ic > Create new profile This secti allows you to create a profile, which enables to execute the mitors for a particular cnecti. 18 Cfigurati Guide for SQL Server Mitoring

19 sqlserver Node <Profile Name> Node The profile name node allows you to modify the profile parameters that you can modify as per your requirements. Every profile runs as a separate thread and multiple profiles can be used to mitor e instance. This way the probe can be cfigured to deploy available resources the best way and allows independent mitoring of several instances simultaneously. You can add checkpoints to a profile that can be made static as per profile settings. Note: The profile name appearing as a child node, under the cnecti name node is user-cfigurable. Hence, these profile names are referred as the profile name node throughout this document. Navigati: sqlserver > Cnecti-cnecti name > profile name Set or modify the following values that are based your requirement: profile name > Profile This secti allows you to modify the parameters of the profile. Heartbeat: Specifies the interval at which all profile checkpoints schedules are tested and triggers an eventual checkpoint executi. Note: This number is a comm denominator to all used check interval values. The higher the value the lower is the profile overhead. Default: 5 Heartbeat Unit: Specifies the unit for the heartbeat. Default: sec Cnecti: Specifies the cnecti that is used in the profile. Check Interval: Specifies the default value for the check interval in the profile. Default: 15 Check Interval Unit: Specifies the unit for the check interval. Clear message: Specifies the message for the timeout clear alarm. SQL Timeout: Specifies if the query reaches the SQL timeout, the checkpoint processing is terminated. The next checkpoint is started and an alarm is issued. Default: 5 Sql timeout unit: Specifies the unit for the SQL Timeout. Default: min Message: Specifies the message name for the profile timeout alarm. Delay Threshold: Specifies the timeout threshold for the profile delay alarm. Delay Threshold unit: Specifies the unit for the delay threshold. Message: Specifies the name of the message that is used for threshold alarm. Chapter 2: Cfigurati Details 19

20 Cfigure a Node Delay Severity: Specifies the severity of the alarm when the threshold delays the profile. Default: Major Timeout Severity: Severity for timeout messages. Default: Major Alarm Source: Allows you to override the source name of the alarm. Use FQDN As QoS Source: Allows the QoS source to be FQDN instead of a simple host name. Default: Not selected Cfigure a Node This procedure provides the informati to cfigure a particular secti within a node. Each secti within the node allows you to cfigure the properties of the SQL Server Mitoring probe. 1. Select the appropriate navigati path. 2. Update the field informati and click Save. The specified secti of the SQL Server Mitoring probe is cfigured. Create New Cnecti You can cfigure the probe to create a cnecti. 1. Click the Optis ic next to the sqlserver node in the navigati pane. 2. Click the Create new cnecti opti. 3. Update the field informati and click Submit. The new cnecti is saved under the Cnectis node in the navigati pane. 20 Cfigurati Guide for SQL Server Mitoring

21 Delete Cnecti Delete Cnecti You can delete an existing cnecti when you no lger want the SQL Server Mitoring probe to mitor it. 1. Click the Optis ic beside the Cnecti-cnecti name node that you want to delete. 2. Click the Delete cnecti opti. The cnecti is deleted. Add Checkpoint You can cfigure the SQL Server Mitoring probe to add a checkpoint. 1. Click the Optis ic next to the Checkpoints node in the navigati pane. 2. Click the Add New Checkpoint opti. 3. Update the field informati and click Submit. The new checkpoint is saved under the Checkpoints node in the navigati pane. Delete Checkpoint You can delete a checkpoint when you no lger need it. 1. Click the Optis ic next to the checkpoint name node in the navigati pane. 2. Click the Delete Checkpoint opti. The checkpoint is deleted from the navigati pane. Chapter 2: Cfigurati Details 21

22 Add Row Identifier Add Row Identifier You can add a row identifier in the SQL Server Mitoring probe for which reporting is de. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Row Identifier secti and then click New. 3. Update the field informati and click Save. The row identifier is added. Delete Row Identifier You can delete a row identifier in the SQL Server Mitoring probe when you no lger need it. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Row Identifier secti and then select the row identifier that you want to delete. 3. Update the field informati and click Save. The row identifier is deleted. Add Message Variable You can add message variables, define their usage, and format in the SQL Server Mitoring probe. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Variable secti and then click New. 3. Update the field informati and click Save. The variable is added. Note: You can add a variable for the custom checkpoints ly. 22 Cfigurati Guide for SQL Server Mitoring

23 Delete Message Variable Delete Message Variable You can delete message variables when you no lger need them. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Variable secti and then select the variable you want to delete. 3. Click Delete and then Save. The variable is deleted. Add Threshold You can add a threshold in the SQL Server Mitoring probe that defines the performance criteria to raise alarm when the threshold value is breached. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Threshold secti and then click New. 3. Update the field informati and click Save. The threshold is added, which allows you to raise an alarm when the threshold value is breached. Delete Threshold You can delete a threshold in the SQL Server Mitoring probe when you no lger need it. 1. Click the checkpoints name node in the navigati pane. 2. Go to Mitors node. 3. Go to the Threshold secti and then select the threshold you want to delete. 4. Click Delete. The threshold is deleted. Chapter 2: Cfigurati Details 23

24 Add Exclude Pattern Add Exclude Pattern You can add an exclude pattern in the SQL Server Mitoring probe. The exclude pattern allows you to define objects that you do not want to mitor the checkpoint. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Exclude secti and then click New. 3. Update the field informati and click Save. The exclude pattern is added, which allows you to define objects that you do not want to mitor the checkpoint. Note: You can add an exclude pattern for the custom checkpoints ly. Delete Exclude Pattern You can delete an exclude pattern in the SQL Server Mitoring probe when you no lger need it. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Exclude secti and then select the exclude pattern that you want to delete. 3. Click Delete. The exclude pattern is deleted. 24 Cfigurati Guide for SQL Server Mitoring

25 Add Include Pattern Add Include Pattern You can add include pattern in the SQL Server Mitoring probe. The include pattern allows you to define objects that you want to mitor the checkpoint. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Include secti and then click New. 3. Update the field informati and click Save. The include pattern is added that allows you to define objects that you want to mitor the checkpoint. Note: You can add an include pattern for the custom checkpoints ly. Delete Include Pattern You can delete an include pattern in the SQL Server Mitoring probe when you no lger need it. 1. Click the checkpoints name node in the navigati pane. 2. Go to the Include secti and then select the include pattern that you want to delete. 3. Click Delete. The include pattern is deleted. Add QoS You can add quality of service in the SQL Server Mitoring probe for a checkpoint. 1. Click the checkpoints name node in the navigati pane for which you want to add a QoS. 2. Click the Mitors node and then click New in the QoS secti. 3. Enter the field informati and click Submit. The QoS is added for that checkpoint. Chapter 2: Cfigurati Details 25

26 Delete QoS Delete QoS You can delete QoS in the SQL Server Mitoring probe when you no lger need it. 1. Click the checkpoints name node in the navigati pane for which you want to delete a QoS. 2. Click the Mitors node and then select the QoS you want to delete. 3. Click Delete. The QoS is deleted for that checkpoint. Delete Checkpoint You can delete ly custom checkpoints from the SQL Server Mitoring probe. 1. Click the Optis ic next to the checkpoint name node and then click New in the QoS secti. 2. Enter the field informati and click Submit. The QoS is added for that checkpoint. Manage Profiles You can cfigure the SQL Server Mitoring probe to create a profile various checkpoints for mitoring the SQL Server cnecti. You can then cfigure the profile to send the QoS messages and generate alarms respse time. 1. Click the Optis ic next to the cnecti name node in the navigati pane. 2. Click the Create new profile opti. 3. Update the field informati and click Submit. The profile is saved and you can cfigure the profile properties for mitoring the SQL Server cnecti. 26 Cfigurati Guide for SQL Server Mitoring

27 Delete Profile Delete Profile You can delete an existing profile when you no lger want the SQL Server Mitoring probe to mitor. 1. Click the Optis ic beside the profile name node that you want to delete. 2. Click the Delete Profile opti. The profile is deleted. Add Profile Checkpoint The Add Profile Checkpoint opti allows you to add a checkpoint in the SQL Server Mitoring probe. 1. Click the Optis ic beside the profile name node for which you want to add a checkpoint. 2. Go to Mitors node. 3. Click the Add Profile Checkpoints opti. The profile checkpoint is added. Chapter 2: Cfigurati Details 27

28

29 Chapter 3: QoS Threshold Metrics Many Nimsoft Mitor 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 secti describes the QoS metrics and provides the default QoS thresholds. This secti ctains the following topics: sqlserver Alert Metrics Default Thresholds (see page 29) sqlserver QoS Metrics (see page 35) Cfigure Dynamic Alarm Thresholds (see page 38) sqlserver Alert Metrics Default Thresholds The following table describes the default settings for the sqlserver alert metrics default threshold. Alarm Metric Warning Threshold Warning Severity Error Threshold Error Severity Active Cnecti Ratio Major Active Users Alloc Space Major Avg Fragmentati Major Avg Wait Time Backup Status Major Blocked Users Descripti Mitors ratio of active cnectis to total allowed cnectis. This checkpoint mitors the number of users having an active transacti at the moment of snapshot. Mitors free space in allocated data files regardless of auto-growth Mitors average fragmentati per allocati unit of an index or table. Mitors average lock wait time in ms. Mitors number of days since last backup. Mitors the number of user blocked. Chapter 3: QoS Threshold Metrics 29

30 sqlserver Alert Metrics Default Thresholds Cachehit Ratio 95 Warning 75 Major Availability Major Cnecti Memory Db Count Db Size Mitors the buffer cache-hit ratio Mitors cnectivity to the database instance Mitors amount of cnecti memory in Kb. Mitors the number of existing databases. Mitors space size (in Kb) for each database, log and data files together. Db State Major Mitors database state Deadlocks Major Differential Backup Status Major Fg Space Major Free Cnecti Major Free Space Major Full Scans Latch Waits Lock Memory Lock Requests Major Lock Timeouts Major Lock Waits Major Mitors the number of deadlocks per secd Mitors number of days since last differential backup Mitors free space in file groups Mitors % free cnectis to SQL Server instance. Mitors free space in database. Mitors the number of full scans (table or index) per secd Mitors the number of latch requests per secd Mitors amount of allocated lock memory in Kb Mitors the number of lock requests per secd Mitor the number of lock-timeouts per secd Mitor the number of lock waits per secd 30 Cfigurati Guide for SQL Server Mitoring

31 sqlserver Alert Metrics Default Thresholds Locked Users Locks Used Major Log Cachehit Ratio Major Log File Growths Log File Shrinks Log Flush Waits Mitors the number of users suspended by locks Mitors % of lock and lock owner blocks used. Mitors the log cache-hit ratio Mitors the usage (growth) of the transacti logs Mitors the usage (shrinking) of the transacti logs Mitors the number of log flush waits per secd Log File Size Major Mitors log file size Log File Usage Major Logic Fragment Major Login Count Lg Jobs Major Lg Queries Major Optimizer Memory Page Reads Page Writes informati Mitors free space in log files SQL Server 2000 ly! Mitors logical fragmentati of an index or table. Mitors the number of users currently logged to the server This checkpoint will find all jobs running lger then defined threshold in secds Mitors lg running queries (in secds) Mitors amount of optimizer memory in Kb. Mitors the number of database page reads per secd Mitors the number of database page writes per secd. Chapter 3: QoS Threshold Metrics 31

32 sqlserver Alert Metrics Default Thresholds Scan Density Major Server CPU Server IO Startup Cache Memory Table Space Total Memory informati Transacti Backup Status Major Transactis Major User CPU User Waits Workspace Memory Major Profile Timeout - - NA Major SQL Server 2000 ly! Mitors table/index fragmentati (density) Mitors % of CPU usage by SQL Server instance Mitors % of I/O busy for SQL Server instance. Mitors the uptime (in days) of the database server Mitors amount of SQL cache memory in Kb Mitors reserved space in user tables. Mitors total amount of dynamic server memory in Kb. Mitors number of days since last transacti log backup Mitors the number of transactis per secd Mitors % of CPU usage by user. Mitors time in secds, sessi spends waiting for a lock. Mitors % of workspace memory allocated. 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. SQL Error - - NA Major SQL Native client error. 32 Cfigurati Guide for SQL Server Mitoring

33 sqlserver Alert Metrics Default Thresholds SQL Timeout - - NA Major Every checkpoint query run asynchrously. In case the query reaches the SQL timeout, the checkpoint processing will be terminated and the next checkpoint will be started. Alarm is issued. Query Checksum - - NA Major Query manipulated. Query Error - - NA Major Suspect Pages Major Agent Job Failure Major Primary Status Major Secdary Status 1 Major Returns data in unsupported format. Checks if suspect pages are logged for databases. Mitors agent jobs which failed during the defined threshold interval (in minutes). Mitors collective status of agents for the primary log shipping database. Mitors collective status of agents for the secdary log shipping database. Chapter 3: QoS Threshold Metrics 33

34 sqlserver Alert Metrics Default Thresholds Primary Time Since Last Backup Major Secdary Time Since Last Copy Major Secdary Time Since Last Restore Major Mitors the durati(in minutes), since the last log backup was taken primary database server in log shipping envirment. Mitors the durati(in minutes), since the last log backup was copied secdary database server in log shipping envirment. Mitors the durati(in minutes), since the last log backup was restored secdary database server in log shipping envirment. 34 Cfigurati Guide for SQL Server Mitoring

35 sqlserver QoS Metrics Secdary Last Restored Latency Major Free Space with Available Disk Major Log File Usage with Available Disk Major Mitors durati(in minutes) from the creati of the last backup to restore of the backup in log shipping envirment. Mitors free space in filegroups after csidering the available disk size. Mitors free space in the database log files after csidering the available disk size. sqlserver QoS Metrics The following table describes the checkpoint metrics that can be cfigured using the sqlserver probe. Mitor Name Units Descripti QOS_SQLSERVER_active_cnecti_ratio Percent Active Cnecti Ratio QOS_SQLSERVER_active_users Count Active Users QOS_SQLSERVER_alloc_space Percent Free Allocated Space QOS_SQLSERVER_av_fragmentati Percent Average Fragmentati QOS_SQLSERVER_average_waittime ms Average Lock Wait Time QOS_SQLSERVER_backup_status Minutes Minutes Since Last Backup QOS_SQLSERVER_blocked_users Count Blocked Users QOS_SQLSERVER_buf_cachehit_ratio Percent Buffer Cachehit Ratio QOS_SQLSERVER_check_dbalive State Availability QOS_SQLSERVER_cnecti_memory Kb Cnecti Memory Allocated QOS_SQLSERVER_database_count Count Database Count QOS_SQLSERVER_database_size Megabytes Database Size QOS_SQLSERVER_database_state State Database State QOS_SQLSERVER_deadlocks Count/s Deadlocks QOS_SQLSERVER_differential_backup_status Minutes Minutes Since Last Differential Backup Chapter 3: QoS Threshold Metrics 35

36 sqlserver QoS Metrics Mitor Name Units Descripti QOS_SQLSERVER_fg_free_space Percent Filegroup Free Space QOS_SQLSERVER_free_cnectis Percent Free Cnectis QOS_SQLSERVER_free_space Percent Free Space QOS_SQLSERVER_full_scans Count/sec. Full Scans QOS_SQLSERVER_latch_waits Requests/Sec Latch Requests QOS_SQLSERVER_lock_memory Kb Lock Memory Allocated QOS_SQLSERVER_lock_requests Requests/Sec Lock Requests QOS_SQLSERVER_lock_timeouts Count/sec Lock Timeouts QOS_SQLSERVER_lock_waits Count/sec Lock Waits QOS_SQLSERVER_locked_users Count Locked Users QOS_SQLSERVER_locks_used Percent Percent Lock Blocks Used QOS_SQLSERVER_log_cachehit_ratio Percent Log Cachehit Ratio QOS_SQLSERVER_log_file_growths Count Log File Growths QOS_SQLSERVER_log_file_shrinks Count Log File Shrinks QOS_SQLSERVER_log_flush_waits Count/sec. Log Flush Waits OQS_SQLSERVER_logfile_size Count Log-file size QOS_SQLSERVER_logfile_usage Percent Log-file Usage QOS_SQLSERVER_logic_fragment Percent Logical Fragmentati QOS_SQLSERVER_login_count Count Login Count QOS_SQLSERVER_lg_queries Ne Mitors lg running queries in secds. QOS_SQLSERVER_mirror_sqlinstance State Mirror Sqlinstance QOS_SQLSERVER_mirror_state State Mirror State QOS_SQLSERVER_mirror_witness_server State Mirror Witness Server QOS_SQLSERVER_optimizer_memory Kilobyte Optimizer Memory QOS_SQLSERVER_page_reads Count/sec. Page Reads QOS_SQLSERVER_page_writes Count/sec. Page Writes QOS_SQLSERVER_scan_density Percent Object Density QOS_SQLSERVER_server_cpu Percent CPU Usage QOS_SQLSERVER_server_io Percent I/O busy QOS_SQLSERVER_server_startup Days Server Uptime 36 Cfigurati Guide for SQL Server Mitoring

37 sqlserver QoS Metrics Mitor Name Units Descripti QOS_SQLSERVER_sqlcache_memory Kb SQL Cache Memory Allocated QOS_SQLSERVER_table_space Kb User Table Space Usage QOS_SQLSERVER_total_memory Kb Total Dynamic Memory QOS_SQLSERVER_transacti_backup_status Minutes Minutes since last Transacti log backup QOS_SQLSERVER_transactis Transactis/sec Transactis QOS_SQLSERVER_user_cpu Percent CPU Usage QOS_SQLSERVER_workspace_memory Percent Workspace Memory Allocated QOS_SQLServer_ls_primary_status Status Primary Status QOS_SQLServer_ls_time_since_last_backup Minutes Minutes Since Last Backup QOS_SQL_Server_ls_secdary_status Status Secdary Status QOS_SQL_Server_ls_time_since_last_copy Minutes Minutes Since Last Copy QOS_SQL_Server_ls_time_since_last_restore Minutes Minutes Since Last Restore QOS_SQL_Server_ls_last_restored_latency Minutes Minutes Last Restored Latency QOS_SQL_Server_fg_freeSpace_with_avail_dis k QOS_SQL_Server_logfile_usage_with_avail_dis k Percent Percent SQL Server Filegroup Free Space csidering Available Disk Size Mitors free space in the database log files after csidering the available disk size. Chapter 3: QoS Threshold Metrics 37

38 Cfigure Dynamic Alarm Thresholds Cfigure Dynamic Alarm Thresholds Dynamic thresholds are cfigured at the QoS metric level in each probe that publishes an alarm for a QoS metric. Important! In order to create dynamic alarm thresholds, you must have the baseline_engine probe versi 2.0 installed the robot and cfigured. Follow these steps for each QoS metric where you want to cfigure dynamic thresholds: 1. Select a node in the tree to view any associated mitors and QoS metrics. 2. Select the mitor you want to modify in the table. 3. Select the Publish Data and Compute Baseline optis to enable the Dynamic Alarm Thresholds secti of the cfigurati. 4. Choose a threshold algorithm. There are three algorithms allowed for dynamic alarm thresholds: Note: You must indicate the directi for each algorithm, either increasing or decreasing. Scalar: Each threshold is a specific value from the computed baseline. Percent: Each threshold is a specific percentage of the computed baseline. Standard Deviati: Each threshold is a measure of the variati from the computed baseline. A large standard deviati indicates that the data points are far from the computed baseline and a small standard deviati indicates that they are clustered closely around the computed baseline. 5. Save your settings. 38 Cfigurati Guide for SQL Server Mitoring

39 Chapter 4: Known Issues Dynamic Populati of Message field with the correspding Message field selected in the drop-down list at runtime is a limitati of the ppm. On creating a checkpoint with the threshold, first select message and then save it. The message text field is updated with the correspding message text after reload. Chapter 4: Known Issues 39