Litmus Edge Announces Change of Value KPI, Saving Critical Network Bandwidth and Costs

Over the past year, the Litmus team focused on introducing features that mattered the most to our customers. The Change of Value KPI in the Analytics pane of the platform is one such capability, and an important one. This KPI is a significant milestone in helping Litmus Edge users stay on top of real-time alerts while saving critical bandwidth in northbound communication. The feature enables users to publish the entire message payload only when there is a change of value in the tag or process flow parameter.

The Change of Value KPI is designed to provide more flexibility to users. Apart from choosing which flow parameter to monitor, users can also specify the tolerance limit for a parameter and a preset time interval, if needed.

When creating an analytics flow, review the Processor Flow Parameters.

You need the following information to use this KPI:

• In the Map Field Name, specify the field you want to observe for Change of Value. This can be value or asset_online depending on the input message. The most commonly used is value, but you can also use success, deviceID, downtime, or something else.

• Enter a delta to ignore minor precision errors.

• The timer interval parameter is useful if the connected input tag is currently not polling, but you still want this KPI to publish a value every few seconds, defined by the timer. If you know your input is going to publish at the expected interval, we recommend you to disable this timer by entering 0 in the field.

• There is no Expected Output if the current value matches the previous or is within the specified range of the delta. In case there is a significant change that exceeds the delta, the entire message payload is displayed.

Learn more about the Change of Value KPI.

Book a demo or get started for free today.