Server - Monitoring Parameters

If the Avantra Server connects to the Avantra Agent through one or more avantra-gateways, you can define this value.

If no connection could be established to an Avantra Agent for more than AgentConnectTimeCrit minutes, the Avantra Server will set the status of the AgentConnect Check to Critical.

If no connection could be established to an Avantra Agent for more than AgentConnectTimeWarn minutes, the Avantra Server will set the status of the AgentConnect Check to Warning.

General-purpose parameter. Do not use it unless instructed by the Avantra support team.

Defines the Avantra Agent TCP/IP listener port. Do not change this value unless the default port is already in use.

If you need to change it, please contact our support for assistance.

If you are not familiar with TCP/IP, or you do not know what a port is, you may want to start further reading at RFC 1180.

By default, the communication between Avantra Agent and Avantra Server is secured by SSL using client-side certificates. Turning SSL off should only be required under rare circumstances, i.e. to work around SSL problems with the Avantra Agent Java Runtime Environment. Please be aware that without SSL communication between Avantra Agent and Avantra Server will be plain text HTTP.

If the Avantra Server did not receive data for more than AliveTimeout minutes, it will set the status of Check AGENTALIVE to Critical. You may decrease this parameter for productive systems, and increase it for systems connected via low speed/low bandwidth links.

AutoChangeDetectionIgnore is used to exclude parameters from System Change Auto Detection. If, for example, a parameter value changes regularly and this behaviour 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.

This parameter has currently no effect for Servers.

Defines the time interval between two consecutive runs of the Basic Check Cycle.

Determine if the Agent shall perform cloud detection. For the purpose of cloud detection, several predefined URLs need to be accessed, which may lead to firewall messages depending on your environment. In this case, you can turn off cloud detection by this parameter.

Defines how long (in minutes) the AGENTALIVE Check remains in status Warning after a Virtual Cluster Server has switched from one Physical Server to the other.

The value of CPULoadAverageTime defines the time period used to compute the average CPU load over. CPULOAD will only result in Warning or Critical status if the CPU load of the system was over the corresponding threshold for CPULoadAverageTime minutes or more. The higher this value is, the less likely you will get alerts due to CPU peaks over a small period of time only.

If the server’s average CPU load exceeds CPULoadCrit percent the check status of CPULOAD turns to Critical.

If the server’s average CPU load exceeds CPULoadWarn percent but does not exceed CPULoadCrit percent, the check status of CPULOAD turns to Warning.

Usually, Daily Checks are executed at DailyCheckStart and delivered immediately. In a large-scale environment with hundreds of Avantra Agents, and if DailyCheckStart has the same value for all Avantra Agents, it may cause a high load of the Avantra Server.

If you set this parameter, the Avantra Agent randomly chooses a time between 0 and DailyCheckSendTimeRange minutes before the Daily Check is actually delivered.

Defines the start time of the FULLCHECK in the Avantra Agent's local time zone. It affects all SAP Instances eventually installed on the same Physical Server or Virtual Cluster Server.

Use only if instructed by Avantra.

If the predicted point in time when the filesystem usage limit is exceeded is within the upcoming FSExCrit hours, the check status of FILESYSTEMS is set to Critical.

If the predicted point in time when the filesystem usage limit is exceeded is within the upcoming FSExWarn hours, but not within the upcoming FSExCrit hours, the check status of FILESYSTEMS is set to Warning (unless the FSUsageCrit threshold is exceeded for some file system).

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

If the parameter is selected the FILESYSTEMS Check also monitors non-local file systems, i.e. mapped network drives (in the Windows world) and NFS-mounted file systems (in the Unix world).

If one or more of the Physical Server’s filesystem inode usage exceeds FSNodeCrit percent, the Check status is set to Critical (on Unix-like operating systems only).

If one or more of the Physical Server’s filesystem inode usage exceeds FSNodeWarn percent, but none of them exceeds FSNodeCrit percent, the check status is set to Warning (unless any other Critical threshold is exceeded for some filesystem; on Unix-like operating systems only).

A list of (local) filesystem types. Avantra Agent does not monitor filesystems having a type not defined in this parameter.

A list of (network) filesystem types. Avantra Agent does not monitor filesystems having a type not defined in this parameter. The parameter is only effective if FSMonitorNetwork is selected.

If one or more of the Physical Server’s filesystem usage exceeds the FSUsageCrit 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.

If one or more of the Physical Server’s filesystem usage exceeds the FSUsageWarn threshold, but none of them exceeds the FSUsageCrit threshold, the check status is set to Warning (unless any other Critical threshold is exceeded for some filesystem).

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.

This parameter is used to configure Tunnels to other Avantra Agents used as Gateways or the Avantra Server.

If you set this parameter Avantra will stop monitoring the System.

This setting can be used if you want to monitor this System only using End-to-End Application Monitoring (from a different System).

Defines how many old log files to keep. If set to 0, there is one log file kept called lyceus.log.old.

If set to a value n greater 0, n log files are kept named with time stamp suffix.

Use this parameter if MasterHost and MasterPort parameters are not sufficient to specify the routing from Avantra Agent to Avantra Server.

Hostname or IP address of the Avantra server, more precisely, of the server running Avantra Server.

The default value is taken from the Avantra Server property Network.masterhost which itself is determined automatically.

If you use MasterConnectRoute, you probably need to set MasterHost to the hostname of the last gateway defined in MasterConnectRoute.

TCP/IP port number the Avantra Server is listening to.

The default value is taken from the Avantra Server property Network.masterport.

If you use AgentConnectRoute you probably need to set MasterPort to the TCP/IP port number of the last gateway defined in AgentConnectRoute.

