Solutions
...
Litmus Production Record Datab...
Litmus Companion Solutions for...
Litmus Production Record Tag Message Conversion Flow
3min
overview litmus production record database allows to record both process and meta data from tags these data can be used for event monitoring and event data recording as shown in the use cases maintenance event tracking docid\ tkqwptytkim7iiwd0is7d unplanned downtime event tracking docid\ jtpmplnnuh qpvz q0ual but they can also be use for visualization similar to a timeseries database or for spc analytics as shown in the chapter reading tag data for spc with utc timestame docid\ vpq661rrc7rwz4n5c3a2z to be able to process the raw tag data send to litmus production record database, a specific set of data has to be send to litmus production record database to learn more about this process, review the chapter inserting single tag item if not using litmus edge integration docid 1 gzvwqc0lnoi0nvbjtfq for sending a single value or inserting multiple tag items if not using litmus edge integration docid\ w3hrwgmi eevia bjz af for sending a batch of values if a the user has deployed litmus edge, the recommended approach is to make use of litmus flows for creating the right payload before using litmus integrations to allow users to not have to spend time developing such a flow, litmus offers the solution litmus production record tag message conversion flow the flow can process different tags from different devicehub devices if a tag has been defined to have multiple items in litmus production record database, as discussed in the chapter core concept behind recording process and meta data for process tags docid\ amceahd6bo48cyboguikw the main part of the flow is the included sub flow which can be duplicated and used in conjunction with other code to create the right message for the right item with the right value this allows to not just send data collected by devicehub, but also data generated through a flow, analytics or a custom application to litmus production record database after having purchased the solution from the litmus central portal solutions catalogue , the user will have the file name litmus production record tag message conversion 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 deployment guide litmus production record tag message conversion flow docid\ wypb0hpgal8f4txrf54pf