Skip to main content

Database - Monitoring Parameters

Here you will find detailed information about monitoring parameters for Database monitored objects.

Monitoring parameters are the mechanism for you to configure how your systems are monitored. They are how you set configuration of how the agent runs, how checks are executed, thresholds for checks (when does a check go critical or warning) and much more. All Monitoring Parameters have a carefully chosen default value. As soon as you add a new system, Avantra uses these defaults. You may change these defaults by defining a parameter and by modifying its values. Monitoring Parameters can be defined for a single system, or for collections of systems using Monitoring Parameter Sets. You can also define your own Custom Monitoring Parameters for use within Custom Checks and automations.

note

For a Database instance of an SAP System, the Database Monitoring Parameters are treated as SAP System Monitoring Parameters.

ADADataExCrit

If the predicted point in time when the data area is exceeded is within the upcoming ADADataExCrit hours, the check status of ADA_DATAAREA is set to Critical.

Reference Data

Configures ChecksADA_DATAAREA
Default Value1
UnitHours

ADADataExWarn

If the predicted point in time when the data area is exceeded is within the upcoming ADADataExWarn hours, but not within the upcoming ADADataExCrit hours, the check status of ADA_DATAAREA is set to Warning, unless the ADADataUsageCrit threshold is exceeded.

Reference Data

Configures ChecksADA_DATAAREA
Default Value12
UnitHours

ADADataForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksADA_DATAAREA
Default ValueActive
UnitEnum

ADADataUsageCrit

If the data area usage exceeds the ADADataUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksADA_DATAAREA
Default Value98 %
Unit% or KB/MB/GB

ADADataUsageWarn

If data area usage exceeds the ADADataUsageWarn threshold, but does not exceed the ADADataUsageCrit threshold, the check status is set to Warning, unless the data area is exhausted in less than ADADataExCrit hours.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksADA_DATAAREA
Default Value95 %
Unit% or KB/MB/GB

ADALogExCrit

If the predicted point in time when the log area is exceeded is within the upcoming ADALogExCrit hours, the check status of ADA_LOGAREA is set to Critical.

Reference Data

Configures ChecksADA_LOGAREA
Default Value1
UnitHours

ADALogExWarn

If the predicted point in time when the log area is exceeded is within the upcoming ADALogExWarn hours, but not within the upcoming ADALogExCrit hours, the check status of ADA_LOGAREA is set to Warning, unless the ADALogUsageCrit threshold is exceeded.

Reference Data

Configures ChecksADA_LOGAREA
Default Value12
UnitHours

ADALogForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksADA_LOGAREA
Default ValueActive
UnitEnum

ADALogUsageCrit

If the log area usage exceeds the ADALogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksADA_LOGAREA
Default Value95 %
Unit% or KB/MB/GB

ADALogUsageWarn

If log area usage exceeds the ADALogUsageWarn threshold, but does not exceed the ADALogUsageCrit threshold, the check status is set to Warning, unless the data area is exhausted in less than ADADataExCrit hours.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksADA_LOGAREA
Default Value80 %
Unit% or KB/MB/GB

ANYBackupFullCritAge

If the last successful full backup run is older than ANYBackupFullCritAge days, the check status is set to Critical.

Reference Data

Configures ChecksADA_BACKUP
Default Value15
UnitDays

ANYBackupFullWarnAge

If the last successful full backup run is older than ANYBackupFullWarnAge days, but still below ANYBackupFullCritAge, the check status is set to Warning.

Reference Data

Configures ChecksADA_BACKUP
Default Value8
UnitDays

ANYBackupSelectRange

ANY_Backup looks for ANYBackupSelectRange days back to find maintenance reports of backups. The default value is 60 days, so usually, there is no need to change this parameter since backups must be made far more often.

Reference Data

Configures ChecksADA_BACKUP
Default Value60
UnitDays

ANYConnectionsNumCrit

If the number of connections to the database exceeds ANYConnectionsNumCrit, the check status of ANY_Connections is set to Critical.

Reference Data

Configures ChecksANY_Connections
Default Value200
UnitNumber

ANYConnectionsNumWarn

If the number of connections to the database exceeds ANYConnectionsNumWarn, but is still below ANYConnectionsNumCrit, the check status of ANY_Connections is set to Warning.

Reference Data

Configures ChecksANY_Connections
Default Value100
UnitNumber

ANYDBExCrit

If the predicted point in time when the dbspace is exceeded is within the upcoming ANYDBExCrit hours, the check status of ANY_DBSpaces is set to Critical.

Reference Data

Configures ChecksANY_DBSpaces
Default Value1
UnitHours

ANYDBExWarn

If the predicted point in time when the dbspace is exceeded is within the upcoming ANYDBExWarn hours, but not within the upcoming ANYDBExCrit hours, the check status of ANY_DBSpaces is set to Warning, unless the ANYDBUsageCrit threshold is exceeded.

Reference Data

Configures ChecksANY_DBSpaces
Default Value12
UnitHours

ANYDBForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksANY_DBSpaces
Default ValueActive
UnitEnum

ANYDBUsageCrit

If the dbspace usage exceeds the ANYDBUsageCrit threshold the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksANY_DBSpaces
Default Value95 %
Unit% or KB/MB/GB

ANYDBUsageWarn

If the data space usage of a database exceeds the ANYDBUsageWarn threshold the check status is set to Warning, unless the ANYDBUsageCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksANY_DBSpaces
Default Value80 %
Unit% or KB/MB/GB

ANYLogExCrit

If the predicted point in time when the transaction log space is exceeded is within the upcoming ANYLogExCrit hours, the check status of ANY_TransLog is set to Critical.

Reference Data

Configures ChecksNone
Default Value1
UnitHours

ANYLogExWarn

If the predicted point in time when the transaction log space is exceeded is within the upcoming ANYLogExWarn hours, but not within the upcoming ANYLogExCrit hours, the check status of ANY_TransLog is set to Warning, unless the ANYLogUsageCrit threshold is exceeded.

Reference Data

Configures ChecksNone
Default Value12
UnitHours

ANYLogForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksNone
Default ValueActive
UnitEnum

ANYLogUsageCrit

If the transaction log space usage exceeds the ANYLogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksNone
Default Value90 %
Unit% or KB/MB/GB

ANYLogUsageWarn

If the transaction log space usage of a database exceeds the ANYLogUsageWarn threshold, the check status is set to Warning unless the ANYLogUsageCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksNone
Default Value75 %
Unit% or KB/MB/GB

ANYMessagesExclude

ANYMessagesExclude does exactly the same as ANYMessagesStatExclude, except that it configures daily check ANY_Messages. Please see documentation of ANYMessagesStatExclude below.

Reference Data

Configures ChecksANY_Messages
Default Value
UnitString

ANYMessagesNumCrit

Defines a Critical threshold for the ANY_Messages check. The check status will be Critical if the number of not excluded server messages with severity ERR is equal to or above ANYMessagesNumCrit.

Reference Data

Configures ChecksANY_Messages
Default Value1
UnitNumber

ANYMessagesNumWarn

Defines a Warning threshold for the ANY_Messages check. ANYMessagesNumWarn behaves exactly as ANYMessagesStatNumWarn, except that it configures daily check ANY_Messages

Reference Data

Configures ChecksANY_Messages
Default Value1
UnitNumber

ANYMessagesStatExclude

You can use this parameter to exclude certain server messages from being evaluated in ANY_MessagesStat check. There are two types of exclude specifications: a simple one, which filters on the server message text only, and an advanced one, which must be specified in the format msg_severity|msg_category|msg_text. A server message must match all three items of a fully-featured exclude specification to be excluded. Multiple exclude specifications must be separated by semicolon ;. Leading and trailing blank spaces before or after the semicolon ; or pipe | character are gently ignored.

You may use wildcards * or ? to specify the server message text.

Example: Excludes

Simple exclude spec on server message text onlyStarting checkpoint of *
Advanced exclude spec filtering out ERR messages of category CHKPT and OTHERERR|CHKPT,OTHER|checkpoint
Advanced exclude spec filtering out ERR messages of any category with message text containing Shared MemoryERR||Shared*Memory
List of above exclude itemsStarting checkpoint of * ; ERR|CHKPT,OTHER|checkpoint ; ERR||Shared*Memory

Reference Data

Configures ChecksANY_MessagesStat
Default Value
UnitString

ANYMessagesStatNumCrit

Defines a Critical threshold for the ANY_MessagesStat check. ANYMessagesStatNumCrit behaves exactly as ANYMessagesNumCrit, except that it configures RealTime Monitoring check ANY_MessagesStat.

Reference Data

Configures ChecksANY_MessagesStat
Default Value1
UnitNumber

ANYMessagesStatNumWarn

Defines a Warning threshold for the ANY_MessagesStat check. The check status will be Warning if the number of not excluded server messages with severity ERR or WARN is equal to or above ANYMessagesStatNumWarn, unless the number of messages with severity ERR is equal to or above ANYMessagesStatNumCrit.

Reference Data

Configures ChecksANY_MessagesStat
Default Value1
UnitNumber

ANYMessagesStatTimespan

RealTime Monitoring check ANY_MessagesStat is designed to recover from check status Warning or Critical, so the check looks back for a time span defined by ANYMessagesStatTimespan only.

Reference Data

Configures ChecksANY_MessagesStat
Default Value60
UnitMinutes

AutoChangeDetectionIgnore

AutoChangeDetectionIgnore is used to exclude parameters from System Change Auto Detection. If, for example, a parameter value changes regularly and this behavior is well-known, you may add the parameter to the exclude list. The parameter value is still updated in the Avantra Database, but no change record will be created. Since there are several change detection objects, you must prefix the list with a keyword to indicate the object type.

For Databases, only DBPARAM is currently supported. Wildcard * is supported to define multiple parameters, e.g. DBPARAM: *MEMORY*, CPU_COUNT.

Reference Data

ConfiguresSystem Change Auto Detection
Default Value
UnitString

BackupAgeCrit

Description

If the last successful Backup is older than BackupAgeCrit days, the check status is set to Critical. You can override this value on a per-day level using the corresponding Monitoring Parameter Exception.

Reference Data

Configures ChecksADA_BACKUP, ORA_BACKUP, DB2_BACKUP, MSS_DBBACKUP, ORA_BRBACKUP, HDB_Backup, SYB_Backup, ANY_Backup, SIQ_Backup
Default Value7
UnitDays

BackupAgeWarn

If the last successful Backup is older than BackupAgeWarn days, but not older than BackupAgeCrit days, the check status is set to Warning. You can override this value on a per-day level using the corresponding Monitoring Parameter Exception.

Reference Data

Configures ChecksADA_BACKUP, ORA_BACKUP, DB2_BACKUP, MSS_DBBACKUP, ORA_BRBACKUP, HDB_Backup, SYB_Backup, ANY_Backup, SIQ_Backup
Default Value1
UnitDays

BackupResetRTMTime

