Skip to main content

# SAP Instance - Monitoring Parameters

Here you will find detailed information about monitoring parameters for SAP Instance 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.

## 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 SAP Instances, `INSTPROFPARAM`, `J2EESYSPROP`, and `J2EEVMPARAM` are currently supported. Wildcard `*` is supported to define multiple parameters.

Example: Ignored Changes `J2EEVMPARAM: java.proc.id, java.mem*; J2EESYSPROP: *`

### Reference Data​

Configures | System Change Auto Detection
Default Value |
Unit | String

## CS_CacheServerScript​

This monitoring parameter is used to set the Cache Server Script Name. It's used to build HTTP called to the Cache Server.

### Reference Data​

Configures Checks | CS_Status
Default Value | sapcsc
Unit | String

## CS_ContentServerScript​

This monitoring parameter is used to set the Content Server Script Name. It is used to build HTTP called to the Content Server.

### Reference Data​

Configures Checks | CS_Status
Default Value | sapcs
Unit | String

## CS_MonitorRepos​

This monitoring parameter is used to build a comma-separated list of all repositories that are monitored in the CS_Status check. If this is left empty, all repositories are monitored.

### Reference Data​

Configures Checks | CS_Status
Default Value |
Unit | String

## CS_Protocol​

This monitoring parameter is used to set either a HTTP or HTTPS protocol for calls to the Content Server. The default value is `auto`, which is HTTPS preferred.

### Reference Data​

Configures Checks | CS_Status
Default Value | auto
Unit | Enum

## DispatcherQueueFillRatioCrit​

If the current number of entries in one of the dispatcher queues exceeds DispatcherQueueFillRatioCrit times the number of available work processes, the DispatcherQueue Check turns toCritical.

### Reference Data​

Configures Checks | DispatcherQueue
Default Value | 10
Unit | Number

## DispatcherQueueFillRatioWarn​

If the current number of entries in one of the dispatcher queues exceeds DispatcherQueueFillRatioWarn times the number of available work processes, the DispatcherQueue Check turns to Warning (unless one of the critical thresholds is exceeded).

### Reference Data​

Configures Checks | DispatcherQueue
Default Value | 5
Unit | Number

## DispatcherQueuePercentCrit​

If the current number of entries in one of the dispatcher queues compared to the maximum number of queue entries exceeds this threshold, the DispatcherQueue Check turns to Critical.

### Reference Data​

Configures Checks | DispatcherQueue
Default Value | 40
Unit | %

## DispatcherQueuePercentWarn​

If the current number of entries in one of the dispatcher queues compared to the maximum number of queue entries exceeds this threshold, the DispatcherQueue Check turns to Warning (unless one of the critical thresholds is exceeded).

### Reference Data​

Configures Checks | DispatcherQueue
Default Value | 20
Unit | %

## ERSConnectErrsCrit​

Starting from ERSConnectErrsCrit failed connection attempts the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | ERS_Connect
Default Value | 1
Unit | Number

## ICMConnUsageCrit​

If the ratio of current connections to the maximum available connections exceeds ICMConnUsageCrit percent, the check-status turns to Critical.

### Reference Data​

Configures Checks | ICMSTAT
Default Value | 95
Unit | %

## ICMConnUsageWarn​

If the ratio of current connections to the maximum available connections exceeds ICMConnUsageWarn percent, but not ICMConnUsageCrit percent, and none of the thresholds ICMQueueUsageCrit or ICMThreadsUsageCrit is exceeded, the check status turns to Warning.

### Reference Data​

Configures Checks | ICMSTAT
Default Value | 85
Unit | %

## ICMQueueUsageCrit​

If the ratio of current queues to maximum available queues exceeds ICMQueueUsageCrit percent, the check status turns to Critical.

### Reference Data​

Configures Checks | ICMSTAT
Default Value | 95
Unit | %

## ICMQueueUsageWarn​

If the ratio of current queues to maximum available queues exceeds ICMQueueUsageWarn percent, but not ICMQueueUsageCrit percent, and none of the thresholds ICMConnUsageCrit or ICMThreadsUsageCrit is exceeded, the check status turns to Warning.

### Reference Data​

Configures Checks | ICMSTAT
Default Value | 85
Unit | %

## ICMThreadsUsageCrit​

If the ratio of current created worker threads to maximum available worker threads exceeds ICMThreadsUsageCrit percent, the check status turns to Critical.

### Reference Data​

Configures Checks | ICMSTAT
Default Value | 95
Unit | %

