AgeWatchdog table
- Last UpdatedApr 24, 2025
- 2 minute read
The ageWatchdog table is used to configure records for the Age Watchdog application, which monitors specified telemetered points within an Omnicomm process.
The ageWatchdog table allows you to select one telemetered point per record in the Monitored point field. The timestamp of this point will be checked according to a Sampling Interval. When checked, the difference between the point's timestamp and the current time is compared to a Time Qualifier span. If the difference is greater than the Time Qualifier, the point will be considered suspect.
If Demand Poll has been enabled for the ageWatchdog record, a demand poll is issued to the associated remote. The Monitored point will then be checked every minute to determine if the demand poll resulted in an update to the point's timestamp.
If the timestamp of the Monitored point has not changed once the Demand Poll Timeout has expired, the Age Watchdog application will respond according to alarm and event configuration for the point. The Age Watchdog application will then continue to check the Monitored point's timestamp every minute. If the timestamp has been updated, the Omnicomm process and remotes are clearly working, so the Age Watchdog application will perform Return-To-Normal processing.
Note: The timestamp of the configured point is checked every minute by default, if the Sampling Interval is set to 0. As a result, the remote of the monitored point and the point itself will be staled every minute if the Time Qualifier span is also left at 0.
Each record in the ageWatchdog table also maintains a persistent state, which indicates the data quality of the monitored point. The records can have one of the following states: disabled, fresh data, suspect data, or stale data. The message set that corresponds to these states is called ageWatchdog.
-
Disabled indicates that the ageWatchdog record is disabled due to manual intervention or a configuration error.
-
Fresh Data indicates that the Age Watchdog application finds no problems after checking the timestamp of the monitored point.
-
Suspect Data indicates that the Age Watchdog application considers the Monitored point to be potentially invalid, and has issued a demand poll to trigger an update to the point's timestamp.
-
Stale Data indicates that the Age Watchdog application has staled the monitored point after its record has been declared old.
Notes: The state of ageWatchdog records is preserved whenever the RealTime service is restarted. It is also replicated across systems for seamless operation of long sampling intervals across system restarts and mode switches.
Any discrepancies that occur between the ageWatchdog records enabled, flag.cmsg, and state fields will be corrected the next time the Age Watchdog application processes the monitored points.