This parameter defines the time period (in hours) after which a Warning or Critical DB2_BACKUPSTAT or ORA_BRBACKUPSTAT check status are set back to OK. This is to avoid showing the Warning or Critical condition all the time.

Reference Data

Configures ChecksORA_BRBACKUPSTAT, DB2_BACKUPSTAT
Default Value8
UnitHours

DB2BackupStatWaitTime

Defines the time interval between two DB2_BACKUPSTAT checks. By default the check runs in the BASIC cycle.

Reference Data

Configures ChecksNone
Default Value10
UnitMinutes

DB2CBOMaxAge

Defines the maximum age for the DB2 cost based optimizer statistics update where statistics are considered as up to date. DB2_CBO_STATS counts the number of tables/indexes not older than DB2CBOMaxAge. You may adapt this parameter if your CBO update runs are scheduled more or less frequently.

Reference Data

Configures ChecksDB2_CBO_STATS
Default Value7
UnitDays

DB2CBONumEntriesUpdCrit

If the number of tables or indexes with statistics not older than DB2CBOMaxAge days is below DB2CBONumEntriesUpdCrit, DB2_CBO_STATS result will be Critical.

Reference Data

Configures ChecksDB2_CBO_STATS
Default Value1000
UnitNumber

DB2CBONumEntriesUpdWarn

If the number of tables or indexes with statistics not older than DB2CBOMaxAge days is below DB2CBONumEntriesUpdWarn but not below DB2CBONumEntriesUpdCrit, the DB2_CBO_STATS result will be Warning.

Reference Data

Configures ChecksDB2_CBO_STATS
Default Value5000
UnitNumber

DB2DBRemote

You may set this parameter if the monitoring Avantra Agent has no access to the filesystem holding the DB2 installation, e.g. if you are using Agentless Monitoring.

In this case, the DB2_FSLOGARCH and DB2_DIAGLOG checks are not executed.

Reference Data

Configures ChecksDB2_FSLOGARCH, DB2_DIAGLOG
Default Value0
UnitBoolean

DB2DiagLogCountCrit

Defines a Critical threshold for the DB2_DIAGLOG check. The check status will be Critical if that many log entries considered as critical are found.

Reference Data

Configures ChecksDB2_DIAGLOG
Default Value1
UnitNumber

DB2DiagLogCountWarn

Defines a Warning threshold for the DB2_DIAGLOG check. The check status will be Warning if that many log entries considered as warning are found unless the DB2DiagLogCountCrit critical threshold is exceeded.

Reference Data

Configures ChecksDB2_DIAGLOG
Default Value1
UnitNumber

DB2DiagLogExprCrit

Designates an entry in the DB2 diagnostics log as critical.

Reference Data

Configures ChecksDB2_DIAGLOG
Default Value('%%level%%' eq 'Severe')
UnitExpression

DB2DiagLogExprWarn

Designates an entry in the DB2 diagnostics log as warning.

Reference Data

Configures ChecksDB2_DIAGLOG
Default Value('%%level%%' eq 'Error')
UnitExpression

DB2DiagLogTimeSpan

Consider only the last DB2DiagLogTimeSpan minutes of the log file.

Reference Data

Configures ChecksDB2_DIAGLOG
Default Value60
UnitMinutes

DB2ExpSQLExclude

Programs executing SQL statements on this list are not considered for the check result. Wildcard * is allowed. Multiple entries must be separated by (space). If your statement includes a space character, please escape it with a backslash .

Reference Data

Configures ChecksDB2_ExpSQL
Default Value%_T*
UnitString

DB2ExpSQLExcludeShow

Defines whether or not excluded statements, which will not contribute to the check result, are displayed.

Reference Data

Configures ChecksDB2_ExpSQL
Default Value0
UnitBoolean

DB2ExpSQLLogicalReadCrit

If for a particular SQL statement the amount of logical reads exceeds DB2ExpSQLLogicalReadCrit percent of the total number of reads of all statements, the check turns to Critical.

Reference Data

Configures ChecksDB2_ExpSQL
Default Value10
Unit%

DB2ExpSQLLogicalReadWarn

If for a particular SQL statement the amount of logical reads exceeds DB2ExpSQLLogicalReadWarn percent of the total number of reads of all statements but does not exceed DB2ExpSQLLogicalReadCrit, the check turns to Warning.

Reference Data

Configures ChecksDB2_ExpSQL
Default Value5
Unit%

DB2ExpSQLPhysicalReadCrit

If for a particular SQL statement the amount of physical reads exceeds DB2ExpSQLPhysicalReadCrit percent of the total number of reads of all statements, the check turns to Critical.

Reference Data

Configures ChecksDB2_ExpSQL
Default Value10
Unit%

DB2ExpSQLPhysicalReadWarn

If for a particular SQL statement the amount of physical reads exceeds DB2ExpSQLPhysicalReadWarn percent of the total number of reads of all statements but does not exceed DB2ExpSQLPhysicalReadCrit, the check turns to Warning.

Reference Data

Configures ChecksDB2_ExpSQL
Default Value5
Unit%

DB2FSLogActiveCrit

If the usage of file systems where the DB2 active log directories are located exceeds the DB2FSLogActiveCrit threshold, the check status is set to Critical.

The file systems of the active logs are taken from the DB2 parameters logpath and mirrorlogpath.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value85 %
Unit% or KB/MB/GB

DB2FSLogActiveWarn

If the usage of file systems where the DB2 active log directories are located exceeds the DB2FSLogActiveWarn threshold, the check status is set to Warning but only if the status is not Critical due to DB2FSLogActiveCrit.

The file systems of the active logs are taken from the DB2 parameters logpath and mirrorlogpath.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value70 %
Unit% or KB/MB/GB

DB2FSLogArchCrit

If the log archive filesystem usage exceeds the DB2FSLogArchCrit threshold the check status is set to Critical. The log archive filesystem is discovered automatically by Avantra Agent.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value85 %
Unit% or KB/MB/GB

DB2FSLogArchExCrit

If the predicted point in time when the filesystem limit is exceeded is within the upcoming DB2FSLogArchExCrit hours, the check result of DB2_FSLOGARCH is set to Critical.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value1
UnitHours

DB2FSLogArchExWarn

If the predicted point in time when the filesystem limit is exceeded is within the upcoming DB2FSLogArchExWarn hours, but not within the upcoming DB2FSLogArchExCrit hours, the check result of DB2_FSLOGARCH is set to Warning, unless the DB2FSLogArchExCrit threshold is exceeded.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value12
UnitHours

DB2FSLogArchForecast

Defines whether the Forecasting algorithm is active or inactive.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default ValueActive
UnitEnum

DB2FSLogArchWarn

If the log archive filesystem usage exceeds the DB2FSLogArchWarn threshold, but does not exceed the DB2FSLogArchCrit threshold, the check status is set to Warning.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value70 %
Unit% or KB/MB/GB

DB2LogExCrit

If the predicted point in time when the log space limit is exhausted is within the upcoming DB2LogExCrit hours, the check result of DB2_LOGUSAGE is set to Critical.

Reference Data

Configures ChecksDB2_LOGUSAGE
Default Value1
UnitHours

DB2LogExWarn

If the predicted point in time when the log space limit is exhausted is within the upcoming DB2LogExWarn hours, but not within the upcoming DB2LogExCrit hours, the check result of DB2_LOGUSAGE is set to Warning.

Reference Data

Configures ChecksDB2_LOGUSAGE
Default Value12
UnitHours

DB2LogForecast

Defines whether the Forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksDB2_LOGUSAGE
Default ValueActive
UnitEnum

DB2LogUsageCrit

If the log space exceeds the DB2LogUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_LOGUSAGE
Default Value95 %
Unit% or KB/MB/GB

DB2LogUsageWarn

If the log space exceeds the DB2LogUsageWarn threshold, but does not exceed the DB2LogUsageCrit threshold, the check status is set to Warning.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_LOGUSAGE
Default Value80 %
Unit% or KB/MB/GB

DB2NumFailArchLogsCrit

If the number of transaction log files located in the Failover Archive Path directory is above DB2NumFailArchLogsCrit, the check status is set to Critical. The Failover Archive Path directory is taken from the DB2 parameter failarchpath.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value5
UnitNumber

DB2NumFailArchLogsWarn

If the number of transaction log files located in the Failover Archive Path directory is above DB2NumFailArchLogsWarn but below DB2NumFailArchLogsCrit, the check status is set to Warning. The Failover Archive Path directory is taken from the DB2 parameter failarchpath.

Reference Data

Configures ChecksDB2_FSLOGARCH
Default Value1
UnitNumber

DB2TableSpaceExCrit

If the predicted point in time when the tablespace limit is exceeded is within the upcoming DB2TableSpaceExCrit hours, the check result of DB2_TABLESPACES is set to Critical.

Reference Data

Configures ChecksDB2_TABLESPACES
Default Value1
UnitHours

DB2TableSpaceExWarn

If the predicted point in time when the tablespace limit is exceeded is within the upcoming DB2TableSpaceExWarn hours, but not within the upcoming DB2TableSpaceExCrit hours, the check result of DB2_TABLESPACES is set to Warning, unless the DB2TableSpaceUsageCrit threshold is exceeded for some tablespace.

Reference Data

Configures ChecksDB2_TABLESPACES
Default Value12
UnitHours

DB2TableSpaceForecast

Defines whether the Forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksDB2_TABLESPACES
Default ValueActive
UnitEnum

DB2TableSpaceUsageCrit

If the use of one of the database tablespaces exceeds the DB2TableSpaceUsageCrit threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_TABLESPACES
Default Value98 %
Unit% or KB/MB/GB

DB2TableSpaceUsageWarn

If the use of one of the database tablespaces exceeds the DB2TableSpaceUsageWarn threshold, but none of them exceeds the DB2TableSpaceUsageCrit threshold, the check status is set to Warning, unless the DB2TableSpaceExCrit threshold is exceeded for some tablespace.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksDB2_TABLESPACES
Default Value95 %
Unit% or KB/MB/GB

DBConnectErrsCrit

Configures the DBCONNECT check status to turn from Warning to Critical when the number of failed database connection attempts is higher than the number defined in this monitoring parameter.

Reference Data

Configures ChecksDBCONNECT, DBCONNECT, DBCONNECT, DBCONNECT, DBCONNECT, DBCONNECT, DBCONNECT
Default Value1
UnitNumber

DBConnectJdbcUrl

Usually, the Avantra Agent automatically determines the URL to connect to the Database. In case the automatically determined URL does not work properly, you may override it using this parameter.

Available interpolations (macros):

%HOST%Database host
%PORT%Database port
%DATABASE%Database name
%HOSTPORT%HANA scale out host and port (only for HANA scale out environments). The format is host1:port;host2:port;… for any scaleout host.
%RSID%Real SAP SID
%USID%Unified SAP SID

Reference Data

Configures ChecksNone
Default Value
UnitString

FullBackupAgeCrit

