Central Monitoring of Operating System Data

The operating system collector SAPOSCOL collects operating system data for any host and stores this in a segment of the shared memory. SAP NetWeaver management agents can copy this data to the monitoring segment and transfer it to the central monitoring system. This means that the data is visilbe in the CCMS monitoring architecture, and is displayed in the operating system monitor . For more detailed information about the operating system collector, see operating system collector SAPOSCOL and SAP Note 371023.

Operating System Data Displayed in the Alert Monitor

After the successful installation of the agent, the CCMS monitoring architecture displays the following data in the Operating System monitor:

• Filesystems
• CPU
• Paging
• Commit Charge (only for Microsoft Windows)
• Swap Space (only for UNIX)
• OS Collector
• LAN

Irrespective of this, the operating system monitor displays all data collected by SAPOSCOL. It is therefore well suited to being an analysis method for the Operating System monitor.

Configuring the Monitoring of Operating System Data

The agent also allows an individualized selection of subtrees for the Operating System and Filesystems monitors. You can use a filter to explicitly remove subtrees or entire components from the monitoring display. No monitoring nodes are then generated for these. As an alternative to filtering out file systems, you can activate an exclusive monitoring with which only the file systems that you explicitly specify are monitored. All other file systems are not then monitored.

You can also change the names of the MTE classes for the monitored operating system data as you wish. This means that you can assign operating system data from different hosts to different MTE classes. This simplifies Customizing, for example, the threshold values or the assignment of different auto-reactions depending on the function or the platform (Microsoft Windows, UNIX) of the monitored hosts.

In the configuration file SAPCCMSR.INI , you can use the parameter OsColFileto specify a configuration file in which you can make these settings. In this case, SAPCCMSR.INI would contain an entry of the type:

OsColFile <configuration file for monitoring operating system data>

This SAPOSCOL filter file is referred to as oscolfile.txt in the following.

Structure of the SAPOSCOL Filter File oscolfile.txt

You can make the following specifications in the oscolfile.txt filter file:

• Filtering Out Components

  After the keyword FilterOutComponent, enter the components that you do not want to be copied to the monitoring segment, and for which the system will therefore not create a subtree in the monitoring tree in transaction RZ20.

• Filtering Out File Systems

  You can use the keyword FilterOutFilesystem to filter out file systems that are not to be copied to the monitoring segment. In this way, you can, for example, exclude particular file systems that are always 100% full from the monitoring. You can specify the file system name or use a pattern with a wildcard character (*).

• Set the MTE Class and Attribute Group of the Monitored Operating System Data

  In the context of monitoring, you can also set the associated MTE class and attribute group yourself for the following components:

  • Microsoft Windows: CPU, Lan, Commit_Charge, Paging
  • UNIX: CPU, Lan, Swap_Space, Paging

  Since this happens at host level, you can assign the operating system data of different hosts to different MTE classes. To do this, enter the keyword MonitorComponent. The syntax of the keyword is:

  MonitorComponent <component name> <MTE class> [<attribute group>]

  The corresponding monitoring objects and monitoring attributes then receive the following names:

  Node Name	Standard MTE Class	MTE Class Set Yourself
  CPU   CPU_Utilization   5minLoadAverage   Idle   Number of CPUs	CPU   CPU_Utilization   5minLoadAverage   Idle   CPU_Number	<Name>   <Name>_Utilization   <Name>_5minLoadAverage   <Name>_Idle   <Name>_CPU_Number
  Paging   Page_In   Page_Out	Paging   Page_In   Page_Out	<Name>   <Name>_Page_In   <Name>_Page_Out
  Commit_Charge   CommitChargeFree   Commit_Percent	Commit_Charge   CommitChargeFreeSpace   CommitChargePercent_Used	<Name>   <Name>_FreeSpace   <Name>_Percent_Used
  Swap_Space   Freespace   Percentage_Used	Swap_Space   SwapFreespace   SwapPercentage_Used	<Name>   <Name>_FreeSpace   <Name>_Percentage_Used
  Lan   <Name of the LAN>     Packets_In     Packets_Out     Collisions     Errors In     Errors Out	Lan   LanMO     LanPacketsIn     LanPacketsOut     LanCollisions     LanErrorsIn     LanErrorsOut	<Name>   <Name>_MO     <Name>_PacketsIn     <Name>_PacketsOut     <Name>_Collisions     <Name>_ErrorsIn     <Name>_ErrorsOut

  Note

  You can see from the table that the set MTE class is used as a prefix for the associated monitoring attributes. Since the length of the MTE class is restricted to 40 characters, a maximum of 24 characters are available to your for the name that you have chosen.

• Set the MTE Class and Attribute Group of the Monitored Disks

  In the same way as setting your own name for the MTE class and attribute group for the monitored operating system data, there is a keyword available with which you can set your own name for the MTE class and attribute group for disks. To do this, enter the keyword MonitorDisk. The syntax of the keyword is:

  MonitorDisk <disk name> <MTE class> [<attribute group>]

  The corresponding monitoring objects and monitoring attributes then receive the following names:

  Node Name	Standard MTE Class	MTE Class Set Yourself
  Disk   <Disk name>     Utilization     DataTransfer     QueueLength     ResponseTime     WaitTime     ServiceTime	Disk   DiskMO     DiskUtilization     DiskDataTransfer     DiskQueueLength     DiskResponseTime     DiskWaitTime     DiskServiceTime	<Name>   <Name>_MO     <Name>_Utilization     <Name>_DataTransfer     <Name>_QueueLength     <Name>_ResponseTime     <Name>_WaitTime     <Name>_ServiceTime

• Adjusting Monitoring of File Systems

  As an alternative to filtering out individual file systems, you can activate an exclusive monitoring. In this case, the system creates a subtree in the monitoring architecture for only the file systems that you specify with the keyword MonitorFilesystem. Other file systems are ignored. Entries with the keyword FilterOutFilesystem are also ignored. The syntax of the keyword is:

  MonitorFilesystem <file system> [<MTE class> [<attribute group>]]

  You can also assign a separate MTE class or attribute group to the monitoring object for the file systems (by default, this is always the class FilesystemMO), so that, for example, you can use a rule-based monitor to display only the file systems that you have explicitly assigned to this MTE class.

• Adjusting the Monitoring of the LAN Interfaces

  You can monitor specific LAN interfaces exclusively in the same way as monitoring certain file systems. You can also set the MTE class and the attribute group of the LAN interfaces to be monitored. To do this, enter the keyword MonitorLAN. The syntax of the keyword is:

  MonitorLAN <LAN> [<MTE class> [<attribute group>]]

  Note

  If you simply want to set the MTE class for all LAN subtrees, in the same way as with the keyword MonitorComponent, enter the wildcard character * for <LAN>.

  Note also that the name for <LAN>must not contain any spaces. In this case, use the wildcard character * as a workaround. In this way, if you wanted, for example, to monitor the LAN interface MS TCP, you could enter only MS* for <LAN>.

• Set the MTE Class and Attribute Group of Monitored Processes

  By default, the MTE class MonitoredProcessesMo is assigned to processes that are monitored by the operating system collector SAPOSCOL. You can change this MTE class (and the attribute group) by specifying the desired name after the keyword MonitorProcess. The syntax of the keyword is:

  MonitorProcess <process name> <MTE class> [<attribute group>]

  Note

  You can individually set the MTE class and attribute group of the monitored processes individually in the selection of the monitored processes (see Monitoring Selected Processes with SAPOSCOL ). This has the advantage that all configuration settings for the monitored processes are in one file.

  Note that with the keyword MonitorProcess, you only assign monitored processes to classes and groups; unlike FilterOutFilesystem and MonitorFilesystem, it does not have any filter functions.

Example SAPOSCOL Filter File oscolfile.txt

The following file is intended to assist you in creating the filter file oscolfile.txt; the meaning of selected configuration settings is explained in the example below:

####################################################################### ###                                                                     ### OsColFile.txt                                                       ### Configuration file for Operating System Monitoring                  ###                                                                     #######################################################################                                                                         # FilterOutComponent <Component Name>                                   ### CCMS agent does not create MTEs for <Component Name>                ### Windows: <Component Name> = CPU | Lan | Commit_Charge | Paging |    ###                             Filesystems                             ### UNIX:    <Component Name> = CPU | Lan | Swap_Space | Paging |       ###                             Filesystems                                                                                                     # FilterOutFilesystem <Filesystem Name> | <Pattern>                     ### CCMS agent does not create MTEs for <Filesystem Name> |<Filesystem> ### Filesystem name can contain '*' as a wildcard (<Pattern>). ### CCMS agent does not create MTEs for <Filesystem Name> | <Pattern>                                                                           # MonitorFilesystem <Name> | <Pattern>   [ <MTE Class>   [<Group>]]     ### CCMS agent creates MTEs for this file system only. All other        ### Filesystems are ignored                                             ### Name can contain '*' as a wildcard (<Pattern>)                      ### Name can be an unsubstituted filesystem name e.g. $DIR_TRANS        ### $DIR_PERF, if these represent file systems collected by saposcol                                                                            ### <MTE Class>  and  <Group> are optional. If you want to specify      ### your own customizing group you have to specify the MTE class, too. # MonitorComponent <Component Name> <MTE Class> [<Group>]               ### CCMS agent creates MTEs with specified MTE class and customizing    ### group. ### <Group> is optional. If you don't specify the customizing group,    ### then the standard name is used. ###                                                                     ### Windows: <Component Name> = CPU | Commit_Charge | Paging            ### UNIX:    <Component Name> = CPU | SwapSpace | Paging                                                                                        # MonitorLAN <Name> | <Pattern>   [ <MTE Class>   [<Group>]]            ### CCMS agent creates MTEs for this LAN interfaces only. All other     ### LAN interfaces are ignored                                          ### Name can contain '*' as a wildcard (<Pattern>)                      ### <MTE Class>  and  <Group> are optional. If you want to specify      ### your own customizing group you have to specify the MTE class, too. # MonitorProcess <Name> | <Pattern> <MTE Class> [<Group>]               ### Changes the MTE Class (and the Attribute Group) of the monitoring   ### objects of the monitored process <Name>. Name can contain '*' as a  ### wildcard (<Pattern>). If you want to specify your own customizing   ### group you have to specify the MTE class, too. 

Examples of Configuration Parameters and their Meaning

 Infrastructure of the SAP NetWeaver Management Agents Start Page