Solutions
...
Litmus Companion Solutions for...
Litmus Production Record Inter...

Creating an event monitoring configuration using the Litmus Production Record Internal Event Configurator

7min

The solution Litmus Production Record Internal Event Configurator is designed to provide a guided experience to assist the user with where to start and where to go.

The sheet Instructions provides a basic workflow, showing which sheets to go first and how to progress.

Document image


It also does provide a link to this documentation.

Document image


To be able to work, it is required that both the data model for which events are to be monitored as well as the tags which are to be used have both been created in Litmus Production Record Database. It is recommended to do define them first, as the configurator will be able to retrieve them to assist with the configuration. This requirement is also stated in the sheet Instructions.

Document image


Factory Reset the Configurator

Users can factory reset the Configurator tool, for example if you want to create a new event configuration on a different SQL-Server, with the Reset Configurator button in the sheet Instructions.

Document image


Reset an individual sheet

Most sheets have a dedicated Clear Sheet button

Document image


In Tool guides and help

The sheets Event_and_Trigger_Definition

Document image


and Event_Item_Definition

Document image


both have a section designed to provide in-sheet assistance.

Help Button

Most sheets provide a help ? button in the right upper corner of the sheet.

Document image


This button opens a help window with three tabs.

Document image


The first tab gives a high level How to guide

Document image


Restrictions on ASCII characters allowed to be used

The second tab shows which Characters are allowed (green) and not allowed (red) when setting up a Event name, Node name, Level name, Device name, Tag name or Item name

Document image


This is necessary, as certain ASCII characters can cause the Transact-SQL used by the Litmus Production Record Database to not work correctly, especially when retrieving data.

The third tab shows which Characters are allowed (green) and not allowed (red) for descriptions.

Document image


This is necessary, as certain ASCII characters can cause the Transact-SQL used by the Litmus Production Record Database to not work correctly. Further are some characters used by applications which use topics such as MQTT or NATS for example as wildcards.