If the last successful Full Backup is older than FullBackupAgeCrit days, the check status is set to Critical. You can define override this value on a per-day level using the corresponding Monitoring Exception Parameter.

Reference Data

Configures ChecksSYB_Backup, SIQ_Backup
Default Value14
UnitDays

FullBackupAgeWarn

If the last successful FullBackup is older than the defined number of days, but not older than FullBackupAgeCrit days, the check status is set to Warning. You can define override this value on a per-day level using the corresponding Monitoring Exception Parameter.

Reference Data

Configures ChecksSYB_Backup, SIQ_Backup
Default Value7
UnitDays

HDBAdmissionMaxRows

Maximum number of rows to return from table M_ADMISSION_CONTROL_EVENTS.

Reference Data

Configures ChecksHDB_Admission
Default Value50
UnitNumber

HDBAdmissionStatus

Define if the check result shall be reported as warning or critical status.

Reference Data

Configures ChecksHDB_Admission
Default ValueWarning
UnitEnum

HDBAdmissionTimeSpan

Configure how far in the past we are looking for entries in table M_ADMISSION_CONTROL_EVENTS.

Reference Data

Configures ChecksHDB_Admission
Default Value10
UnitMinutes

HDBAlertsErrorCountCrit

This monitoring parameter sets the HDB_Alerts check to critical, if the number of alerts with a rating Error found within a timespan defined by by HDBAlertsTimeSpan is equal to or above the defined threshold.

note

Please note that no matter how this parameter is defined, the check status will at least be warning if at least one alert with high priority is found within HDBAlertsTimeSpan.

Reference Data

Configures ChecksHDB_Alerts
Default Value1
UnitNumber

HDBAlertsExcludeIDs

You can exclude alerts from contributing to the check status by specifying the alert's ID using this parameter. Multiple entries must be separated by spaces, comma, or semicolon. The syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right alerts will still be excluded as long as numeric values are found.

note

Excluded alerts will still be reported in the check result's overview table. They will be marked with string (Excluded) in the Alert ID column and will not be colored.

Reference Data

Configures ChecksHDB_Alerts
Default Value
UnitString

HDBAlertsHighCountCrit

This monitoring parameter sets the HDB_Alerts check to critical, if the number of alerts with a rating High found within a timespan defined by by HDBAlertsTimeSpan is equal to or above the defined threshold.

note

Please note that no matter how this parameter is defined, the check status will at least be warning if at least one alert with high priority is found within HDBAlertsTimeSpan.

Reference Data

Configures ChecksHDB_Alerts
Default Value1
UnitNumber

HDBAlertsLowCountWarn

This monitoring parameter sets the HDB_Alerts check to warning, if the number of alerts with a rating Low found within a timespan defined by by HDBAlertsTimeSpan is equal to or above the defined threshold.

note

HDB_Alerts will return a check status of OK if no alerts with priority above Low are found and if the number of Low priority alerts is below the threshold.

Reference Data

Configures ChecksHDB_Alerts
Default Value20
UnitNumber

HDBAlertsMediumCountWarn

This monitoring parameter sets the HDB_Alerts check to warning, if the number of alerts with a rating Medium found within a timespan defined by by HDBAlertsTimeSpan is equal to or above the defined threshold.

note

HDB_Alerts will return a check status of OK if no alerts with priority above Medium are found and if the number of Low priority alerts is below the HDBAlertsLowCountWarn threshold.

Reference Data

Configures ChecksHDB_Alerts
Default Value1
UnitNumber

HDBAlertsTimeSpan

Restricts the watch period of HDB_Alerts.

Reference Data

Configures ChecksHDB_Alerts
Default Value60
UnitMinutes

HDBBackupCompleteSelectRange

Restricts the watch period of HDB_Backup.

Reference Data

Configures ChecksHDB_Backup
Default Value60
UnitDays

HDBBackupPreparedWaitingOnSnapDelay

If the backup status is “prepared” and it started less than 5 Minutes earlier, then the check is OK.

Reference Data

Configures ChecksNone
Default Value5
UnitMinutes

HDBCertificateValidityCrit

This monitoring parameter triggers the HDB_Certificates) check status to change to critical if the expiration date of a certificates is in less days, from now, than the defined value.

Reference Data

Configures ChecksHDB_Certificates
Default Value5
UnitDays

HDBCertificateValidityWarn

This monitoring parameter triggers the HDB_Certificates) check status to change to warning if the expiration date of a certificates is in less days, from now, than the defined value, but more than HDBCertificateValidityCrit.

Reference Data

Configures ChecksHDB_Certificates
Default Value50
UnitDays

HDBCertificateValidityIgnore

This monitoring parameter is used to define a time (day) value that once the age of an expired certificate is greater than the value, the certificate is ignored from the HDB_Certificates) check result.

Reference Data

Configures ChecksHDB_Certificates
Default Value10
UnitDays

HDBCertificatePurposes

This monitoring parameter configures HDB_Certificates to only monitor certificate collection purposes listed.

By default, this is set to empty and all purposes are considered.

Accepted list items are:

  • SSL
  • SAML
  • JWT
  • X509
  • SAP LOGON
  • DATABASE REPLICATION
  • LDAP
  • REMOTE SOURCE

Reference Data

Configures ChecksHDB_Certificates
Default Value
UnitEnumX

HDBCertificateUsages

This monitoring parameter configures the HDB_Certificates) check to only monitor certificate usages listed.

By default, this is set to empty and will include all certificate usages.

Reference Data

Configures ChecksHDB_Certificates
Default Value
UnitEnumX

HDBCPULoadAverageTime

Defines the time span (in minutes) that is taken into account for the HDB_CPULoad Check.

Reference Data

Configures ChecksHDB_CPULoad
Default Value10
UnitMinutes

HDBCPULoadCrit

If one of the node's CPU load exceeds this threshold, the check status turns to Critical.

Reference Data

Configures ChecksHDB_CPULoad
Default Value90
Unit%

HDBCPULoadWarn

If one of the node's CPU load exceeds this threshold, the check status turns to Warning, unless the Critical threshold HDBCPULoadCrit is exceeded for any node.

Reference Data

Configures ChecksHDB_CPULoad
Default Value75
Unit%

HDBDeltaMergesNumCrit

If there are more delta merges than the threshold taking longer than HDBDeltaMergesTimeCrit amount of time the check status of HDB_DeltaMerges turns to critical.

Reference Data

Configures ChecksHDB_DeltaMerges
Default Value10
UnitNumber

HDBDeltaMergesNumWarn

If there are more delta merges than the threshold taking longer than HDBDeltaMergesTimeWarn amount of time the check status of HDB_DeltaMerges turns to warning, unless the critical threshold is exceeded.

Reference Data

Configures ChecksHDB_DeltaMerges
Default Value5
UnitNumber

HDBDeltaMergesTimeCrit

If there are more delta merges than HDBDeltaMergesNumCrit taking longer than the defined amount of time the check status of HDB_DeltaMerges turns to critical.

Reference Data

Configures ChecksHDB_DeltaMerges
Default Value20
UnitMinutes

HDBDeltaMergesTimeWarn

If there are more delta merges than HDBDeltaMergesNumWarn taking longer than the defined amount of time the check status of HDB_DeltaMerges turns to warning, unless the critical threshold is exceeded.

Reference Data

Configures ChecksHDB_DeltaMerges
Default Value10
UnitMinutes

HDBDisksUsageCrit

f the usage of the disks containing the storage device exceeds the threshold the check status is set to Critical.

Reference Data

Configures ChecksHDB_Disks
Default Value90 %
Unit% or KB/MB/GB

HDBDisksUsageWarn

If the usage of the disks containing the storage device exceeds the threshold, the check status is set to Warning, unless the HDBDisksUsageCrit threshold is exceeded.

Reference Data

Configures ChecksHDB_Disks
Default Value80 %
Unit% or KB/MB/GB

HDBDisksLogExCrit

If the predicted point in time when the SAP HANA Log Area space is exceeded lies within the upcoming defined hours, the check status of HDB_DisksLog is set to Critical.

Reference Data

Configures ChecksHDB_DisksLog
Default Value1
UnitHours

HDBDisksLogExWarn

If the predicted point in time when the SAP HANA Log Area space is exceeded lies within the upcoming defined hours, the check status of HDB_DisksLog is set to warning, unless the threshold for a critical status has been met.

Reference Data

Configures ChecksHDB_DisksLog
Default Value12
UnitHours

HDBDisksLogUsageCrit

If the usage of the filesystems containing the log areas exceeds the threshold, the check status is set to Critical.

Reference Data

Configures ChecksHDB_DisksLog
Default Value20 %
Unit% or KB/MB/GB

HDBDisksLogUsageWarn

If the usage of the filesystems containing the log area exceeds the threshold, the check status is set to Warning, unless the HDBDisksLogUsageCrit threshold is exceeded.

Reference Data

Configures ChecksHDB_DisksLog
Default Value10 %
Unit% or KB/MB/GB

HDBDisksLogBackupUsageCrit

If the usage of the filesystems containing the log backups exceeds the threshold, the check status is set to Critical.

Reference Data

Configures ChecksHDB_DisksLogBackup
Default Value85 %
Unit% or KB/MB/GB

HDBDisksLogBackupUsageWarn

If the usage of the filesystems containing the log area exceeds the threshold, the check status is set to Warning, unless the HDBDisksLogBackupUsageCrit threshold is exceeded.

Reference Data

Configures ChecksHDB_DisksLogBackup
Default Value70 %
Unit% or KB/MB/GB

HDBExcludeStorageDeviceIDs

You can exclude storage devices from contributing to the check status by specifying the storage device ID using this parameter. Multiple entries must be separated by comma or semicolon. The syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right storage devices will still be excluded as long as numeric values are found.

note

Excluded storage devices will still be reported in the check result's overview table. They will be marked as Excluded Yes.

Reference Data

Configures ChecksHDB_Disks, HDB_DisksLogBackup, HDB_DisksLog
Default Value
UnitString

HDBExcludeStorageIDs

You can exclude storage devices from contributing to the check status by specifying the storage ID using this parameter. Multiple entries must be separated by comma or semicolon. The syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right storage devices will still be excluded as long as numeric values are found.

note

Excluded storage devices will still be reported in the check result's overview table. They will be marked as Excluded Yes.

Reference Data

Configures ChecksHDB_Disks, HDB_DisksLogBackup, HDB_DisksLog
Default Value
UnitString

HDBExcludeStorageTypes

You can exclude storage devices from contributing to the check status by specifying the storage device type (e.g. Data, Log_backup) using this parameter. Multiple entries must be separated by comma or semicolon. The exclude list may contain leading and/or trailing spaces, and spaces between the items. They will be trimmed away to make sure that the right storage devices will be excluded.

note

Excluded storage devices will still be reported in the check result's overview table. They will be marked as Excluded Yes.

Reference Data

Configures ChecksHDB_Disks, HDB_DisksLogBackup, HDB_DisksLog
Default Value
UnitString