## ICMThreadsUsageWarn​

If the ratio of current created worker threads to maximum available worker threads exceeds ICMThreadsUsageWarn percent, but not ICMThreadsUsageCrit percent, and none of the thresholds ICMConnUsageCrit or ICMQueueUsageCrit is exceeded, the check status turns to Warning.

### Reference Data​

Configures Checks | ICMSTAT
Default Value | 85
Unit | %

## IgnoreJavaAddIn​

In case the SAP instance auto-discovery finds a double-stack instance but the Java part is not used intentionally, you can use this parameter to prevent the Java add-in from being monitored.

### Reference Data​

Configures Checks | None
Default Value | 0
Unit | Boolean

## IgnoreWebDisp​

To suppress monitoring of the integrated Web Dispatcher on an Abap_Scs with Web Dispatcher instance, you may set this parameter to true. The Abap_Scs with Web Dispatcher instance will then be regarded as an ordinary Abap_Scs instance, and all checks and performance values related to Web Dispatcher monitoring won't be available.

### Reference Data​

Configures Checks | None
Default Value | 0
Unit | Boolean

## InstanceDowntimeCrit​

If the downtime of a properly shut down SAP instance exceeds InstanceDowntimeCrit minutes, the RFCCONNECT, J2EECONNECT, or SCS_MSGSRV check status turns from Warning to Critical.

### Reference Data​

Configures Checks | RFCCONNECT, J2EECONNECT, SCS_MSGSRV, ASCS_MSGSRV
Default Value | 120
Unit | Minutes

## J2EEApplThreadsPoolUsageCrit​

If the number of used application threads exceeds J2EEApplThreadsPoolUsageCrit percent of the maximum thread pool size, the check status is set to Critical.

### Reference Data​

Configures Checks | J2EEApplThreadsPool
Default Value | 90
Unit | %

## J2EEApplThreadsPoolUsageWarn​

If the number of used application threads exceeds this value but does not exceed J2EEApplThreadsPoolUsageWarn percent of the maximum thread pool size, the check status is set to Warning.

### Reference Data​

Configures Checks | J2EEApplThreadsPool
Default Value | 80
Unit | %

## J2EEConnectErrsCrit​

Starting from J2EEConnectErrsCrit consecutive failed connection attempts, the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | J2EECONNECT
Default Value | 1
Unit | Number

## J2EEConnectHttpErrsCrit​

Starting from J2EEConnectHttpErrsCrit consecutive failed HTTP connection attempts on the system info page, the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value | 1
Unit | Number

## J2EEConnectHttpPageKeywords​

The parameter can be used to configure custom keywords, which serve to verify the validity of the `/nwa/sysinfo` page, which is retrieved by the J2EEConnectHttp check. If one of the keywords is found on the page, the page is considered to be valid and the J2EEConnectHttp check is OK.

By default, the check J2EEConnectHttpPageKeywords looks for the instance host name on the page. For customized pages, which do not contain the instance host name, this turns the check to Critical.

If you specify a `*`, the page verification is omitted, and a successful login to any page is accepted.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## J2EEConnectUrlQuery​

This monitoring parameter is used to define the query string that is appended to the URLs that J2EEConnectHttp uses. The query string is appended before the suffixes that are added by J2EEConnectUrlSuffix.

The default value `saml2=disabled` disables SAML2 for the logon.

### Reference Data​

Configures Checks | None
Default Value | saml2=disabled
Unit | String

## J2EEConnectUrlSuffix​

Defines the URL to be used by the J2EEConnectHttp Check.

The following syntax is supported:

- Suffix only, e.g. `/sap/monitoring/SystemInfo`. The Suffix is appended to the default URL (`http://localhost:5<sysno>00`) by the Avantra-agent internally.
  For SAP systems 7.10 and newer, the default path is `/nwa/sysinfo`.
  For SAP systems 7.0x and older, the default path is `/sap/monitoring/SystemInfo`.

- Suffix with leading port, e.g. `:8080/sap/monitoring/SystemInfo`. (The leading colon is mandatory!). You will have to use this syntax if the HTTP port has been changed from its default value `5<system_number>00`.

- Whole URL starting with `http://`. You can freely define which URL to be checked. This mode may be used for special purposes.

- Whole URL starting with `https://`. You can use this option if you want to access an HTTPS service. You also have to use this option if the default SystemInfo page is accessed via HTTPS.

In the `HTTP/HTTPS` options, placeholders for hosts and ports can be used. Specify `<host>` to let the Avantra Agent use the default host (usually 'localhost') and/or `<port>` to let it use the default port of the specified protocol (`5<sysno>00` for http and `5<sysno>01` for HTTPS).

Example: J2EEConnectUrlSuffix

    https://<host>:<port>/sap/monitoring/SystemInfo
    http://192.168.123.456:<port>/myhtmlpage

You can also use client authentication in conjunction with HTTPS. See the description of J2EEKeystoreName for further information.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value | sap/monitoring/SystemInfo
Unit | String

## J2EEKeyPw​

This password is used to retrieve the keys from the keystore specified in the J2EEKeystoreName monitoring parameter.

Do not define this parameter unless the keystore keys are password protected.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## J2EEKeystoreName​

If you use the J2EECONNECT check with `HTTPS`, you might also want to use certificates to authenticate the server and client. Whereas server certificates are handled without further configuration (the Avantra-agent trusts all incoming certificates by default), client certificates must be configured and installed manually.

In order to enable client authentication in the J2EECONNECT check, a java keystore file containing the accurate certificate must have been generated, stored in a location readable by the Avantra-agent, and defined in this parameter. (If you do not define this parameter, no client authentication will be performed.)

The path of the keystore file can be specified as follows:

- Fully qualified path, e.g.. `/usr/keys/keystore.ks`
- Relative path. A relative path is applied to the Agent's cfg directory, e.g. `keystore.ks` (will resolve to `<syslinkinstall_dir>/lyceus/cfg/keystore.ks`.)

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## J2EEKeystorePw​

Password for an optional integrity check of the keystore. If you specify this parameter, the used keystore is checked for integrity, otherwise, the keystore is loaded without an integrity check. For this to work, the keystore must have been stored using the same integrity password before.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## J2EEKeystoreType​

Indicates the type of the keystore specified in J2EEKeystoreName. The keystore type must exactly correspond to the type of the used java keystore. If a keystore is specified but not a keystore type, `pkcs12` is used as the default keystore type.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## J2EEP4Port​

The Avantra-agent connects the Java instance at the P4 port, as SAP Visual Administrator does. If this TCP/IP port has been changed from its default value, you need to adapt J2EEP4Port to the correct value.

### Reference Data​

Configures Checks | None
Default Value | `5<sysnr>04`
Unit | String

## J2EEP4TransportType​

The Avantra-agent connects the Java instance at the P4 port defined by J2EEP4Port. The J2EEP4TransportType monitoring parameter defines the transport layer (or protocol) used for this connection. By default, the value is `None` and the `P4` protocol is used.

You can choose `SSL` in order to use the `P4S` protocol scheme in case of which the Avantra-agent uses Transport Layer Security (TLS) for the connection.

You can choose `HTTPS` to use the `P4HTTPS` protocol scheme. The Avantra-agent then tunnels the connection through HTTPS.

### Reference Data​

Configures Checks | None
Default Value | None
Unit | Enum

## J2EESystemThreadsPoolUsageCrit​

If the number of used system threads exceeds J2EESystemThreadsPoolUsageCrit percent of the maximum thread pool size, the check status is set to Critical.

### Reference Data​

Configures Checks | J2EESystemThreadsPool
Default Value | 90
Unit | %

## J2EESystemThreadsPoolUsageWarn​

If the number of used system threads exceeds this value but does not exceed J2EESystemThreadsPoolUsageWarn percent of the maximum thread pool size, the check status is set to Warning.

### Reference Data​

Configures Checks | J2EESystemThreadsPool
Default Value | 80
Unit | %

## JavaASAvgRespTimeConsiderBest​

Defines the percentage of the best-performing server processes used to calculate the overall server response time. The remaining will not be considered.

### Reference Data​

Configures Checks | JavaASAvgRespTime
Default Value | 100
Unit | Percent (%)

## JavaASAvgRespTimeCrit​

If the `JARM` average response time exceeds this value, the check status is set to Critical.

### Reference Data​

Configures Checks | JavaASAvgRespTime
Default Value | 3000
Unit | Milliseconds

## JavaASAvgRespTimeReset​

Defines if or if not the JavaASAvgRespTime check resets the `JARM` statistic records. By default, it does. There is no need to change this value unless you use other tools that also try to reset the `JARM` statistic records.

### Reference Data​

Configures Checks | JavaASAvgRespTime
Default Value | 1
Unit | Boolean

## JavaASAvgRespTimeWarn​

If `JARM` average response time exceeds this value but does not exceed JavaASAvgRespTimeCrit, the check status is set to Warning.

### Reference Data​

Configures Checks | JavaASAvgRespTime
Default Value | 1500
Unit | Milliseconds

## JavaASRespTimeAvgCycles​

This parameter configures JavaASAvgRespTime by defining the minimum number of check cycles needed for the check to calculate the average response time to compare against JavaASAvgRespTimeWarn and JavaASAvgRespTimeCrit.

### Reference Data​

Configures Checks | JavaASAvgRespTime
Default Value | 2
Unit | Number

## JavaHttpPort​

The Avantra Agent tries to determine the HTTP port of a Java SAP Instance automatically from the instance profile entries `ICM/SERVER_PORT_nn` with protocol HTTP (for pre 7.10 instances `ICM/HTTP/J2EE_nn`); by default `5<sysno>00` is used.

If an HTTPS port is detected in the profile as well, the HTTPS port will be preferred to the HTTP port, and the connection will be established using SSL and the HTTPS port. To overrule this behavior, you may set JavaHttpPort, which in turn overrides HTTPS and forces the usage of HTTP on the specified port.

If detection fails and the default port is wrong, JavaHttpPort may be used to force-set the HTTP port.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## JavaHttpsPort​

The Avantra Agent tries to determine the HTTPS port of a Java SAP Instance automatically from the instance profile entries `ICM/SERVER_PORT_nn` with protocol HTTPS (for pre 7.10 instances `ICM/HTTPS/J2EE_nn`);. If no HTTPS port is detected, HTTPS won't be used by default.

If both HTTP and HTTPS ports are detected in the profile, the HTTPS port will be preferred over the HTTP port, and the connection will be established using SSL and the HTTPS port. See the description of JavaHttpPort for further details.

If detection fails for an HTTPS port, JavaHttpsPort may be used to force-set the HTTPS port, overruling any JavaHttpPort setting.

### Reference Data​

Configures Checks | J2EEConnectHttp
Default Value |
Unit | String

## JavaLongRunningThreadsCountCrit​

If the long-running threads count of any cluster node of an AS Java is equal to or above this setting, the check status of JavaLongRunningThreads will be Critical, otherwise, Warning if higher than 0.

### Reference Data​

Configures Checks | JavaLongRunningThreads
Default Value | 1
Unit | Number

## JavaLongRunningThreadsCountWarn​

If the long-running threads count of any cluster node of an AS Java is higher than zero, the JavaLongRunningThreads check status will be Warning.

### Reference Data​

Configures Checks | JavaLongRunningThreads
Default Value | 1
Unit | Number

## JavaServerNodesRunningPctCrit​

If the percentage of running server nodes of an SAP J2EE instance compared to all nodes is equal to or below this value, the check status will be Critical.

note

The "Disabled" nodes are not considered in the calculation.

### Reference Data​

Configures Checks | JavaServerNodes
Default Value | 50
Unit | %

## JavaServerNodesRunningPctWarn​

If the percentage of running server nodes of an SAP J2EE instance compared to all nodes is equal to or below this value but still above JavaServerNodesRunningPctCrit, the check status will be Warning.

note

The "Disabled" nodes are not considered in the calculation.

### Reference Data​

Configures Checks | JavaServerNodes
Default Value | 80
Unit | %

## JavaStackMonitor​

When sapcontrol is available and configured for a system / instance in the avantra-ui (see ), it's possible to monitor the Java by means of sapcontrol instead of the traditional `JMX/P4` monitor.

The `SAPControl` setting might be useful if the `JMX/P4` monitor doesn't work reliably or is not accessible for some reason.

### Reference Data​

Configures Checks | None
Default Value | JMX/P4
Unit | Enum

## JVMGCRatioCrit​

Configures critical threshold for JVMGarbageCollector check. If the time spent on garbage collection is equal to or above JVMGCRatioCrit percent of the JVM total runtime, the check status will be Critical.

### Reference Data​

Configures Checks | JVMGarbageCollector
Default Value | 40
Unit | %

## JVMGCRatioWarn​

Configures warning threshold for JVMGarbageCollector check. If the time spent on garbage collection is equal to or above JVMGCRatioWarn percent of the JVM total runtime, but still below JVMGCRatioCrit, the status of the GC ratio sub-check will Critical.

### Reference Data​

Configures Checks | JVMGarbageCollector
Default Value | 20
Unit | %

## JVMMemoryUsageCrit​