Defines the time interval between two consecutive runs of the Medium Check Cycle. Please be aware that the cycle time is always 'rounded' up to the next CheckCycleTime time. For example, if you enter 8 minutes as the MediumCheckCycleTime and the CheckCycleTime is set to 5 minutes, the check will be executed every 10 minutes in every 2nd check interval.

If the physical memory usage exceeds the MemoryUsageCrit 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.

If the physical memory usage exceeds the MemoryUsageWarn threshold but does not exceed the MemoryUsageCrit 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.

The Avantra Agent re-sends a Check Result after MessageSuppressTime minutes if check status and check message have not changed during this time.

If the total amount of paging space usage exceeds the PagingSpaceCrit 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.

If the total amount of paging space usage exceeds the PagingSpaceWarn threshold but does not exceed the PagingSpaceCrit 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.

If the Server's total amount of paging space is less PagingSpacePhysMemRatioWarn percent of the physical memory, the check status of Check PAGINGSPACE is set to Warning.

The default is 0, in which case this sub-Check is disabled.

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.

Use this monitoring parameter to collect disk IO performance data for file systems. Disk IO performance data for file systems is not collected by default. It must be turned on using this monitoring parameter. Define the names of the file systems you want to collect data for. Multiple entries can be separated by one or more spaces, comma, or semicolon. If one of these characters appears in a file system path, you must escape it with \. You can use wildcard * to define multiple file systems.

Use this monitoring parameter to collect performance data of network I/O interfaces. Performance data is not collected by default for network interfaces. It must be turned on with this monitoring parameter. Define the names of the network interfaces, multiple network interfaces can be separated with spaces, comma, or semicolon. You can use wildcard \* to define network interfaces.

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

Defines the maximum number of bytes of the check message that are transferred to the Avantra Server. This is to prevent network transmission problems in case of very large message sizes.

This parameter controls the SAP Instance Auto Discovery algorithm of the Avantra Agent.

By default, only SAP Instances with an instance profile file ending on the hostname (on Physical Servers) or the Virtual Cluster Server Name (on Virtual Cluster Servers) are monitored. If your profiles are named differently and you are using logical hostnames, first, have a look at SAPLogicalHostDetection and SAPLogicalHostResolution.

You can change this behavior by using the keyword ALL. The keywords ALL and EXCEPT can be combined.

This parameter determines how SAP Instances are discovered on the server. SAPInstanceDetectionMode has three values: PROFILES, SAPServices, and AUTO. In the first case, the filesystem is scanned for SAP instance profiles, which is the default behavior. In the case of SAPServices, the sapservices file is parsed and SAP instance profiles are detected based on the findings. For the AUTO search method, profiles are determined from the sapservices file if it is present and can be read. Otherwise, a filesystem scan for SAP instance profiles will be performed.

SAPInstanceProfilePaths tells the Avantra Agent where to look for profiles additionally. There are specified directories that contain SAP Instance profiles, or the direct paths can be specified to the certain profile files. These profiles then are examined for systems and used for system detection.

If the hostname used by the instance (SAPLOCALHOST) is a Logical Host Name and doesn’t match the Server Name defined in Avantra, monitoring will not be performed. But if this parameter is activated on the corresponding SAP System, the Agent will do a /etc/hosts and DNS lookup for the Logical Host Name, and if the name resolves to a matching IP address, the instance will be monitored by the Agent.

! Do not use this parameter in conjunction with Virtual Cluster Servers. Otherwise, instances might be detected twice - once for the logical host and once for a VCS with the corresponding host name, which may lead to mutual cancellation.

In addition to the SAPLogicalHostDetection parameter, this parameter can be used to define IP addresses or host names for Logical Host name resolution. Normally the automatic resolution using the hosts file or DNS will work, but in case of DNS problems or Agentless Monitoring, this parameter can be set to customize the resolution. On a per-host basis, mappings of multiple host names to an IP address or host name can be defined. If Logical Host detection is active but this parameter doesn’t provide a mapping, the detection falls back to the hosts file / DNS mapping.

The format of the parameter looks as follows:

The following examples show how to set the parameter:

The <sid>adm user reads the user environment of the bootstrap instance, but this user can be arbitrary. Therefore the correct mapping can be specified from system id (sid) to the user with this parameter, for example:

WDB: wdmadm

It tells the Avantra Agent that the sidadm of system WDB is 'wdmadm' and provides the environment of wdmadm for system WDB.

Instructs the Avantra Server to automatically define SAP Systems, when instances are detected on a server which can’t be assigned to an existing SAP System in Avantra.

The SAP System is assigned to the customer that owns the server the instance has been detected on. The Unified SAP SID will be composed of the first three letters of the customer name and the real SAP SID, i.e customer Avantra and system PR1 will result in AVA_PR1.

Defines the maximum time (in seconds) the Avantra Agent reads an incoming TCP/IP connection. There usually is no need to change this value.

Defines the Critical threshold for the TimeOffset check; if the Agent server UTC time differs from the Avantra Server UTC time more than the configured value, TimeOffset becomes Critical.

Defines the Warning threshold for the TimeOffset check; if the Agent server UTC time differs from the Avantra Server UTC time more than the configured value, TimeOffset becomes Warning.

Defines the timeout for Avantra Agent child processes performing operating system calls. If the value exceeds, the process is terminated. There usually is no need to change this value. This parameter affects Solaris systems only.

Defines how verbose the Avantra Agent performs logging. Valid values range from 0 to 5

This monitoring parameter allows you to control Virtual Cluster Server detection (only applicable to Avantra Agents >= Avantra Version 20.11.7). There are three possible settings for this parameter: Auto (default), Local, Master.