HDBExpSQLExclude

Programs executing SQL statements on this list are not considered for the check result. Wildcard * is allowed. Multiple entries must be separated by , (comma). If your statement includes a comma character, please escape it with a backslash \.

Reference Data

Configures ChecksHDB_ExpSQL
Default Value
UnitString

HDBExpSQLTimePctCrit

If the total execution time of an SQL statement compared to the total execution time of all SQL statements exceeds the defined percent, the check status of HDB_ExpSQL turns to Critical.

Reference Data

Configures ChecksHDB_ExpSQL
Default Value10
Unit%

HDBExpSQLTimePctWarn

If the total execution time of an SQL statement compared to the total execution time of all SQL statements exceeds the defined percent the check status of HDB_ExpSQL turns to Warning, unless the Critical threshold is exceeded.

Reference Data

Configures ChecksHDB_ExpSQL
Default Value5
Unit%

HDBJobNameExclude

You can exclude job names from contributing to the check status by specifying the job names using this parameter. Multiple entries must be separated by comma or semicolon. The syntax is forgiving, i. e. leading, trailing or multiple spaces will not harm and the right jobs will still be excluded as long as the job name matches.

You may use placeholders ? (single character) and * (any number of characters) to specify a job name pattern to be excluded.

note

Excluded jobs will still be reported in the check result's overview table. They will be marked with an icon that shows an Excluded... tooltip text.

Reference Data

Configures ChecksHDB_JobRuntime
Default ValueBackup
UnitString

HDBJobRuntimeCrit

If jobs are found running longer than the defined number of minutes the check status is set to Critical.

Reference Data

Configures ChecksHDB_JobRuntime
Default Value10
UnitMinutes

HDBJobRuntimeWarn

If jobs are found running longer than the defined number of minutes the check status is set to Warning, unless there is a job found running longer than HDBJobRuntimeCrit minutes.

Reference Data

Configures ChecksHDB_JobRuntime
Default Value5
UnitMinutes

HDBLandscapeSeverity

Define the severity of HDB_Landscape in case of a problem.

Reference Data

Configures ChecksHDB_Landscape
Default ValueWarning
UnitEnum

HDBLicenseExpireTimeCrit

If the license has an expiration date, the Check HDB_License turns to Critical if less than the defined number of days are left until expiration.

Reference Data

Configures ChecksHDB_License
Default Value7
UnitDays

HDBLicenseExpireTimeWarn

If the license has an expiration date, the Check HDB_License turns to Warning if less than the defined number of days are left until expiration, unless the Critical threshold HDBLicenseExpireTimeCrit is exceeded.

Reference Data

Configures ChecksHDB_License
Default Value30
UnitDays

HDBLicenseMemoryConsumCrit

Memory relation of the used memory to the licensed memory.

Reference Data

Configures ChecksHDB_License
Default Value90
Unit%

HDBLicenseMemoryConsumWarn

Memory relation of the used memory to the licensed memory.

Reference Data

Configures ChecksHDB_License
Default Value80
Unit%

HDBLogBackupConsecutiveFailedThreshold

This monitoring parameter defines a threshold where if the number of consecutive failed log backups is higher than the threshold, the HDB_LogBackup check status is set to Critical.

Reference Data

Configures ChecksHDB_LogBackup
Default Value1
UnitNumber

HDBLogBackupTimeSpan

Defines the time span in minutes which is used to examine log backups back from the current moment.

Reference Data

Configures ChecksHDB_LogBackup
Default Value60
UnitNumber

HDBLogFilesCritCount

If more locked log files are found the HDB_LogFiles check status will change to critical.

Reference Data

Configures ChecksHDB_LogFiles
Default Value5
UnitNumber

HDBLogFilesWarnCount

If more locked log files are found the HDB_LogFiles check status will change to warning.

Reference Data

Configures ChecksHDB_LogFiles
Default Value3
UnitNumber

HDBMemoryPeakUsageCrit

If the Database peak memory usage compared to the allocation limit exceeds the defined threshold, the check status is set to Critical.

Reference Data

Configures ChecksHDB_MemoryPeak
Default Value95 %
Unit% or KB/MB/GB

HDBMemoryPeakUsageWarn

If the Database peak memory usage compared to the allocation limit exceeds the defined threshold, the check status is set to warning, unless the HDBMemoryPeakUsageCrit threshold has been met.

Reference Data

Configures ChecksHDB_MemoryPeak
Default Value90 %
Unit% or KB/MB/GB

HDBMemoryPhysicalUsageCrit

If a host's physical memory usage exceeds the defined threshold, the check status is set to Critical.

Reference Data

Configures ChecksHDB_MemoryPhysical
Default Value95 %
Unit% or KB/MB/GB

HDBMemoryPhysicalUsageWarn

If a host's physical memory usage exceeds the defined threshold, the check status is set to warning, unless the threshold for HDBMemoryPhysicalUsageCrit has been met.

Reference Data

Configures ChecksHDB_MemoryPhysical
Default Value90 %
Unit% or KB/MB/GB

HDBMemoryServicesUsageCrit

If a services memory usage exceeds a defined percent or a service's free memory falls below a defined number of KB/MB/GB, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksHDB_MemoryServices
Default Value95 %
Unit% or KB/MB/GB

HDBMemoryServicesUsageWarn

If a services memory usage exceeds a defined percent or a service's free memory falls below a defined number of KB/MB/GB, the check status is set to warning, unless the HDBMemoryServicesUsageCrit threshold is met.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksHDB_MemoryServices
Default Value90 %
Unit% or KB/MB/GB

HDBSystemReplDelayCrit

Configures the Critical threshold for system replication delay in seconds.

Reference Data

Configures ChecksHDB_SystemReplDelay
Default Value3600
UnitSeconds

HDBSystemReplDelayWarn

Configures the warning threshold for system replication delay in seconds.

Reference Data

Configures ChecksHDB_SystemReplDelay
Default Value30
UnitSeconds

HDBSystemReplIgnoreReplicationStatus

When set to True, this monitoring parameter configures HDB_SystemReplication to ignore the REPLICATION_STATUS column when considering the check status.

Reference Data

Configures ChecksHDB_SystemReplication
Default ValueFalse
UnitBoolean

HDBSystemReplIgnoreSecondaryActive

When set to True, this monitoring parameter configures HDB_SystemReplication to ignore the SECONDARY_ACTIVE_STATUS column when considering the check status.

Reference Data

Configures ChecksHDB_SystemReplication
Default ValueTrue
UnitBoolean

HDBSystemReplIgnoreSecondaryFullyRecoverable

When set to True, this monitoring parameter configures HDB_SystemReplication to ignore the SECONDARY_FULLY_RECOVERABLE column when considering the check status.

Reference Data

Configures ChecksHDB_SystemReplication
Default ValueFalse
UnitBoolean

HDBSystemReplNotFoundStatus

If system replication is not set up for a HANA database, HDB_SystemReplication will return an OK check status by default. You can change this using the this parameter, thereby enforcing that system replication is configured.

Reference Data

Configures ChecksHDB_SystemReplication
Default ValueOK
UnitEnum

HDBTableAllocationCrit

The relation of the total memory pools in % to the global allocation limit.

Reference Data

Configures ChecksHDB_TableAllocationUse
Default Value50
Unit%

HDBTableAllocationWarn

The relation of the total memory pools in % to the global allocation limit.

Reference Data

Configures ChecksHDB_TableAllocationUse
Default Value30
Unit%

HDBTableRowCountCrit

Value in relation to rows to the upper limit of 2 billion rows.

Reference Data

Configures ChecksHDB_TableRowCount
Default Value90
Unit%

HDBTableRowCountExclude

This parameter defines the tables, by name, that can be excluded from HDB_TableRowCount. Wildcards can be used.

Reference Data

Configures ChecksHDB_TableRowCount
Default Value
UnitString

HDBTableRowCountTopTables

Define how many top tables the check monitors.

Reference Data

Configures ChecksHDB_TableRowCount
Default Value10
UnitNumber

HDBTableRowCountWarn

Value in relation to rows to the upper limit of 2 billion rows.

Reference Data

Configures ChecksHDB_TableRowCount
Default Value80
Unit%

HDBTenantMemoryPeakUsageCrit

If the Database tenant peak memory usage compared to the allocation limit exceeds the threshold, the check status is set to Critical.

Reference Data

Configures ChecksHDB_TenantMemoryPeak
Default Value95 %
Unit% or KB/MB/GB

HDBTenantMemoryPeakUsageWarn

If the Database tenant peak memory usage compared to the allocation limit exceeds the threshold, the check status is set to warning, unless the HDBTenantMemoryPeakUsageCrit threshold has been met.

Reference Data

Configures ChecksHDB_TenantMemoryPeak
Default Value90 %
Unit% or KB/MB/GB

MSSBackupAgeMasterCrit

If the last successful backup of the MSSQL primary configuration Database is older than the defined number of days, the check status is set to Critical.

Reference Data

Configures ChecksMSS_DBBACKUP
Default Value14
UnitDays

MSSBackupAgeMasterWarn

If the last successful backup of the MSSQL primary configuration Database is older than the defined number of days, but not older than MSSBackupAgeMasterCrit days, the check status is set to Warning.

Reference Data

Configures ChecksMSS_DBBACKUP
Default Value7
UnitDays

MSSBackupAgeMsdbCrit

If the last successful backup of the MSSQL MSDB Database is older than the defined number of days, the check status is set to Critical.

Reference Data

Configures ChecksMSS_DBBACKUP
Default Value14
UnitDays

MSSBackupAgeMsdbWarn

If the last successful backup of the MSSQL MSDB Database is older than the defined number of days, but not older than MSSBackupAgeMsdbCrit days, the check status is set to Warning.

Reference Data

Configures ChecksMSS_DBBACKUP
Default Value7
UnitDays

MSSBackupExclude

Comma-separated list of database names that are ignored from the MSS_DBBACKUP check. By default, the check includes the master and msdb database as well. If you want to exclude databases, set the names of those databases in this monitoring parameter. Use a comma to separate multiple databases.

Reference Data

Configures ChecksNone
Default Value
UnitString

MSSDBExCrit

If the predicted point in time when the DB space limit is exceeded is within the upcoming defined number of hours, the check result of MSS_DBUSAGE is set to Critical.

Reference Data

Configures ChecksMSS_DBUSAGE
Default Value1
UnitHours

MSSDBExWarn

If the predicted point in time when the DB space limit is exceeded is within the upcoming defined number of hours, but not within the upcoming MSSDBExCrit hours, the check result of MSS_DBUSAGE is set to Warning.

Reference Data

Configures ChecksMSS_DBUSAGE
Default Value12
UnitHours

MSSDBForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksMSS_DBUSAGE
Default ValueActive
UnitEnum

MSSDBUsageCrit

If the usage of the database exceeds the defined threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksMSS_DBUSAGE
Default Value95 %
Unit% or KB/MB/GB

