Configuring Monitoring Settings

You use this procedure to specify the global monitoring settings in SAP Landscape Management.

Prerequisites

When using an ABAP system or LDAP as backend for user management, use a local user of the SAP NetWeaver Java engine to perform the configuration. Otherwise the jobs stop working if the user backend is unavailable.
You have the authorization to configure monitoring settings.

For more information, see Standard Permissions.

Procedure

Choose Setup Settings.
Choose Expert Mode.
On the Monitoring tab, choose Edit.

Specify your general monitoring settings.

Field	Default Value	Possible Values	Description
OS Process Names to be Ignored when Determining Instance Status and Calculating Validation Warnings [semicolon separated list, wildcards allowed]	None	List of process names, separated by semicolons	Instances are realized by Operating System (OS) processes. When determining the status of an instance or when calculating validation warnings for an instance, the statuses of all OS processes belonging to this instance are determined and evaluated. If for some reason any OS processes are ignored, they can be counted using this setting. Example igswd.exe; igswd
OS Process Names to be Ignored when Determining Instance Statuses [semicolon separated list, wildcards allowed]	None	List of process names, separated by semicolons	Instances are realized by OS processes. When determining the status of an instance, the statuses of all OS processes belonging to this instance are determined and evaluated. If for some reason any OS processes are ignored, they can be counted using this setting. Although some OS processes are ignored when determining the instance status, they are not ignored when calculating validation warnings. Example igswd.exe; igswd
Use FQDN Hostnames Only	Checkbox deselected	Checkbox selected Checkbox deselected	When you select this checkbox, all hosts and instances not configured with a full qualified hostnames will become invalid. To use system clones you need to unrepare existing clones and install at least SAP Host Agent 720 Patch 205.
Allowed Hostnames for Outgoing Connections [semicolon separated, ip-addresses and host names allowed]	localhost;	Valid allowed hostnames	Default hostnames/ip-addresses for all outgoing connections.
Allowed Ports for Outgoing Connections [semicolon separated, instance names allowed]:	nfs;ldap;ldaps;cifs;microsoft-ds	Valid allowed ports	Default ports for all outgoing connections.
Time Interval between Periodic Monitoring Wakeups [seconds]	10	2 - 30	The monitoring manager is an asynchronous background task and sleeps most of the time. From time to time the manager wakes up, triggers the monitoring of multiple instances and hosts, and then sleeps again. The specified parameter defines the time interval between subsequent wakeups.
Socket Connection Timeout for Monitoring [seconds]	5	1 - 30	When monitoring instances and hosts, network connections have to be established for sending monitoring requests to SAP Host Agents and instance agents. The specified parameter defines how long SAP Landscape Management waits until the connection cancels with an error.
Socket Read Timeout for Monitoring [seconds]	15	1 - 120	When monitoring instances and hosts, SAP Landscape Management sends information requests to SAP Host Agents and instance agents. The specified parameter defines how long SAP Landscape Management waits for the connection acknowledgment before aborting the request.
Maximum Retries after Connection Timeout or Read Timeout [seconds]	3	1 - 10	If connection timeouts or read timeouts occur, SAP Landscape Management monitoring tries the specified number of times to successfully complete a request before reporting an error.
Time Interval for Refreshing Host Monitoring Data [seconds]	60	2 - 600	SAP Landscape Management monitoring periodically updates host monitoring data. The specified setting defines the time interval for one update cycle.
Time Interval for Refreshing Instance Monitoring Data [seconds]	60	2 - 600	SAP Landscape Management monitoring periodically updates instance monitoring data. The specified setting defines the time interval for one update cycle.
Time Interval for Refreshing Inventory Monitoring Data [seconds]	300	2 - 3600	SAP Landscape Management monitoring periodically updates inventory monitoring data. The specified setting defines the time interval for one update cycle.
Time Interval for Refreshing Storage Monitoring Data [seconds]	86400	60 - 86400	SAP Landscape Management periodically caches and updates the mapping between mount points configured on SAP systems and the related volumes on storage systems. In order to do this, all configured storage managers are called. The specified setting defines the time interval in which all mounts of all configured systems are mapped.
Maximum Size of Persistent Monitoring Cache [bytes]	524288000		To enhance the performance of the monitoring charts the monitoring engine keeps recently collected metrics in memory cache. Generally the bigger the cache, the further in past the charts can be served from the memory. Larger landscapes will need larger cache to store data over the same time-frame.
After which the Minutely Aggregated Monitoring Data gets Purged [days]	7	0 - 365	The number of days after which the minutely aggregated data gets deleted from the database. Recommendation To use disk space economically, keep older data in the database with lower granular aggregation like hourly or daily.
After which the Hourly Aggregated Monitoring Data gets Purged [days]	90	0 - 3650	The number of days after which the hourly aggregated data gets deleted from the database. Recommendation To use disk space economically, keep older data in the database with daily aggregation.
After which the Daily Aggregated Monitoring Data gets Purged [days]	2555	0 - 2147483647	The number of days after which the minutely aggregated data gets deleted from the database. Recommendation To use disk space economically, it is recommended, that after certain time period even daily aggregations get finally purged.
Detailed Host Monitoring	Checkbox selected	Checkbox selected Checkbox deselected	To update processor and monitoring data during monitoring calls, keep the checkbox selected.

