Solutions
...
Litmus Companion Solutions for...
Litmus Production Record Event...
Monitoring Litmus Production Record Event Processing Flow
4min
the solution litmus production record event processing flow comes with an integration webui for monitoring and error logging it can be accessed using the node red webui button the first screen show a summary of all involved components a green dot, indicates that no issues have been found, while a yellow dot will indicate a missing configuration a red indicator shows that either the configuration provided has an error this is an example where no configuration is processed by the flow the last row of the summary table is used to monitor if the flow itself is operational if the dot is green all node red nodes operate as expected if the dot is red, one or more of the nodes have thrown an error, which might also be shown in the debug window the detailed event config monitor gives a breakdown of which tag of which device has been identified as valid to be processed the detailed identifier processing monitor gives a breakdown of which tag of which device have been identified as identifier and what there current status is to learn more about identifiers, you can review the chapter how are data for a production record data model stored docid\ n26ytjyqxp15wxwtqi j the detailed item processing monitor gives a breakdown of which tag of which device has been identified as items and are processed the detailed trigger processing monitor gives a breakdown of which triggers are monitored and when they have last been executed (time of trigger last true) and data been published (time of gate last open) the status of yellow indicates that the trigger is currently not true, while the color blue indicates that the trigger is true but the gate is not yet open as it still waits for all data to be available if the status is green, the trigger is true and the gate is open the detailed gate processing monitor shows the last data which have been published on which topic if a new value for a topic is published, it will overwrite the row the error log shows the last 20 errors thrown by the flow