MSSDBUsageWarn

If the usage of the MSSQL database exceeds the defined threshold but does not exceed MSSDBUsageCrit threshold, the check status is set to Warning.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksMSS_DBUSAGE
Default Value80 %
Unit% or KB/MB/GB

MSSDBRemote

You can set this parameter if the monitoring Avantra Agent has no access to the filesystem holding the SQL Server installation, e.g. if you are using Agentless Monitoring.

In this case, the MSS_DBUSAGE and MSS_LOGUSAGE do not consider auto-growth database files.

Reference Data

Configures ChecksMSS_DBUSAGE, MSS_LOGUSAGE
Default Value0
UnitBoolean

MSSExpSQLExclude

SQL statements on this list are not considered for the check result. Wildcard * is allowed. Multiple entries must be separated by ; (semicolon). If your statement includes a semicolon character, please escape it with a backslash \.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value%_T*
UnitString

MSSExpSQLExcludeShow

Defines whether or not excluded statements, which will not contribute to the check result, are displayed.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value0
UnitBoolean

MSSExpSQLLogicalReadCrit

If for a particular SQL statement the amount of logical reads exceeds a defined percent of the total number of reads of all statements, the check turns to Critical.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value10
Unit%

MSSExpSQLLogicalReadWarn

If for a particular SQL statement the amount of logical reads exceeds a defined percent of the total number of reads of all statements, but does not exceed MSSExpSQLLogicalReadCrit, the check turns to Warning.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value5
Unit%

MSSExpSQLNumTopRecs

The number defined in this parameters limits the number of considered SQL statements to the top value. By default, the top 20000 SQL statements are shown. This is due to performance reasons.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value2000
UnitNumber

MSSExpSQLPhysicalReadCrit

If for a particular SQL statement the amount of physical reads exceeds a defined percent of the total number of reads of all statements, the check turns to Critical.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value10
Unit%

MSSExpSQLPhysicalReadWarn

If for a particular SQL statement the amount of physical reads exceed a defined percent of the total number of reads of all statements, but does not exceed MSSExpSQLPhysicalReadCrit, the check turns to Warning.

Reference Data

Configures ChecksMSS_EXPSQL
Default Value5
Unit%

MSSLogBckAgeCrit

If the transaction log for the MSSQL database is older than the defined number of minutes, the check status is set to Critical.

Reference Data

Configures ChecksMSS_LOGBACKUP
Default Value60
UnitMinutes

MSSLogBckAgeWarn

If the transaction log for the SAP SID database is older than the defined number of minutes, but is not older than MSSLogBckAgeCrit minutes, the check status is set to Warning.

Reference Data

Configures ChecksMSS_LOGBACKUP
Default Value30
UnitMinutes

MSSLogExCrit

If the predicted point in time when the transaction log limit is exceeded is within the upcoming defined number of hours, the check status is set to Critical.

Reference Data

Configures ChecksMSS_LOGUSAGE
Default Value1
UnitHours

MSSLogExWarn

If the predicted point in time when the transaction log limit is exceeded is within the upcoming defined number of hours, the check status is set to Warning, unless the MSSLogExCrit threshold is exceeded.

Reference Data

Configures ChecksMSS_LOGUSAGE
Default Value12
UnitHours

MSSLogForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksMSS_LOGUSAGE
Default ValueActive
UnitEnum

MSSLogUsageCrit

If the usage of the transaction log of the database exceeds the threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksMSS_LOGUSAGE
Default Value95 %
Unit% or KB/MB/GB

MSSLogUsageWarn

If the usage of the transaction log of the database exceeds the threshold, the check status is set to Warning, unless the MSSLogUsageCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksMSS_LOGUSAGE
Default Value80 %
Unit% or KB/MB/GB

MSSUseNTLMv2

A recent version of the Microsoft SQL server might force SQL connections to use NT LAN Manager Protocol Version 2 (NTLMv2) security. If you experience the error message The login is from an untrusted domain and cannot be used with Windows authentication in the DBCONNECT check, setting this parameter to true might fix this.

Reference Data

Configures ChecksNone
Default Value0
UnitBoolean

ORAAlertLogCountCrit

The check status will be Critical if that many log entries considered as critical are found.

Reference Data

Configures ChecksORA_ALERTLOG
Default Value1
UnitNumber

ORAAlertLogCountWarn

The check status will be Warning if that many log entries considered as Warning are found, unless the ORAAlertLogCountCrit threshold is exceeded.

Reference Data

Configures ChecksORA_ALERTLOG
Default Value1
UnitNumber

ORAAlertLogExprCrit

Designates an entry in the Oracle alert log as critical. Readers familiar with regular expressions may note that the expression below is a Perl style regular expression which is case insensitive.

Configures ChecksORA_ALERTLOG
Default Value

'%%msg%% =~ /ORA-0*(?:(255|257|270|272|376|447|470|471|472|473|474|600|603|1113|1114|1115|1122|1135|1578|1628|1629|1630|1631|1632|1650|1651|1652|1653|1654|1655|1656|1680|1681|1683|1684|1685|1688|1691|1692|1693|1694|3113|7445|16014|16038|19502|19504|19510|27044|27063|27072|30036)(?:\D|$))|Corrupt block/i and not Like('%%msg%%';'Patch Description:')

UnitExpression

ORAAlertLogExprWarn

Designates an entry in the Oracle alert log as warning.

Configures ChecksORA_ALERTLOG
Default Value

'%%msg%%' =~ /ORA-0*(?:(60|1149|1555|1562)(?:\D|$))|Checkpoint not complete/i and not Like('%%msg%%';'Patch Description:')

UnitExpression

ORAAlertLogLocation

Defines the location of the Oracle alert log file (full path, including the file name). The macro %%SID%% is provided and will be replaced with the Real SAP SID (for SAP Systems) or the database name (for Databases). The macro %%ORACLE_HOME%% may be used as well.

Reference Data

Configures ChecksNone
Default Value
UnitString

ORAAlertLogTimeSpan

Restricts the watch period of the ORA_ALERTLOG check.

Reference Data

Configures ChecksORA_ALERTLOG
Default Value60
UnitMinutes

ORABackupSkipFilesCheck

If the flag is set, the ORA_BACKUP does not verify if files marked as active in RMAN do actually exist on the filesystem.

Reference Data

Configures ChecksORA_BACKUP
Default Value0
UnitBoolean

ORABackupTool

This parameter tells Avantra which backup tool is used for the backup of the Oracle Database and thus controls which checks are executed.

If the parameter is set to RMAN the check ORA_BACKUP is executed which verifies backups performed with Oracle RMAN. If the parameter is set to BRBACKUP, the checks ORA_BRBACKUPSTAT, ORA_BRBACKUP, and ORA_BRARCHIVE will be executed.

Reference Data

Configures ChecksORA_BACKUP, ORA_BRBACKUPSTAT, ORA_BRBACKUP, ORA_BRARCHIVE
Default Value
UnitEnum

ORABrbackupDelayCrit

If the running time of an Oracle online backup is above the defined percent of the usual average runtime, the check status is set to Critical.

Reference Data

Configures ChecksORA_BRBACKUPSTAT
Default Value100
Unit%

ORABrbackupDelayTimeCrit

If the running time of an Oracle online backup is above ORABrbackupDelayCrit percent of the usual average runtime and above the defined number of minutes in this parameter, the check status is set to Critical.

Reference Data

Configures ChecksORA_BRBACKUPSTAT
Default Value30
UnitMinutes

ORABrbackupDelayTimeWarn

If the running time of an Oracle online backup is above ORABrbackupDelayWarn percent of the usual average runtime and above ORABrbackupDelayTimeWarn minutes, but below ORABrbackupDelayCrit percent or ORABrbackupDelayTimeCrit minutes, the check status is set to Warning.

Reference Data

Configures ChecksORA_BRBACKUPSTAT
Default Value15
UnitMinutes

ORABrbackupDelayWarn

If the running time of an Oracle online backup is above ORABrbackupDelayWarn percent of the usual average runtime, but below ORABrbackupDelayCrit percent, the check status is set to Warning.

Reference Data

Configures ChecksORA_BRBACKUPSTAT
Default Value50
Unit%

ORABrbackupOfflineDelayCrit

If the running time of an Oracle offline backup is above ORABrbackupOfflineDelayCrit percent of the usual average runtime, the check status of the DBCONNECT, RFCCONNECT or J2EECONNECT checks are set to Critical. For standalone Oracle Databases, the parameter is only effective if the BR*Tools are used.

Reference Data

Configures ChecksRFCCONNECT, DBCONNECT
Default Value50
Unit%

ORABrbackupSuccessFIDs

Defines the BRBACKUP function IDs considered as valid backup types when BRBACKUP is checked. The pre-configured ant aft means only full tape backups are considered as backups. If your Oracle database is backed up with backint (and thus the backup target is a file instead of a tape), you need to set the parameter to ant aft anf aff.

Reference Data

Configures ChecksORA_BRBACKUPSTAT, ORA_BRBACKUP
Default Valueant aft
UnitString

ORABrToolsSchema

This parameter defines the Oracle schema where the tables for BR*Tools are located. Usually, the Avantra Agent determines the schema, and only if this fails you need to define the schema manually.

Reference Data

Configures ChecksORA_BRBACKUPSTAT, ORA_BRBACKUP, ORA_BRARCHIVE
Default Value
UnitString

ORABrToolsSelectRange

Only the latest ORABrToolsSelectRange days are searched for successful BR*Tools operations.

Reference Data

Configures ChecksORA_BRBACKUPSTAT, ORA_DBCHECKLOG, ORA_BRBACKUP, ORA_BRARCHIVE
Default Value90
UnitDays

ORADataFileIncrementsCrit

Controls the number of auto-extent increments to be available in an Oracle datafile filesystem before a Critical alert is raised.

Reference Data

Configures ChecksORA_DATAFILES
Default Value0
UnitNumber

ORADataFileIncrementsWarn

Controls the number of auto-extent increments to be available in an Oracle datafile filesystem before a Warning alert is raised.

Reference Data

Configures ChecksORA_DATAFILES
Default Value2
UnitNumber

ORADataGuardDBCount

Defines the number of databases to be monitored by ORA_DATAGUARD check. To enable the check, set the ORADataGuardDBCount value to 1.

Reference Data

Configures ChecksORA_DATAGUARD
Default Value0
UnitNumber

ORADBAOperAgeCrit

If the last successful execution of any of the checked DBA operations is older than ORADBAOperAgeCrit days, the check status turns to Critical.

Reference Data

Configures ChecksORA_DBAOPER
Default Value14
UnitDays

ORADBAOperAgeWarn

If the last successful execution of any of the checked DBA operations is older than ORADBAOperAgeWarn days, but none is older than ORADBAOperAgeCrit or even unsuccessful, the check status turns to Warning.

Reference Data

Configures ChecksORA_DBAOPER
Default Value7
UnitDays