Configures critical threshold for Java virtual memory usage. If the amount of the Java virtual memory used exceeds JVMMemoryUsageCrit percent of the available memory, the check-status is set to Critical.

### Reference Data​

Configures Checks | JVM_MEMORY
Default Value | 90
Unit | %

## JVMMemoryUsageWarn​

Configures warning threshold for Java virtual memory usage. If the amount of the Java virtual memory used exceeds this value but does not exceed JVMMemoryUsageCrit percent of the available memory, the check status is set to Critical.

### Reference Data​

Configures Checks | JVM_MEMORY
Default Value | 80
Unit | %

## LyjconCmdLineParams​

Special purpose parameter to control the Avantra Agent.

warning

Do not use unless instructed by the Avantra Support Team.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## LyjconLibPath​

Special purpose parameter for setting the relative Jar search path of Avantra Agent.

warning

Do not use unless instructed by the Avantra Support Team.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## LyjconLibs​

Special purpose parameter for setting the Jars loaded by Avantra Agent.

warning

Do not use unless instructed by the Avantra Support Team.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## RdispMsservInternal​

The MessageServer daily check checks the parameter `rdisp/msserv_internal` according to SAP recommendations and standard configurations. If this parameter has a different value and you know that your systems are running safely with your value, you can override the default behavior of the MessageServer daily check with this monitoring parameter.

Set the port of your `rdisp/msserv_internal` parameter value. For most systems, typical values are `39xx`. You can also use regular expressions, use `39\d\d` to allow all ports from 3900 to 3999. For S/4HANA and BW/4HANA systems, the port value is `9311`.

### Reference Data​

Configures Checks | MessageServer
Unit | String

## OSCollectorMaxAge​

warning

This is a deprecated parameter. Do not use.

### Reference Data​

Configures Checks | None
Default Value | 15
Unit | Minutes

## PerfDataCollectABAPTaskTypes​

Per default, Avantra-agent collects performance data for ABAP task types DIALOG and additionally for the task types listed in this parameter. Task type DIALOG is always recorded so it's not required to specify it using PerfDataCollectABAPTaskTypes. Per default, performance is also collected for background jobs and HTTP requests.

You can list possible task types using SAP transaction Workload (`ST03`). For example, possible values are `AUTOABAP, AUTOCCMS, AUTOJAVA, AUTOTH, BACKGROUND, BUFFER SYNC, DDLOG CLEANUP, DEL. THCALL, DIALOG, HTTP, RFC, RPCTH, SPOOL, UPDATE, UPDATE2`.

### Reference Data​

Configures Checks | None
Default Value | BACKGROUND; HTTP
Unit | String

## 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 Checks | None
Default Value | 1
Unit | Boolean

## PredictiveAnalyticsEngine​

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

- 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 Checks | None
Default Value | Balanced
Unit | Enum

## 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 Checks | None
Default Value |
Unit | DCDList

## RemoveFromDBDelay​

If an SAP Instance is no longer discovered by any Avantra Agent, it will be marked in Avantra as `NOT_SEEN`. (In this state, it can only be removed from the system manually using Avantra WebUI.)

If it's discovered again by any Avantra Agent within the RemoveFromDBDelay days period, the `NOT_SEEN` flag is simply removed.

If the SAP Instance is not discovered by any Avantra Agent for RemoveFromDBDelay days, it will be removed from the Avantra Database.

### Reference Data​

Configures Checks | None
Default Value | 7
Unit | Days

## RFCConnectErrsCrit​

Starting from RFCConnectErrsCrit failed RFC connection attempts, the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | RFCCONNECT
Default Value | 1
Unit | Number

## SAPControlProtocol​

This parameter allows you to configure the protocol to access the SAPControl Web Service Interface of an SAP instance.

If you specify `OFF`, SAPControl won't be used for the instance.

If you specify `Adaptive`, the SAPControl connector will use Windows Named Pipes / Unix Domain Sockets to connect to the SAPControl Web Service, unless the optional SAPControl User is defined for the SAP System, see Adding a SAP System. If the SAPControl User is defined, `HTTP/HTTPS` will be used automatically.

If you specify `NamedPipes`, the SAPControl connector will use Windows Named Pipes / Unix Domain Sockets to connect to the SAPControl Web Service of the underlying instance, regardless of its type. Make sure the Agent OS user has sufficient permissions to access the Named Pipe / Domain Socket.

