Summary
New alarm module export alerts from secondaryValidation logging to server in JSON format. Once
Since 2024.01. Backported to RWS2022.02, RWS2023.02
Overview
The approach of exporting alerts to the new RWS alarmmodule consists of three steps:
- Configuring a loggingTimeSeries in the secondaryValidation tasks so the alerts are not only logged, but also stored in a dedicated loggingTimeSeries.
- Schedule a task to serialize entries in the loggingTimeSeries that aren't flagged as exported yet.
- Configure a flagSourceColumn and a customFlagSource in the general export where exported alarms can be marked as exported.
Config examples
<?xml version="1.0" encoding="UTF-8"?> <timeSeriesExportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesExportRun.xsd"> <export> <general> <exportType>IQM</exportType> <serverUrl>https://alarmmodule.rws.nl/api/v1/event</serverUrl> <user>apiuser.rwsos.iwp</user> <password>O$sjv5bd%R.?</password> <exportTimeZone> <timeZoneOffset>+00:00</timeZoneOffset> </exportTimeZone> <flagSourceColumnFilter>exported</flagSourceColumnFilter> <exportedFlagSource>verzonden</exportedFlagSource> <exclusiveFlagSourceColumn>false</exclusiveFlagSourceColumn> </general> <properties> <string value="RWsOS.IWP" key="source"/> <string value="RWsOS.IWP" key="deviceCode"/> </properties> <timeSeriesSet> <moduleInstanceId>$MODULE_INSTANCE_ID$</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Comment</parameterId> <locationId>dummy</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="nonequidistant"/> <relativeViewPeriod startOverrulable="true" endOverrulable="false" unit="minute" start="-1440" end="1"/> <readWriteMode>add originals</readWriteMode> </timeSeriesSet> </export> </timeSeriesExportRun>