ORADBAOperFunctionIDs

Only the DBA operations corresponding to the function IDs defined with this parameter are considered by the ORA_DBAOPER check.

Reference Data

Configures ChecksORA_DBAOPER
Default Valuealy dbv opt
UnitString

ORADBAOperSelectRange

Only the latest ORADBAOperSelectRange days are searched for successful DBA operations.

Reference Data

Configures ChecksORA_DBAOPER
Default Value60
UnitDays

ORADBRemote

You may set this parameter if the monitoring Avantra Agent has no access to the filesystem holding the Oracle installation, e.g. if you are using Agentless Monitoring.

Reference Data

Configures ChecksRFCCONNECT, ORA_BACKUP, ORA_FSLOGARCH, ORA_DATAFILES, ORA_ALERTLOG
Default Value0
UnitBoolean

ORAEnqueueDeadLocksCrit

This parameter defines the minimum number of deadlocks that must have occurred in the last ORAEnqueueTimeSpan minutes to turn the ORA_Enqueue check Critical.

By setting this parameter to -1, the deadlocks check of ORA_Enqueue is disabled.

Reference Data

Configures ChecksORA_Enqueue
Default Value1
UnitNumber

ORAEnqueueDeadLocksWarn

his parameter defines the minimum number of deadlocks that must have occurred in the last ORAEnqueueTimeSpan minutes to turn the ORA_Enqueue check Warning.

If this parameter is set to a value equal to or higher than ORAEnqueueDeadLocksCrit, it has no effect.

Reference Data

Configures ChecksORA_Enqueue
Default Value1
UnitNumber

ORAEnqueueTimeoutsCrit

This parameter defines the minimum ratio of timeouts to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Critical.

By setting this parameter to 0, the timeouts check of ORA_Enqueue is disabled.

Reference Data

Configures ChecksORA_Enqueue
Default Value20
Unit%

ORAEnqueueTimeoutsWarn

This parameter defines the minimum ratio of timeouts to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Warning.

If this parameter is set to a value equal to or higher than ORAEnqueueTimeoutsCrit, it has no effect.

Reference Data

Configures ChecksORA_Enqueue
Default Value10
Unit%

ORAEnqueueTimeSpan

The ORA_Enqueue check collects enqueue statistics data up to a certain age. This parameter defines the age (in minutes) of the oldest data set to consider. If a data set gets older, it's removed from the collection.

Reference Data

Configures ChecksORA_Enqueue
Default Value30
UnitMinutes

ORAEnqueueWaitsCrit

This parameter defines the minimum ratio of wait events to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Critical.

By setting this parameter to 0, the wait events check part of ORA_Enqueue is disabled.

Reference Data

Configures ChecksORA_Enqueue
Default Value75
Unit%

ORAEnqueueWaitsWarn

This parameter defines the minimum ratio of wait events to requests/conversions of the last ORAEnqueueTimeSpan minutes necessary to turn the ORA_Enqueue check Warning.

If this parameter is set to a value equal to or higher than ORAEnqueueWaitsCrit, it has no effect.

Reference Data

Configures ChecksORA_Enqueue
Default Value50
Unit%

ORAExpSQLExclude

Statements issued from programs listed within this parameter are not considered for the check result. The list is separated by one or more blank spaces. Program names containing blank spaces must be enclosed in double quotes. You may use the special macro <NOPROG> to sort out statements that have no Program Name value.

Note that prior to SAP Basis Release 4.5C no program names are shown at all. In this case, the <NOPROG> macro excludes all statements.

Reference Data

Configures ChecksORA_EXPSQL
Default Value%_T*
UnitString

ORAExpSQLExcludeShow

Defines whether or not statements generated by excluded programs are shown in the check message.

Reference Data

Configures ChecksORA_EXPSQL
Default Value0
UnitBoolean

ORAExpSQLGetCrit

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLGetCrit percent of the total buffer gets, the check result turns to Critical.

Reference Data

Configures ChecksORA_EXPSQL
Default Value10
Unit%

ORAExpSQLGetWarn

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLGetWarn percent of the total buffer gets, and no statement exceeds an amount of ORAExpSQLGetCrit percent of the total buffer gets or ORAExpSQLReadCrit percent of the total disk reads, the check turns to Warning.

Reference Data

Configures ChecksORA_EXPSQL
Default Value5
Unit%

ORAExpSQLReadCrit

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLReadCrit percent of the total disk reads, the check result turns to Critical.

Reference Data

Configures ChecksORA_EXPSQL
Default Value10
Unit%

ORAExpSQLReadWarn

If any SQL statement (not excluded by ORAExpSQLExclude) exceeds an amount of ORAExpSQLReadWarn percent of the total disk reads, and no statement exceeds an amount of ORAExpSQLGetCrit percent of the total buffer gets or ORAExpSQLReadCrit percent of the total disk reads, the check turns to Warning.

Reference Data

Configures ChecksORA_EXPSQL
Default Value5
Unit%

ORAExtentsUsageCrit

If the number of extents allocated for an Oracle segment exceeds ORAExtentsUsageCrit percent of max_extents defined for this segment, the check status is set to Critical.

Reference Data

Configures ChecksORA_SEGMENTS
Default Value95
Unit%

ORAExtentsUsageWarn

If the number of extents allocated for an Oracle segment exceeds a percentage of max_extents defined for this segment, but does not exceed ORAExtentsUsageCrit percent, the check status is set to Warning.

Reference Data

Configures ChecksORA_SEGMENTS
Default Value90
Unit%

ORAFSLogArchCrit

If the log arch filesystem usage exceeds the defined threshold, the check status is set to Critical. The log arch filesystem is discovered automatically by Avantra Agent.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksORA_FSLOGARCH
Default Value85 %
Unit% or KB/MB/GB

ORAFSLogArchWarn

If the log arch filesystem usage exceeds the ORAFSLogArchWarn threshold, but does not exceed the ORAFSLogArchCrit threshold, the check status is set to Warning, unless the ORAFSLogArchExCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksORA_FSLOGARCH
Default Value70 %
Unit% or KB/MB/GB

ORAFSLogArchExCrit

If the predicted point in time when the filesystem limit is exceeded is within the upcoming defined number of hours, the check result is set to Critical.

Reference Data

Configures ChecksORA_FSLOGARCH
Default Value1
UnitHours

ORAFSLogArchExWarn

If the predicted point in time when the filesystem limit is exceeded is within the upcoming defined number of hours, but not within the upcoming ORAFSLogArchExCrit hours, the check result is set to Warning, unless the ORAFSLogArchExCrit threshold is exceeded.

Reference Data

Configures ChecksORA_FSLOGARCH
Default Value12
UnitHours

ORAFSLogArchForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksORA_FSLOGARCH
Default ValueActive
UnitEnum

ORAFSLogArchLocation

The ORA_FSLOGARCH check tries to read the log archive destination location from the Oracle parameters. In cases where this doesn't work, this parameter allows you to force override / set the archive destination location. There can be multiple paths entered, separated by semicolons ( ';' ).

Reference Data

Configures ChecksORA_FSLOGARCH
Default Value
UnitString

ORAHomeDir

Usually, the Avantra Agent determines the Oracle Home directory automatically. In case it does not you may set this parameter accordingly.

Reference Data

Configures ChecksDBCONNECT, ORA_BACKUP, ORA_TABLESPACES, ORA_SEGMENTS, ORA_FSLOGARCH, ORA_LOG_MODE, ORA_DATAFILES, ORA_ALERTLOG, ORA_BRBACKUPSTAT, ORA_EXPSQL, ORA_DBAOPER, ORA_DBCHECKLOG, ORA_BRBACKUP, ORA_BRARCHIVE
Default Value
UnitString

ORARMANSelectRange

ORA_BACKUP will select RMAN data not older than defined in this parameter.

Reference Data

Configures ChecksORA_BACKUP
Default Value30
UnitDays

ORASAPToolsEnable

If the parameter is set, the checks ORA_DBAOPER and ORA_DBCHECKLOG will be executed.

This is the default for Database instances of an SAP System.

If you run SAPDBA or BRCONNECT with a standalone Database you may set this parameter as well.

Reference Data

Configures ChecksORA_DBAOPER, ORA_DBCHECKLOG
Default Value
UnitBoolean

ORASAPToolsSchema

This parameter defines the Oracle schema where the tables for SAPDBA or BRCONNECT are located. Usually, Avantra Agent determines the schema and only if this fails, you need to define the schema manually.

Reference Data

Configures ChecksORA_DBAOPER, ORA_DBCHECKLOG
Default Value
UnitString

ORASegsChkWaitTime

Defines the time interval between two ORA_SEGMENTS checks.

Reference Data

Configures ChecksORA_SEGMENTS
Default Value60
UnitMinutes

ORASessionsCountWait

Defines the count threshold for sessions that exceed ORASessionsTimeWaitWarn or ORASessionsTimeWaitCrit time thresholds. The threshold is compared to the number of Critical sessions for a Critical check result, or the number of Critical plus Warning sessions for a Warning check result.

Reference Data

Configures ChecksORA_Sessions
Default Value1
UnitNumber

ORASessionsIgnoreWaitClass

Configures the wait classes that shall be ignored by ORA_Sessions.

Reference Data

Configures ChecksORA_Sessions
Default ValueIdle Configuration Concurrency
UnitString

ORASessionsTimeWaitCrit

ORA_Sessions compares session wait times of matching sessions against this threshold to categorize them as Critical. All Critical sessions are counted and further compared against ORASessionsCountWait for the final check result.

Reference Data

Configures ChecksORA_Sessions
Default Value10
UnitMinutes

ORASessionsTimeWaitWarn

ORA_Sessions compares session wait times of matching sessions against this threshold to categorize them as Warning. All Warning sessions are counted and further compared against ORASessionsCountWait for the final check result.

Reference Data

Configures ChecksORA_Sessions
Default Value5
UnitMinutes

ORATableSpaceExCrit

If the predicted point in time when the tablespace limit is exceeded is within the upcoming defined number of hours, the check result of ORA_TABLESPACES is set to Critical.

Reference Data

Configures ChecksORA_TABLESPACES
Default Value1
UnitHours

ORATableSpaceExWarn

If the predicted point in time when the tablespace limit is exceeded is within the upcoming ORATableSpaceExWarn hours, but not within the upcoming defined number of hours, the check result of ORA_TABLESPACES is set to Warning, unless the ORATableSpaceUsageCrit threshold is exceeded for some tablespace.

Reference Data

Configures ChecksORA_TABLESPACES
Default Value12
UnitHours

ORATableSpaceForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksORA_TABLESPACES
Default ValueActive
UnitEnum

ORATableSpaceUsageCrit

If one of the databases tablespaces usage exceeds the defined threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksORA_TABLESPACES
Default Value98 %
Unit% or KB/MB/GB

ORATableSpaceUsageWarn