If you specify `HTTP`, the SAPControl connector will use HTTP to connect to the SAPControl Web Service of the underlying instance, regardless of its type. The HTTP port defaults to `5<sysno>13`, unless the services file (i.e. `/etc/services` on Unix, `C:\Windows\System32\drivers\etc\services` on Windows) contains an entry `sapctrl<sysno>` (HTTP) defining a different port. When you specify this option, you have to define a SAPControl User in the corresponding SAP System properties; see Defining the SAPControl User.

If you specify `HTTPS`, the SAPControl connector will use HTTPS to connect to the SAPControl Web Service of the underlying instance, regardless of its type. The HTTPS port defaults to `5<sysno>14`, unless the services file (i.e. `/etc/services` on Unix, `C:\Windows\System32\drivers\etc\services` on Windows) contains an entry `sapctrls<sysno>` (HTTPS) defining a different port. When you specify this option, you have to define a SAPControl User in the corresponding SAP System properties; see Defining the SAPControl User.

### Reference Data​

Configures Checks | WD_Connect, ERS_Connect
Default Value | Adaptive
Unit | Enum

## SAPHost​

If host name detection fails, then the SAP host with the defined value is used.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## SAPPSECertCrit​

If any of the 5 valid-to dates PSE files is within the specified threshold set by monitoring parameter SAPPSECertCrit, the check status is set to Critical.

### Reference Data​

Configures Checks | SAPPSECertificates
Default Value | 10
Unit | Day

## SAPPSECertWarn​

If any of the 5 valid-to dates PSE files is within the threshold set by monitoring parameter SAPPSECertWarn, but not lower than the SAPPSECertCrit value, the check status is set to Warning.

### Reference Data​

Configures Checks | SAPPSECertificates
Default Value | 30
Unit | Day

## SAPPSECertIgnore​

Expired certificates no longer contribute to SAPPSECertificates status if they are expired for SAPPSECertIgnore days or more.

### Reference Data​

Configures Checks | SAPPSECertificates
Default Value | 10
Unit | Day

## SAPPSECertExclude​

Use this monitoring parameter to create a list of certificate files in CSV format (wildcard `*` is supported). The specified certificates will be excluded by the SAPPSECertificates check.

### Reference Data​

Configures Checks | SAPPSECertificates
Default Value | `sap_system_pki_instance.pse, TEMP*.pse`
Unit | String

## SAPPSECertInclude​

Use this monitoring parameter to create a list of certificate files in CSV format (wildcard `*` is supported). Only the specified certificates will be scanned and processed by the SAPPSECertificates check. If left blank, all the certificates except the ones specified in the SAPPSECertExclude are considered.

### Reference Data​

Configures Checks | SAPPSECertificates
Default Value |
Unit | String

## SAPRouterString​

Configure a route string describing a connection between two hosts using one or more SAProuters.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## SCSMsgSrvConnectErrsCrit​

Starting from SCSMsgSrvConnectErrsCrit failed message server connection attempts the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | SCS_MSGSRV, ASCS_MSGSRV
Default Value | 1
Unit | Number

## SCSMsgSrvHttpPort​

Define the port to connect to the Java_Scs or Abap_Scs Messaging Server. By default, this is `81<system_number>`.

### Reference Data​

Configures Checks | SCS_MSGSRV, ASCS_MSGSRV
Default Value |
Unit | String

## SCSMsgSrvHttpsPort​

If messaging server's HTTPS port detection fails, then the defined value is used.

### Reference Data​

Configures Checks | SCS_MSGSRV
Default Value |
Unit | String

## SNCLibraryPath​

This parameter configures the path and file name of the SAP Cryptographic Library that is used for the SNC encryption of RFCCONNECT.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## SNCSecuDir​

This parameter defines the value for the `SECUDIR` environment variable that is used by the RFC connection over SNC (RFCCONNECT). It is possible to override this parameter on a SAP Instance level.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## TimeOutCCMS​

The Avantra agent waits TimeOutCCMS seconds before it cancels CCMS custom checks.

On very slow systems with a lot of CCMS custom checks defined, it may be necessary to increase this parameter.

note

The parameter controls the cumulated runtime of all defined CCMS Custom Checks of a particular SAP Instance.

### Reference Data​

Configures Checks | None
Default Value | 60
Unit | Seconds

## TimeOutFullCheck​

The Avantra Agent waits TimeOutFullCheck seconds before it cancels a running Daily Check.

It might be necessary to increase the timeout on very big systems (in terms of data size) and depending on the set of active checks.

note

