...
The configuration contains definitions of one or more time series that can be used as input for checks. Each timeSeries contains a timeSeriesId and a timeSeriesSet. The timeSeriesId can be used to reference this the time series in a check. Alternatively time series definitions can be embedded in the checks.
...
The minNumberOfValuesCheck, minNonMissingValuesCheck, minReliableOrDoubtfulValuesCheck and minReliableValuesCheck all consist of the following elements.
- timeSeries: One or more items that describe the data time series that need to be checked. If the specified data This can be either an embedded time series or a reference to a time series defined at the start of the configuration file. If this contains multiple time series (e.g. for multiple locations), then each time series is checked individually.
- checkRelativePeriod: The check will only consider data in this time period. This time period is relative to the timeZero of the taskrun in which this the module instance runs. The start and end of the period are included. This period overrules any relativeViewPeriods specified in the timeSeriesSets of the time series.
- minNumberOfValues: The minimum required number of values in the time series to pass the check.
- logLevel: Log level for the log message that is logged if a time series does not pass this the check. If level is error or fatal, then the module will stop running after logging the first log message.
- logEventCode: Event code for the log message that is logged if a time series does not pass this the check. This event code has to contain a dot, e.g. "TimeSeries.Check", because the log message is only visible to the master controller if the event code contains a dot.
- logMessage: Log message that is logged if a time series does not pass this the check. It is possible to use the tag %HEADER% in the logMessage. The %HEADER% tag will be replaced with the header of the time series.
...