Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • category - If you have configured any Event Categories, you can select to only generate notifications for System events with the selected categories. See 4.4 Event Category for further information about Event Categories.

  • contents - The contents field contains a hard coded string with event specific information. If you want to use this field for filtering you can enter a part of the contents as a hard coded string, e g the state you are interested in Idle/Running/Stopping/etc. However, for System events, the content consists of the text "System message:" and then the system message itself, see the description of the system message above.

  • eventName - This field can be used to specify which event types you want to generate notifications for. This may be useful if the selected event type is a parent to other event types. However, since the System event is not a parent to any other event, this field will typically not be used for this event.

  • origin - If you only want to generate notifications for events that are issued from certain Execution Contexts, you can specify the IP addresses of these Execution Contexts in this field.

  • receiveTimeStamp - This field contains the date and time for when the event was inserted into the Platform database. If you want to use timeStamp for filtering, it may be a good idea to enter a regular expression, for example, "2012-04.*" for catching all System events from 1st of April, 2012, to 30th of April, 2012.

  • severity - With this field you can determine to only generate notifications for state changes with a certain severity; Information, Warning, Error or Disaster. This may be useful to filter on if you only want to view System events that generate Warnings for example.

  • timeStamp This field contains the date and time for when the Execution Context generated the event. If you want to use timeStamp for filtering, it may be a good idea to enter a regular expression, for example, "2012-06-15 09:.*" for catching all System events from 9:00 to 9:59 on the 15th of June, 2012.

Note
titleNote!

The values of these fields may also be included in the notifications according to your configurations in the Notifier Setup tab.

Examples of System Event Configuration

Info
titleExample - System Event sent to Log File



This configuration will give you the following notification setup:

  • When a System event occurs, a System Event notification will be generated.

  • When this notification is generated a new log line will be added in the systemevent.txt file located in the /home/MyDirectory/systemevent/ directory, with the following data:

    • The timestamp for when the System Event was registered.

    • The System Event message.

...

Info
titleExample - System Event sent to Mail



This configuration will give you the following notification setup:

  • When a System Event with a message containing the text "Warning" is registered, a System Event notification will be generated.

  • When this notification is generated a mail will be sent to the my.mail@mycompany.com e-mail address with the following data:

    • The subject will say: "System Event".

    • The message will contain the following text: The following warning has been detected: <the system event message>.


Scroll ignore
scroll-viewportfalse
scroll-pdftrue
scroll-officefalse
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmlfalse


Next: