- For the individual log attribute. The changes then overwrite the
properties "inherited" from the MTE class.
In addition, the variant for which the properties are to be changed canbe specified. Note that the owner of a variant must be identical to thecompany name used in the XMI logon. Variants that are specifiedexplicitly are created using Transaction RZ21.
If no variant is specified, the changes will be made for the variantthat has the same name as the company name used for the XMI logon. If avariant with this name does not exist, the system creates itautomatically.Description
INCLUDE RETURN_DESC ID TX
Value range
MSG_TID_INVALID: The specified TID is invalid.
MSG_C_CALL_FAILED: The last C function called could not be executed.
MSG_COMMUNICATION_PROBLEM: The system could execute the method due tocommunication problems (possibly check network connection).
MSG_DB_PROBLEM: The system encountered a problem accessing thedatabase.
INCLUDE RETURN_DEFAULT_RANGE ID TX
Description
The time period in seconds to check for the most serious alert.
The alert monitor evaluates all messages that were added to the logduring this time period, starting from the present time. From thesemessages, it chooses the one that produced the most serious alert. Thismessage is displayed in the alert monitor as the current value of thismonitoring attribute.
Description
Specifies which entry from a log attribute is to be displayed as the"current value" of the attribute. The current value is displayed in thealert monitor.
Value range
The possible modes for determining the current value include:
AL_TD_MSC_VAL_MODE_LAST 1: Displays the most recently reported message
AL_TD_MSC_VAL_MODE_HIGHALRT 2: Displays the message that produced themost serious alert
AL_TD_MSC_VAL_MODE_WORST_SINCE 3: Displays the message that producedthe most serious alert in a specified time period. When you specify atime period, the alert monitor searches for the most serious alertwithin that time period.
Description
INCLUDE EXTERNAL_USER_NAME_DESC ID TX
Value range
INCLUDE EXTERNAL_USER_NAME_RANGE ID TX
Description
Specifies how many message lines should be kept in a log attribute.
Example: If you specify 100 in this field and request that the newestmessages should be kept, then your message log will always contain the100 most recent messages reported into the message log.
Note that the amount of shared memory available to the monitoringarchitecture may also limit the size of a message log. If the messagelog remains smaller than the limit that you specify here, then increasethe amount of shared memory available to the monitoring architecture.Do this on the R/3 server in which the log monitoring attribute isheld.
This option applies only to log attributes in which the monitoringarchitecture provides the log management functionality. This optiondoes not apply to log attributes that refer to the R/3 system log or toexternal logs.
Description
The number of message lines to be kept in the message log.
Procedure
Choose one of the following:
- As many as possible to keep as many message lines in the message
log as possible. This uses as much space as is available for the logattribute. There are usually more messages held than specified inMax. number of lines to be saved.
- The oldest so that the message log contains the oldest messages
that were reported into the message log. The number of oldest messagesthat are saved in the message log depends on the Max. number oflines to be saved that you have specified.
- The newest so that the message log contains the newest messages
that were reported into the message log. The number of newest messagesthat are saved in the message log depends on the Max. number oflines to be saved that you have specified.Description
Specifies the maximum number of alerts that should be kept active for aparticular monitor attribute. Should the number of alerts exceed thislimit, then the excess alerts are discarded according to the methodspecified for the attribute (see data elementALKEEPALTY).
In addition to this user-definable limit, the number of alerts that canbe held is limited by the physical size of the shared memory area setaside for the monitoring architecture. Space in this area is allocatedfor monitoring objects and attributes, properties, and data. Remainingspace is filled with alerts. The number of alerts that can be retainedcan therefore be increased by allocating more shared memory to themonitoring architecture (SAP system profile parameters for sharedmemory).Description
This (optional) parameter defines the maximum severity level before analert is triggered.
An alert is only triggered when the severity exceeds the value sethere.
Value range
Values can be between 0 (very low) and 255 (very high).
Description
This (optional) parameter defines the maximum value before an alert istriggered.
Value range
Possible values are:
- 0: inactive value
- 1: GREEN
- 2: Yellow
- 3: RED
If YELLOW is selected, an alert will only be triggered if the value isRED.Description
INCLUDE TID_DESC ID TX
Description
If this (optional) parameter is set ("X"), the specified changes areexecuted for the monitor tree element itself. Otherwise, the changesare executed for the MTE class the monitor tree element is assigned to.
Description
This (optional) parameter defines the name of the variant used.
The owner of the specified variant must be identical to the companyname entered for the XMI logon. If no variant is entered, the systemuses the variant with the same name as the company name entered for theXMI logon. If this variant does not exist, the system creates itautomatically.
Description
This parameter contains the filter definition for the log attribute.
INCLUDE BAPI_DATAELEMENT ID TX