Avoiding Objects Being Copied to the Monitoring Segment 
Avoiding Objects Being Copied to the Monitoring Segment
Use
If you use a
CCMS agent to transfer the SAPOSCOL data to a central monitoring system, you can use the transfer of the data from the SAPOSCOL shared memory segment to the CCMS monitoring segment to remove certain data that is not to be displayed. You can do this by specifying a configuration file that specifies which SAPOSCOL data is not to be copied to the monitoring architecture segment. In this way, you can remove file systems and components from the monitoring segment.
This is, for example, useful, if you monitor file systems with a rule-based monitor, but want to exclude certain file systems that are always 100% full from this monitoring.
The hidden data is still collected by SAPOSCOL; it is simply no longer copied to the CCMS monitoring segment and is not displayed in the
Alert Monitor.
Every agent has the configuration file SAPCCMSR.INI in its working directory. In this file, enter the line
OSColFile <File path of the filter file>.The filter file contains information about the components and file systems that are not to be monitored. You can remove file systems from the CCMS monitoring segment using the parameter
FilterOutFilesystem; you can use the parameter FilterOutComponent to remove entire components from the CCMS monitoring segment.Example
The following lines are contained in the configuration file SAPCCMSR.INI:
### Format of entries for mechanism to filter out
### SAPOSCOL values:
OsColFile d:\usr\sap\TVB\D26\log\sapccm4x\oscol.ini
The specified file oscol.ini contains the following lines:
FilterOutComponent LAN
FilterOutFilesystem d:\test
No more values are displayed in the monitoring architecture for the file system
d:\test and for values for the LAN.See also:
