Litmus Production Record Event Processing Flow

overview litmus production record database allows for two ways of monitoring production event triggers and recording the respective production record data as shown in the use cases maintenance event tracking docid\ tkqwptytkim7iiwd0is7d unplanned downtime event tracking docid\ jtpmplnnuh qpvz q0ual the first option is to make use of the option to define single trigger based event monitoring inside litmus production record database itself where raw process data for tags are send to litmus production record database and used both for trigger monitoring as well as providing the data for the production event record if triggers require the monitoring of more than one tag and/or the trigger is also used for additional task not related to litmus production record database, the event monitoring has to be done outside of litmus production record database such as litmus flows an example for this is described by the use case production event tracking docid 8llhzd6hncgtoxfyy t1e if a the user has deployed litmus edge, the recommended approach is to make use of litmus flows for the event monitoring to allow users to not have to spend time developing such a flow, litmus offers the solution litmus production record event processing flow the biggest advantage of this flow is, that it scales very well allowing to monitor the same event for different devices as it tracks events based on the name of a devicehub device therefore, if several devices have the same tags holding the same information, they all can be processed by the same flow after having purchased the solution from the litmus central portal solutions catalogue , the user will have the file name litmus production record event processing v1 0 0 json this file can then be imported to a litmus edge flows instance after successfully importing and deploying the flow into the litmus flows instance, the user is ready to take the next step configuring the litmus production record event processing flow docid\ ai7zqnxxn58fpoo7lhohe