The parameter controls the cumulated runtime of all Checks executed during a Daily Check.

### Reference Data​

Configures Checks | None
Default Value | 450
Unit | Seconds

## TimeOutJ2EEConnect​

The Avantra agent waits TimeOutJ2EEConnect seconds before it cancels a running Java sap-instance connection attempt.

### Reference Data​

Configures Checks | J2EECONNECT
Default Value | 60
Unit | Seconds

## TimeOutMediumCheck​

warning

This is a legacy parameter only valid for Avantra Agents of release 5.2.

The Avantra agent waits TimeOutMediumCheck seconds before it cancels a running Medium check-cycle. On very slow systems, it may be necessary to increase this parameter.

### Reference Data​

Configures Checks | None
Default Value | 300
Unit | Seconds

## TimeOutMsgSrvConnect​

The Avantra agent waits TimeOutMsgSrvConnect seconds before it cancels a connection attempt to the Abap_Scs and Java_Scs message server.

### Reference Data​

Configures Checks | SCS_MSGSRV, ASCS_MSGSRV
Default Value | 30
Unit | Seconds

## TimeOutRFCConnect​

The Avantra agent waits TimeOutRFCConnect seconds before it cancels a running RFC connection attempt.

### Reference Data​

Configures Checks | RFCCONNECT
Default Value | 30
Unit | Seconds

## TimeOutSAPControl​

SAPControl is used for several operations during monitoring, like remote detection of instances for agentless SAP system monitoring, certain checks, etc. This parameter allows you to configure the connect and read timeout for those SAPControl operations per instance.

### Reference Data​

Configures Checks | None
Default Value | 30
Unit | Seconds

## TimeOutTREXConnect​

The Avantra agent waits TimeOutTREXConnect seconds before it cancels a running TREX connection attempt.

### Reference Data​

Configures Checks | TREX Connect
Default Value | 60
Unit | Seconds

## TREXAlertStatusMapping​

This parameter allows you to reconfigure the mapping of the check states of a TREX Alert Server to the check states of Avantra. You must specify a comma-separated list of numbers, which get assigned in order of their appearance to the Avantra states 2 (`CRITICAL`), 1 (`WARNING`), 0 (`OK`), -1 (`UNKNOWN`), -2 (`DISABLED`). Not all states must be specified, so it's sufficient to assign the first 3 values to get a proper mapping.

Optionally, you can specify mappings for the check name in addition to the default mapping, or you can simply change the mapping for individual checks. Consider the following examples:

> `2,1,0` : All TREX checks use mapping `2,1,0`

> `2,1,0;TREX Alertserver Start: 3,2,1` : All TREX checks use mapping `2,1,0` except for check TREX Alertserver Start, which uses `3,2,1`

> `TREX Disk Usage: 2,1,0; TREX CPU Usage: 2,1,0` : All TREX checks use the default mapping `3,2,1,0` except for checks TREX Disk Usage (`2,1,0`) and TREX CPU Usage (`2,1,0`).

The default assignment is 3 > 2 (`CRITICAL`), 2 > 1 (`WARNING`), 1 > 0 (`OK`), 0 > -1 (`UNKNOWN`)

### Reference Data​

Configures Checks | None
Default Value | 3;2;1;0
Unit | String

## TREXConnectErrsCrit​

Starting from TREXConnectErrsCrit failed RFC connection attempts, the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | TREX Connect
Default Value | 1
Unit | Number

## TREXLandscapeID​

If detection of TREX landscape ID fails, then the defined value is used.

### Reference Data​

Configures Checks | None
Default Value |
Unit | String

## WDCertAllowSelfSigned​

If disabled, WD_Certificates will check the trust chain to the root certificate authority. If enabled, the trust chain is not verified, so that self-signed certificates will be OK.

### Reference Data​

Configures Checks | WD_Certificates
Default Value | 1
Unit | Boolean

## WDCertDaysCrit​

If the number of days before the SSL certificate of the SAP web dispatcher expires is below this value, the check status is set to Critical.

### Reference Data​

Configures Checks | WD_Certificates
Default Value | 30
Unit | Number

## WDCertDaysWarn​

If the number of days before the SSL certificate of the SAP web dispatcher expires is below this value but not below WDCertDaysCrit, the check status is set to Warning.

### Reference Data​

Configures Checks | WD_Certificates
Default Value | 60
Unit | Number

## WDConnectErrsCrit​

Starting from WDConnectErrsCrit failed connection attempts, the check status will turn from Warning to Critical.

### Reference Data​