If one of the databases tablespaces usage exceeds the defined threshold, the check status is set to Warning, unless the ORATableSpaceExCrit threshold is exceeded for some tablespace.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksORA_TABLESPACES
Default Value95 %
Unit% or KB/MB/GB

ORATableSpaceUseSegments

When set to True, this monitoring parameter enables the use of segment-based usage data in SQL Statements.

Reference Data

Configures ChecksORA_TABLESPACES
Default Value0
UnitBoolean

ORATNSAdminDir

By default, Avantra uses TNS to connect the Oracle database of an SAP System. Thus the Avantra Agent will determine the TNS admin directory (where the file tnsnames.ora is located). If this process fails, e.g. since the Oracle home directory could not be determined, you may set ORATNSAdminDir manually to work around the issue.

Reference Data

Configures ChecksDBCONNECT
Default Value
UnitString

ORATNSAlias

By default, Avantra uses TNS to connect the Oracle Database instance of an SAP System with the TNS alias being equal to the Real SAP SID. If the TNS alias is different from the Real SAP SID, you need to set this parameter to the corresponding TNS alias.

Reference Data

Configures ChecksDBCONNECT
Default Value
UnitString

PerfDataCollection

Controls whether or not Performance Data Collection is turned on for Systems. If you do not want the Avantra Agent to collect performance data you may remove the flag.

Reference Data

Configures ChecksNone
Default Value1
UnitBoolean

PGSQLBloatIndexPctCrit

This monitoring parameter defines the critical threshold for the index bloat percentage in PostgreSQL Database. If an index exceeds the value of preset bloat percentage of the DB size, the check result is Critical.

Reference Data

Configures ChecksPGSQL_Bloat
Default Value25
UnitPercent

PGSQLBloatIndexPctWarn

This monitoring parameter defines if the index bloat percentage in PostgreSQL Database is higher than the predefined parameter value and not higher than the PGSQLBloatIndexPctCrit value. If the index bloat percentage is within these limits, then the check result is Warning.

Reference Data

Configures ChecksPGSQL_Bloat
Default Value2.5
UnitPercent

PGSQLBloatTablePctCrit

This monitoring parameter defines the threshold for the table bloat percentage in PostgreSQL Database. If a table exceeds the value of preset bloat percentage of the Database size, the check result is Critical.

Reference Data

Configures ChecksPGSQL_Bloat
Default Value90
UnitPercent

PGSQLBloatTablePctWarn

This monitoring parameter defines if the table bloat percentage in PostgreSQL Database is higher than the preset parameter value and not higher than the PGSQLBloatTablePctCrit parameter value. If the value of bloat percentage is within these limits, then the check result is Warning.

Reference Data

Configures ChecksPGSQL_Bloat
Default Value5
UnitPercent

PGSQLConnectionsUsedCrit

This monitoring parameter defines the threshold for the ratio of active user connections to the total number of connections in PostgreSQL Database. If this ratio exceeds the preset value, the check result is Critical.

Reference Data

Configures ChecksPGSQL_Connections
Default Value90
UnitPercent

PGSQLConnectionsUsedWarn

This monitoring parameter defines if the ratio of active user connections to the total number of connections in PostgreSQL Database exceeds the parameter value and not above the PGSQLConnectionsUsedCrit parameter value. If the percentage of active user connections is within these limits, then the check result is Warning.

Reference Data

Configures ChecksPGSQL_Connections
Default Value80
UnitPercent

PGSQLDeadlocksCrit

This monitoring parameter defines the critical threshold for the number of deadlocks detected per hour in PostgreSQL. If the number goes above this parameter value, the check result is Critical.

Reference Data

Configures ChecksPGSQL_Deadlocks
Default Value600
UnitNumber

PGSQLDeadlocksWarn

This monitoring parameter defines if the number of deadlocks detected per hour in PostgreSQL is higher than the parameter value (preset by customer) and not higher than the PGSQLDeadlocksCrit parameter value. If the number returned is within these limits, then the check result is Warning.

Reference Data

Configures ChecksPGSQL_Deadlocks
Default Value60
UnitNumber

PGSQLIdleInTransactionsCrit

This monitoring parameter defines the Critical threshold if the number of idle in transaction sessions in PostgreSQL Database reaches the defined threshold.

Reference Data

Configures ChecksPGSQL_LongTransactions
Default Value5
UnitNumber

PGSQLIdleInTransactionsWarn

This monitoring parameter defines the Warning threshold if the number of idle in transaction sessions in PostgreSQL Database reaches the defined threshold.

Reference Data

Configures ChecksPGSQL_LongTransactions
Default Value1
UnitNumber

PGSQLLongTransactionsCrit

This monitoring parameter defines the Critical threshold if the number of long-running sessions in PostgreSQL Database reaches the defined threshold.

Reference Data

Configures ChecksPGSQL_LongTransactions
Default Value10
UnitNumber

PGSQLLongTransactionsWarn

This monitoring parameter defines the Warning threshold if the number of long-running sessions in PostgreSQL Database reaches the defined threshold.

Reference Data

Configures ChecksPGSQL_LongTransactions
Default Value1
UnitNumber

PGSQLReplicationSlotLagCrit

This monitoring parameter defines the threshold for replication slot lag in PostgreSQL Database. If the lag goes above or equals this parameter value, the check result is Critical.

Reference Data

Configures ChecksPGSQL_ReplicationSlot
Default Value16
UnitNumber

PGSQLReplicationSlotLagWarn

This monitoring parameter defines the threshold for replication slot lag in PostgreSQL Database. If the lag goes above or equals this parameter value, the check result is Warning.

Reference Data

Configures ChecksPGSQL_ReplicationSlot
Default Value1
UnitNumber

PGSQLTempFileCrit

This monitoring parameter defines the threshold for the number of files in the temporary files storage in PostgreSQL Database. If this number exceeds the parameter value, the check result is Critical.

Reference Data

Configures ChecksPGSQL_TempFiles
Default Value600
UnitNumber

PGSQLTempFileWarn

This monitoring parameter defines the threshold for the number of files in the temporary files storage in PostgreSQL Database. If this number exceeds the parameter value, the check result is Warning.

Reference Data

Configures ChecksPGSQL_TempFiles
Default Value60
UnitNumber

PGSQLTransactionIdletime

This monitoring parameter defines the length of time that a transaction needs to run before it's considered as an idle in transaction.

Reference Data

Configures ChecksPGSQL_LongTransactions
Default Value300
UnitNumber

PGSQLTransactionRuntime

This monitoring parameter defines the length of time that a transaction needs to run for before it's considered a long-running transaction.

Reference Data

Configures ChecksPGSQL_LongTransactions
Default Value600
UnitNumber

PredictiveAnalyticsEngine

Use this monitoring parameter to configure the Predictive Analytics engine for the Database. By default the engine is configured as Balanced.

Available options are:

  • Use Off to turn off the Predictive Analytics engine.
  • Use Best Performance to configure the Predictive Analytics engine to run with best performance.
  • Use Balanced to configure the Predictive Analytics engine to run in a balanced way.
  • Use Highest Precision to configure the Predictive Analytics engine to run with highest precision.

Reference Data

Configures ChecksNone
Default ValueBalanced
UnitEnum

RelevantDailyCheckDetails

Defines a list of Daily Check details that are considered relevant for the Daily Check status, i.e. the status of which contributes to the overall status. By default the parameter is not defined, i.e. all Daily Check details contribute.

If you define an empty list no Daily Check detail will contribute. In this case, the status of the Daily Check will be Unknown always.

Reference Data

Configures ChecksNone
Default Value
UnitDCDList

RunDailyCheckOnWE

If set, Daily Checks will run on Saturday and Sunday as well.

Reference Data

Configures ChecksSYB_ErrorLog, FULLCHECK
Default Value0
UnitBoolean

RUNJSAllowDBWrite

This monitoring parameters can be set to 'Enabled' or 'Disabled' (default) value. It allows SQL queries defined within custom checks and workflows to change the data in the Database.

note

This monitoring parameter is only effective when the configuration setting Security.RUNJSAllowDBWrite is set to moniparam.

Reference Data

Configures ChecksNone
Default ValueDisabled
UnitEnum

SIQBackupSelectRange

SIQ_Backup looks back the defined number of days to find successful backups. The default value is 60 days, so usually, there is no need to change this parameter since backups must be made far more often.

Reference Data

Configures ChecksSIQ_Backup
Default Value60
UnitDays

SIQCatalogCacheUsageCrit

If the Catalog cache usage goes above this parameter value, the check result is Critical.

Reference Data

Configures ChecksSIQ_Cache
Default Value95
Unit%

SIQCatalogCacheUsageWarn

If the Catalog cache usage goes above this parameter value, the check result is Warning.

Reference Data

Configures ChecksSIQ_Cache
Default Value80
Unit%

SIQConnectionsNumCrit

If the number of free connections goes below this parameter value, the check result is Critical.

Reference Data

Configures ChecksSIQ_Connections
Default Value2
UnitNumber

SIQConnectionsNumWarn

If the number of free connections goes below this parameter value and not below SIQConnectionsNumCrit parameter value, the check result is Warning.

Reference Data

Configures ChecksSIQ_Connections
Default Value5
UnitNumber

SIQDataFilesUsageCrit

If the dbfile usage exceeds the defined threshold the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSIQ_DataFiles
Default Value95 %
Unit% or KB/MB/GB

SIQDataFilesUsageWarn

If the dbfile usage of a database exceeds the defined threshold the check status is set to Warning.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSIQ_DataFiles
Default Value80 %
Unit% or KB/MB/GB

SIQDataSpacesExCrit

If the predicted point in time when the dataspace is exceeded is within the upcoming defined number of hours, the check status of SIQ_DataSpaces is set to Critical.

Reference Data

Configures ChecksSIQ_DataSpaces
Default Value1
UnitHours

SIQDataSpacesExWarn

If the predicted point in time when the data space is exceeded is within the upcoming defined number of hours, but not within the upcoming SIQDataSpacesExCrit hours, the check status of SIQ_DataSpaces is set to Warning.

Reference Data

Configures ChecksSIQ_DataSpaces
Default Value12
UnitHours

SIQDataSpacesForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksSIQ_DataSpaces
Default ValueActive
UnitEnum

SIQDataSpacesUsageCrit

If the usage of a dataspace exceeds the threshold the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSIQ_DataSpaces
Default Value95 %
Unit% or KB/MB/GB

SIQDataSpacesUsageWarn

If the usage of a dataspace exceeds the threshold the check status is set to Warning, unless the SIQDataSpacesUsageCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSIQ_DataSpaces
Default Value80 %
Unit% or KB/MB/GB

SIQLongTransactionsWarn

Configures a warning threshold for the number of long-running transactions. If the number goes above or equals this parameter value, but does not reach the SIQOperationsWaitingCrit parameter, the check result is Warning.

Reference Data

Configures ChecksSIQ_LongTransactions
Default Value1
UnitNumber

SIQLongTransactionsCrit

