Configure alarms for system objects

To enable alarming for your application, you need to configure your Galaxy’s WinPlatform and AppEngine objects as alarm providers. Both system objects report their own alarms.

Client applications subscribe to application object alarms by the area containing the objects. Client applications can also subscribe to WinPlatforms and AppEngines directly. These are called "pseudo-areas." They do not need to be assigned to an area for a client to see the alarms, although the user may want to assign them to an area, such as for simplifying the alarm query in the InTouch Alarm Viewer or Alarm DB Logger.

The following list shows the alarms for each system object.

• WinPlatform

  • Excess CPU load alarm

  • Low disk space alarm

  • Excessive page faults alarm

  • Low memory alarm

  • Engine failure alarm

  • Engine checkpoint failure alarm

  • Object quarantined condition

  • Subscription folding condition

  • Scheduler scan overrun condition

    A WinPlatform object includes a general communication alarm when it loses contact with the areas to which it is subscribed.

• AppEngine

  • Checkpoint failure alarm

  • Object quarantined condition

  • Subscription folding condition

  • Scheduler scan overrun condition

  • Redundancy failover alarm

  • Redundancy Standby unavailable

  • Redundancy Standby not ready

• ViewEngine

  • Checkpoint failure alarm

  • Object quarantined condition

  • Subscription folding condition

  • Scheduler scan overrun condition

WebViewEngine, Area and InTouchViewApp system objects do not include any alarms.