Configures Checks | WD_Connect
Default Value | 1
Unit | Number

## WDConnUsageCrit​

If the number of used connections exceeds WDConnUsageCrit percent of the maximum number of connections available, the check status is set to Critical.

### Reference Data​

Configures Checks | WD_ConnectionStat
Default Value | 95
Unit | %

## WDConnUsageWarn​

If the number of used connections exceeds this value but does not exceed WDConnUsageCrit percent of the maximum number of connections available, the check status is set to Warning.

### Reference Data​

Configures Checks | WD_ConnectionStat
Default Value | 85
Unit | %

## WDQueueUsageCrit​

If the number of used queue entries exceeds WDQueueUsageCrit percent of the maximum number of queue entries available, the check status is set to Critical.

### Reference Data​

Configures Checks | WD_QueueStat
Default Value | 95
Unit | %

## WDQueueUsageWarn​

If the number of used queue entries exceeds this value but does not exceed WDQueueUsageCrit percent of the maximum number of queue entries available, the check status is set to Warning.

### Reference Data​

Configures Checks | WD_QueueStat
Default Value | 85
Unit | %

## WDThreadsUsageCrit​

If the number of used worker threads exceeds WDThreadsUsageCrit percent of the maximum number of worker threads available, the check status is set to Critical.

### Reference Data​

Configures Checks | WD_ThreadStat
Default Value | 95
Unit | %

## WDThreadsUsageWarn​

If the number of used worker threads exceeds this value but does not exceed WDThreadsUsageCrit percent of the maximum number of worker threads available, the check status is set to Warning.

### Reference Data​

Configures Checks | WD_ThreadStat
Default Value | 85
Unit | %

## WorkProcDiaStatusCrit​

### Description​

WorkProcDiaStatusCrit controls the optional part of the WorkProcesses check.

You can define a list of work process status (i.e. `On Hold`, `Stopped`, `Shutdown`, `Reserved`, `Starting`) and / or reasons (from the reason column of SAP transaction Work Process Overview `SM50`). If a work process is found with either the defined status or reason the Check will turn to Critical.

### Reference Data​

Configures Checks | WorkProcesses
Default Value |
Unit | EnumX

## WorkProcDiaStatusNOkPctCrit​

### Description​

Controls the first mandatory sub-check of WorkProcesses.

If the number of non-OK work processes exceeds WorkProcDiaStatusNOkPctCrit percent of the total number of work processes, the WorkProcesses check will turn to Critical.

### Reference Data​

Configures Checks | WorkProcesses
Default Value | 60
Unit | %

## WorkProcDiaStatusNOkPctWarn​

### Description​

Controls the first mandatory sub-check of WorkProcesses. Warning threshold corresponding to WorkProcDiaStatusNOkPctCrit above.

If the number of non-OK work processes exceeds this value but not WorkProcDiaStatusCrit percent of the total number of work processes, the check will turn to Warning, unless any other of the executed sub-checks is Critical.

### Reference Data​

Configures Checks | WorkProcesses
Default Value | 30
Unit | %

## WorkProcDiaStatusWarn​

### Description​

WorkProcDiaStatusWarn controls the optional part of the WorkProcesses check.

You can define a list of work process status (i.e., On Hold, Stopped, Shutdown, Reserved, Starting) and/or reasons (from the reason column of SAP transaction Work Process Overview `SM50`). If a work process is found with either the defined status or reason, the Check will turn to Warning, unless any other of the executed sub-checks is Critical.

### Reference Data​

Configures Checks | WorkProcesses
Default Value |
Unit | EnumX

## WorkProcDiaTimeUsageCrit​

### Description​

Controls the second mandatory sub-check of WorkProcesses.

If the elapsed CPU time of the dialog work process with the lowest CPU time is ≥ WorkProcDiaTimeUsageCrit % of the total elapsed time between two snapshots, the Check Result will be Critical.

### Reference Data​

Configures Checks | WorkProcesses
Default Value | 10
Unit | %

## WorkProcDiaTimeUsageWarn​

### Description​

Controls the second mandatory sub-check of WorkProcesses.

If the elapsed CPU time of the dialog work process with the lowest CPU time is ≥ WorkProcDiaTimeUsageWarn but < WorkProcDiaTimeUsageCrit % of the total elapsed time between two snapshots, the Check Result will be Warning, unless any other of the executed sub-checks is Critical.

### Reference Data​

Configures Checks | WorkProcesses
Default Value | 5
Unit | %