Live Data Lapse

The EQuIS Live Data Lapse Agent will monitor data coming in via EQuIS Live and notify the user if no new data has arrived within the expected period of time.

Monitoring Data

The Data Lapse Agent can be run as a scheduled EQuIS Information Agent (EIA), at the desired frequency, to automatically monitor series as often as needed. If a series has no datum with a DATUM_UTC_DT greater than the last time the EIA was run, then a notification will be generated for that series. The last time the EIA was run is the report's maximum ST_TASK.COMPLETED_DATE.

To better illustrate this point, the following SQL statement joins the ST_TASK (TASK_ID) with the report name (and user report name) and will show the report names with the dates (and times) it was run. This, along with the series datum will tell the user if there is a lapse in the data.

SELECT r.report_name,

ur.name AS 'user report name',

t.completed_date

FROM st_task t

INNER JOIN st_report_task rt ON rt.task_id = t.task_id

INNER JOIN st_report_event re ON re.report_event_id = rt.report_event_id

INNER JOIN st_user_report ur ON ur.user_report_id = re.user_report_id

INNER JOIN st_report r ON r.report_id = ur.report_id

WHERE r.report_name LIKE '%Lapse%'

ORDER BY t.completed_date DESC;

Therefore, the EIA frequency should be scheduled based on the frequency that the data is being reported.

The Data Lapse Agent can also be run in EQuIS Professional or Enterprise (using the EZView widget) to monitor series manually, without having to schedule an EIA. The report results will show series that have no datum with a DATUM_UTC_DT greater than the time that the agent runs minus twice the maximum DT_LOGGER.TRANSMIT_PERIOD_S of the selected series (or twice the Workflow Sleep Seconds, if it is greater).

Notes:

•The data lapse time is different for EIA than it is for non-EIA. For EIA, it is the last time the EIA was run, while for non-EIA, it is the time that the agent runs minus twice the maximum DT_LOGGER.TRANSMIT_PERIOD_S of the selected series (or twice the Workflow Sleep Seconds, if it is greater).

•The RECORD_COUNT column values will be 0 for all series in the notification, or report results, if a data lapse is present. If there is no lapsed data, there will not be a notification or report results.

•The Data Lapse Agent report output includes DT_FACILITY.FACILITY_CODE for the logger, or logger series (if available). The FACILITY_CODE report output will only be available for users with permissions to view each individual facility included in the report.

The report has the following input parameters:

•Monitor these series – Shows a list of series that can be selected to monitor. Series will only be visible if the DT_LOGGER.TRANSMIT_PERIOD_S field is populated (i.e., not null). The DT_LOGGER.TRANSMIT_PERIOD_S field is the number of seconds that elapse between data collection events for this data logger.

•Notification defeat interval (for EIA use only) – Defines the length of time, in minutes, following a notification being sent out, during which there will be no (further) notifications sent out. The EIA will still run, as scheduled, but notifications will not be sent out during this time. A value of 0 always sends out a notification (if there's a data lapse). The date and time that the last notification was sent out is saved in the user report's @last_notification (hidden) parameter (in the ST_USER_REPORT_PARAMETER table).