Signaling the Data Source that has a problem

[Limraj]

Expected Behavior
If the Data Source is having script executing/connections problems, this should be visible to the user in watchlists and graphical views.

To reproduce

1. Login as admin;
2. Create Virtual Data Source as virtual_ds (enabled, update: 1s) and Virtual Data Point as virtual_dp_1 (enabled, numeric, random, min:0, max:123, start value:0) and virtual_dp_2 (enabled, settable, binary, no change, start value:0)
3. Create Meta Data Source as meta_ds (enabled) and Meta Data Point as meta_dp (enabled, numeric) Added to context:
   p1 - 'virtual_ds - virtual_dp_1';
   p2 - 'virtual_ds - virtual_dp_2';
   and set script:
   if(p2.value) return p1.value; return -1;
4. Added to watchlist as wl_1, add added points:
   a) 'meta_ds - meta_dp';
   b) 'virtual_ds - virtual_dp_1';
   c) 'virtual_ds - virtual_dp_2';
5. Disabled virtual_ds;
6. meta_dp does not change and does not indicate a problem -> ERROR 1;
7. Enabled virtaul ds -> meta_ds meta_dp value changes as expected;
8. Deleted 'virtual_ds - virtual_dp_1' -> identical behavior as in step 7, meta_dp does not indicate a problem -> ERROR 2;

Test procedure:

1. Case from issue to check, you can check it first on the old code;

2. You import a new configuration and check how it works, if you disable some virtual data point, or sql data point, or all of them, are you able to find out from the alarms that these meta data points do not work because you have disabled points in their context and specifically which points are in question, which specific points are causing the problem;
   Sign (2).zip

3. You configure your own structure, let it be for these 2 nestings and repeat the tests;

4. You create a simple cyclic configuration meta_1 -> meta_2 > meta_1, and meta_1 -> meta_2 -> meta_3 -> meta_1

5. You create as many of these Data Sources with points as possible and check if there is no generation of multiple events;

To do
It is worth adding such signaling at least in:

• Meta Data Source
• Modbus IP
• SNMP
• HTTP Retriever
• SQL
• MQTT
• Internal Data Source
• Virtual Data Source
• JMX
• Modbus Serial
• 1-wire
• BACnet I/P
• DNP3 IP
• DNP3 Serial
• AMQP
• ASCII File Reader
• ASCII Serial
• Dr.Storage HT-5B
• Galil DMC-21x2
• HTTP Image
• HTTP Receiver
• IEC101 Ethernet
• IEC101 Serial
• M Bus
• Mitsubishi Alpha2
• NMEA listener
• OPC DA
• OpenV4J
• Pachube
• POP3 Email
• Serotonin Persistent TCP
• VMStat Data Source

You can follow the solution included in Data Source MQTT/AMQP;

Specifications
Scada-LTS Version: 2.6.18

Linked:
#1745