Metrics Specifications

This table lists the monitoring metrics (for example, resource.cpu.usage) that are supported by SAP Landscape Management, and specifies their properties (such as unit, default aggregation, discrete, or continuous, persisted).

Aggregation Type	Description
MIN	The aggregated value is the smallest value among the aggregated entities.
MAX	The aggregated value is the largest value among the aggregated entities.
SUM	The aggregated value is the sum of the values among the aggregated entities.
AVERAGE	The aggregated value is the mean of the values among the aggregated entities.

Metrics Collectors

This table lists the monitoring metrics collectors (for example, the collector resource_util_cache) and their definitions. A collector is a component that periodically runs and collects metrics.

One of the implementations in the following table is assigned to each collector. The implementation indirectly determines the Java class that represents the collector.

Implementation	Description
RESOURCE_UTIL_CACHE_METRICS_COLLECTOR	The metrics values are collected from the internal status cache which obtains the values from the SAP Host Agent of the managed host.
HOST_AGENT_METRICS_COLLECTOR	The metrics values are collected from the SAP Host Agent of the managed host.
SAP_CCMS_METRICS_COLLECTOR	The metrics values are collected from the managed instance through the Computing Center Management System (CCMS) RFC API.
VIRT_LANDSCAPE_CACHE_COLLECTOR	The metrics values are collected from the internal virtual landscape monitoring cache which obtains the values from the managed virtual providers through the internal virtualization API.
SERVICE_HEALTH_COLLECTOR	The metrics values are collected from the internal service status cache which obtains the values from the instance agent of the managed instance.
INVENTORY_COLLECTOR	The metrics values are collected internally based on the current inventory.
VALIDATION_COLLECTOR	The metrics values are collected internally based on the current validation results.

The Targets column defines the entity types that are monitored by the collector.

Entity Type	Description
ComputerSystem	Managed host
System	Managed SAP system
Database	Managed database instance
Instance	SAP instance
Characteristic	Internal characteristic such as pool It must be defined together with the characteristic name, for example, Characteristic:Pool.
VirtualProvider	Virtual provider
VirtualResource	Virtual host
HostSystem	Host system The physical servers hosting virtual hosts
ResourcePool	A group of physical hosts hosting virtual hosts
Datastore	Data storage of a virtual provider where virtual hosts are stored
ComputeCluster	A logical unit of virtual computing hosts

Metrics Collection Mappings

This table maps the metrics specification and metrics collector, and specifies the source, that is, how the collector retrieves the value for the entity monitored.

Note
- Database log archiving
- The required storage size for monitoring data depends on the number of monitored entities, the number of monitored metrics (for example, CPU load, memory) in each host and their configuration. The monitoring data is frequently collected, aggregated, and purged. A large number of database logs may be generated. Therefore, appropriate database log archiving must be ensured.
To estimate the required storage size for monitoring data, choose Database Size Estimator for Persistent Monitoring Data button.
Save your entries.

Results

The SAP Landscape Management job LVM_Job_Monitoring is rescheduled using the current user.

You can review the status of the jobs and the scheduling user in the SAP NetWeaver Administrator tool Java Scheduler.

SAP Landscape Management 3.0, Enterprise Edition

Configuring Monitoring Settings

Prerequisites

Procedure

Results

Next Steps