Note the following points when monitoring messages using the Logged Messages (PL_MESS) record:

• When a message occurs that satisfies the condition expression set when the alarm is defined, the alarm status changes to error. After that, when a message occurs that does not satisfy the condition expression, the alarm status returns to normal. If you set the alarm monitoring using messages, check the messages on the Event Monitor or Event History window of PFM - Web Console.
• Character strings that can be monitored by the condition expression of the alarm definition consist of a maximum of 511 bytes that can be stored in the Logged Messages (PL_MESS) record. Because character strings stored in the Logged Messages (PL_MESS) record include header information such as the identifier (id), the length of messages that can be monitored is shorter than the 511 bytes for the header information portion.
• To monitor a character string of 512 bytes or more, use the event file setting of PFM - Agent for Platform to set the character string you wish to monitor as a filter condition. At this time, set an identifier (id) for the message as well. By setting this identifier (id) in the condition expression of the alarm definition, you can monitor messages that include the character string set as the filter condition.
  For example, if you want to monitor messages that include character string ABC, use the event file of PFM - Agent for Platform to set Console for the identifier (id) and set ABC for the filter condition:
  

  logfile=/tmp/console_log
  id=Console
  regexp=ABC

  After that, in the New Alarm Table > Alarm Conditions window of PFM - Web Console, set Console as the error value or warning threshold value.
  This setting sets the identifier (id) Console as the header information for messages that include the character string ABC. PFM - Web Console issues an alarm when a message occurs that includes the Console character string.