Configures a critical threshold for the number of long-running transactions. If the number exceeds or equals this parameter value, the check result is Critical.

Reference Data

Configures ChecksSIQ_LongTransactions
Default Value5
UnitNumber

SIQMainCacheUsageCrit

If the Main cache usage goes below this parameter value, the check result is Critical. By default this parameter is disabled (-1%).

Reference Data

Configures ChecksSIQ_Cache
Default Value-1
Unit%

SIQMainCacheUsageWarn

If the Main cache usage is equal or less than the defined value the check result is Warning.

Reference Data

Configures ChecksSIQ_Cache
Default Value80
Unit%

SIQOperationsWaitingCrit

If the number of waiting operations goes above this parameter value, the check result is Critical.

Reference Data

Configures ChecksSIQ_OperationsWaiting
Default Value10
UnitNumber

SIQOperationsWaitingWarn

If the number of waiting operations goes above this parameter value and below the SIQOperationsWaitingCrit parameter value, the check result is Warning.

Reference Data

Configures ChecksSIQ_OperationsWaiting
Default Value5
UnitNumber

SIQTempCacheUsageCrit

If the Temp cache usage is equal or higher than this parameter value, the check result is Critical.

Reference Data

Configures ChecksSIQ_Cache
Default Value95
Unit%

SIQTempCacheUsageWarn

If the Temp cache usage is equal or higher than this parameter value and below SIQTempCacheUsageCrit, the check result is Warning.

Reference Data

Configures ChecksSIQ_Cache
Default Value90
Unit%

SIQThreadsWarn

If the number of free threads goes below this parameter value and not below the SIQThreadsCrit parameter value, the check result is Warning.

Reference Data

Configures ChecksSIQ_Threads
Default Value20
UnitNumber

SIQThreadsCrit

If the number of free threads goes below or equals this parameter value, the check result is Critical.

Reference Data

Configures ChecksSIQ_Threads
Default Value5
UnitNumber

SIQTransactionRuntime

Configures the time a transaction may run without being treated as long-running. If some transaction is running longer than the defined value.

Reference Data

Configures ChecksSIQ_LongTransactions
Default Value60
UnitMinutes

StartStopDependentWINService

This parameter is only applicable if your database runs on a Windows operating system as a Windows service. Avantra Automation can start and stop those Windows services but Avantra does not know if dependent Windows services should be started or stopped. If you want to start and stop those dependent Windows services as well, then activate it with this parameter.

Reference Data

Configures ChecksNone
Default Value
UnitBoolean

Syb_ConfigExclude

This monitoring parameter defined a comma separated list of all configuration parameters to be excluded from Syb_Config.

Reference Data

Configures ChecksSyb_Config
Default Value
UnitString

Syb_ConfigOsOverwrite

This monitoring parameter can define an operating system of the database host.

Reference Data

Configures ChecksSyb_Config
Default Value
UnitEnum

SYB_FullBackupAgeCrit

This monitoring parameter checks the database against dump_type DATABASE (full) and CUMULATIVE (incremental). The check status is set to Critical if the last successful full backup is older than the defined number of days. You can define overriding this value on a per-day level using the corresponding Monitoring Parameter Exception.

Reference Data

Configures ChecksSYB_BACKUP
Default Value7
UnitDays

SYB_FullBackupAgeWarn

This monitoring parameter checks the database against dump_type DATABASE (full) and CUMULATIVE (incremental). If the last successful backup is older than the defined number of days but not older than FullBackupAgeCrit days, the check status is set to Warning. You can define overriding this value on a per-day level using the corresponding Monitoring Parameter Exception.

Reference Data

Configures ChecksSYB_BACKUP
Default Value1
UnitDays

Syb_SaptoolsCreds

This monitoring parameter defines a credential type to use for database query. If left empty, the default monitoring credentials are used.

Reference Data

Configures ChecksSyb_Config
Default Value
UnitEnum

SYBBackupExclude

Comma-separated list of database names that are ignored from SYB_Backup. Spaces before or after the comma are gently ignored. Excluded databases will still appear in the SYB_Backup table display, but are marked as Excluded → Yes. Most databases that usually require no backup up are already excluded by default.

SAP's Database Administration guide for SAP Business Suite on SAP ASE notes that backups are optional for certain databases, so you may choose to add additional ones to the exclusion list as needed.

Reference Data

Configures ChecksSYB_Backup
Default Valuemodel; saptempdb; sybsecurity; sybsystemdb; sybsystemprocs; tempdb
UnitString

SYBBackupOKDisplayMax

Defines how many successful backups will be displayed in the table of SYB_Backup. This history is just for your convenience. You may reduce this parameter to 1 if you want to see only the latest successful backup.

Reference Data

Configures ChecksSYB_Backup
Default Value5
UnitNumber

SYBBackupSelectRange

SYB_Backup looks for the defined number of days back to find successful backups. The default value is 60 days, so usually, there is no need to change this parameter since backups must be made far more often.

Reference Data

Configures ChecksSYB_Backup
Default Value60
UnitDays

SYBBackupStatDelayTimeCrit

If the running time of a Sybase backup is above 100 percent of the usual average runtime and above the defined number of minutes, the check status is set to Critical.

Reference Data

Configures ChecksSYB_BackupStat
Default Value30
UnitMinutes

SYBBackupStatDelayTimeWarn

If the running time of a Sybase backup is above 50 percent of the usual average runtime and above the defined number of minutes, the check status is set to Warning, unless the value is higher than the SYBBackupStatDelayTimeCrit threshold.

Reference Data

Configures ChecksSYB_BackupStat
Default Value15
UnitMinutes

SYBBackupStatExclude

Comma-separated list of database names that are ignored from SYB_BackupStat. Spaces before or after the comma are gently ignored. Excluded databases will still appear in the SYB_BackupStat table display, but are marked as Excluded → Yes. Most databases that usually require no backup up are already excluded by default.

SAP's Database Administration guide for SAP Business Suite on SAP ASE notes that backups are optional for certain databases, so you may choose to add additional ones to the exclusion list as needed.

Reference Data

Configures ChecksSYB_BackupStat
Default Valuemodel; saptempdb; sybsecurity; sybsystemdb; sybsystemprocs; tempdb
UnitString

SYBBackupStatFailedDisplayTime

Defines the time how long a failed backup is displayed (status is defined by SYBBackupStatFailedStatus).

The check status will reset to OK after the defined number of minutes, in this monitoring parameter, has passed since the failed backup was detected.

Reference Data

Configures ChecksSYB_BackupStat
Default Value60
UnitMinutes

SYBBackupStatFailedStatus

Defines whether a failed backup reported by SYB_BackupStat shall be reported as Warning or Critical status.

Reference Data

Configures ChecksSYB_BackupStat
Default ValueWarning
UnitEnum

SYBDBExCrit

If the predicted point in time when the data space is exceeded is within the upcoming defined number of hours, the check status is set to Critical.

Reference Data

Configures ChecksSYB_DataSpaces
Default Value1
UnitHours

SYBDBExWarn

If the predicted point in time when the data space is exceeded is within the upcoming defined number of hours, but not within the upcoming SYBDBExCrit hours, the check status is set to Warning.

Reference Data

Configures ChecksSYB_DataSpaces
Default Value12
UnitHours

SYBDBForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksSYB_DataSpaces
Default ValueActive
UnitEnum

SYBDBUsageCrit

If the data space usage of a database exceeds the defined threshold the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSYB_DataSpaces
Default Value95 %
Unit% or KB/MB/GB

SYBDBUsageWarn

If the data space usage of a database exceeds the defined threshold, the check status is set to Warning, unless the SYBDBUsageCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSYB_DataSpaces
Default Value80 %
Unit% or KB/MB/GB

SYBErrorLogExcludeErrNums

You may use this parameter to exclude certain error numbers from being evaluated in SYB_ErrorLog and SYB_ErrorLogStat. Multiple numbers are defined in a comma-separated list. Leading and trailing blank spaces before or after the comma character are gently ignored.

Reference Data

Configures ChecksSYB_ErrorLog, SYB_ErrorLogStat
Default Value
UnitString

SYBErrorLogTimeSpan

SYB_ErrorLogStat is designed to recover from check status Warning or Critical, so the check looks back for a time span defined by this monitoring parameter only.

Reference Data

Configures ChecksSYB_ErrorLogStat
Default Value60
UnitMinutes

SYBLogBackupAgeCrit

If the last transaction log dump is above the defined number of minutes ago, the check result is Critical.

Reference Data

Configures ChecksSYB_LogBackup
Default Value120
UnitMinutes

SYBLogBackupAgeWarn

If the last transaction log dump is above the defined number of minutes ago, but below SYBLogBackupAgeCrit minutes, the check status is Warning.

Reference Data

Configures ChecksSYB_LogBackup
Default Value60
UnitMinutes

SYBLogBackupExclude

You may use this parameter to exclude databases from being checked by SYB_LogBackup. The names of the databases are defined in a comma-separated list. Leading and trailing blank spaces before or after the comma character are gently ignored.

By default, many system databases are already excluded by default. However, databases are still checked for the full transaction log, no matter if excluded or not.

Reference Data

Configures ChecksSYB_LogBackup
Default Valuemaster; model; saptempdb; saptools; sybmgmtdb; sybsecurity; sybsystemdb; sybsystemprocs; tempdb
UnitString

SYBLogExCrit

If the predicted point in time when the log space is exceeded is within the upcoming defined number of hours, the check status is set to Critical.

Reference Data

Configures ChecksSYB_LogSpaces
Default Value1
UnitHours

SYBLogExWarn

If the predicted point in time when the log space is exceeded is within the upcoming defined number of hours, but not within the upcoming SYBLogExCrit hours, the check status is set to Warning.

Reference Data

Configures ChecksSYB_LogSpaces
Default Value12
UnitHours

SYBLogForecast

Defines whether the forecasting algorithm is active or inactive. See Forecasting for more information.

Reference Data

Configures ChecksSYB_LogSpaces
Default ValueActive
UnitEnum

SYBLogUsageCrit

If the data space usage of a database exceeds the defined threshold, the check status is set to Critical.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSYB_LogSpaces
Default Value95 %
Unit% or KB/MB/GB

SYBLogUsageWarn

If the data space usage of a database exceeds the defined threshold the check status is set to Warning, unless the SYBLogUsageCrit threshold is exceeded.

You can define the threshold either in percentage of the total size of the resource, or in KB, MB, or GB values of the remaining free space. In the first case, the parameter gets effective if the usage measured in % of the total space is higher than the defined threshold. In the second case the parameter gets effective if the remaining free space is lower than the defined threshold.

Reference Data

Configures ChecksSYB_LogSpaces
Default Value80 %
Unit% or KB/MB/GB

TimeOutDBMonitor

Defines the timeout for Avantra Agent child processes performing Database checks (in seconds). If the value exceeds, the process is terminated.

Reference Data

Configures ChecksDBCONNECT, ORA_BACKUP
Default Value180
UnitSeconds