You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The CloudPublisher can be configured to put into the KuraMessage body one of the properties received.
When this happens, the original property is left in the properties, which all end up in the list of metrics in the KuraMessage.
This leads to possible duplication of data. If a user wants to publish something in the body of the message, he probably also wants to remove that property from the metrics.
To Reproduce
Steps to reproduce the behavior:
Create a WireGraph with some string metric (Timer -> JavascriptFilter -> Publisher)
Configure the JavascriptFilter to create a "payload" Stirng metric in output
Configure the CloudPublisher to put the "payload" metric into the MQTT message body
Verify how the Publisher will publish both a "payload" metric in the metrics, and the content of "payload" in the body
Expected behavior
If the CloudPublisher is configured with a non-empty value in the "set.body.from.property" property, the property should not be included in the metrics of the resulting KuraMessage
Target Environment (please complete the following information):
Board: ANY
OS version: ANY
The text was updated successfully, but these errors were encountered:
Describe the bug
The CloudPublisher can be configured to put into the KuraMessage body one of the properties received.
When this happens, the original property is left in the properties, which all end up in the list of metrics in the KuraMessage.
This leads to possible duplication of data. If a user wants to publish something in the body of the message, he probably also wants to remove that property from the metrics.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If the CloudPublisher is configured with a non-empty value in the "set.body.from.property" property, the property should not be included in the metrics of the resulting KuraMessage
Target Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: