Transferring Monitoring Pauses with CCMS Agents 

Use

You can work with monitoring pauses in the CCMS monitoring infrastructure. During a monitoring pause of this type, depending on the settings either the generation of alerts for the relevant monitored systems or all monitoring for these systems, including the collection of monitoring data, is deactivated  More information: Administration of Monitoring Pauses in the Alert Monitor.

There are three ways in which you can create monitoring pauses:

●      Centrally from the System Landscape Administration work center in the Solution Manager

●      Centrally from the configuration interface of the CCMSPING availability monitoring (see Creating and Deleting Monitoring Pauses)

●      Locally from the monitored instance using a  CCMS Agent. In this case, the pause always relates to the instance that the agent is monitoring.

The third method is described in this section.

While with central scheduling, you can create one-time and periodically recurring monitoring pauses with any start and end times, when you are using the CCMS agent, you can only schedule a monitoring pause for immediate start or end a monitoring pause with immediate effect.

Prerequisites

The prerequisites fort he central monitoring system (CEN) and the monitored systems are described in Administration of Monitoring Pauses in the Alert Monitor.

Features

If you use the CCMS agent to start a monitoring pause for the monitored instance, the following steps are automatically performed:

●      The monitoring pause is sent by RFC from the monitored instance to the central monitoring system (client RFC call)

●      In the central monitoring system, a monitoring pause is activated for the nodes that provide semantic data about this instance.

●      On the local monitored instance, a monitoring pause is activated for the entire monitoring segment.

Activities

Starting a Monitoring Pause

To start a monitoring pause for the instance that the agent monitors, enter the appropriate command below for your instance type at the operating system command prompt:

●      ABAP instance

sapccm4x pf=<instance profile> -monitoring_off
-level NO_ALERTS|NO_VALUES [-initiator <user name>]
[-info <any text>]

●      Java/TREX instance

sapccmsr –j2ee pf=<instance profile> -monitoring_off
-level NO_ALERTS|NO_VALUES [-initiator <user name>]
[-info <any text>]

Ending a Monitoring Pause

To end a monitoring pause for the instance that the agent monitors, enter the appropriate command below for your instance type at the operating system command prompt:

●      ABAP instance

sapccm4x pf=<instance profile> -monitoring_on
[-initiator <user name>] [-info <any text>]

●      Java/TREX instance

sapccmsr –j2ee pf=<instance profile> -monitoring_on
[-initiator <user name>] [-info <any text>]

The parameters and options in these commands have the following meaning:

Parameter/Option	Meaning
instance profile	Complete path of the profile of the monitored instance, for example c:\usr\sap\C11\SYS\profile\C11_DVEBMGS00_host1
-monitoring_off	Monitoring pause starts with immediate effect
-monitoring_on	Monitoring pause ends with immediate effect
-level NO_ALERTS|NO_VALUES	NO_ALERTS: During the monitoring pause, no alerts are generated. However, the monitoring data for the instance is still collected during the pause. NO_VALUES: During the monitoring pause, no alerts are generated, and the collection of the monitoring data itself is also deactivated during the pause.
-initiator <user name>	Name of the user responsible for the monitoring pause (optional)
-info <any text>	Any text, which is stored with the monitoring pause. This text is usually the reason for the monitoring pause (optional).

 CCMS Agents start page