[GitHub] [streampipes] heinehenning added a comment to the discussion: Include SparkplugB Adapter and DataSink

[GitBox <gi...@apache.org>]

GitHub user heinehenning added a comment to the discussion: Include SparkplugB Adapter and DataSink

Hi @tenthe!

I am not 100% sure if your last question was directed at me or at @bossenti.
From a user perspective I would say that for the part of reading/receiving SpB StreamPipe offers all the tools necessary. You could map SpB metrics in a similar fashion as JSON payloads during the definition of the connector.
For the transformation of data into SpB we need to define at least the following things at one place or another:
- GroupId
- NodeId
- DeviceId
- MetricName
The easiest  option would be to pack all that stuff into a MQTT-SpB-DataSink and define them together with the rest of the MQTT connection. If a metric should contain more than just one value some kind of mapping needs to happen between DataSource and the Metric.
The approach from node-red-contrib-mqtt-sparkplug-plus is not to bad. 
It gives some help defining the metric. But it still requires the user to put together the payload by hand. As a user it would be nice to have an option to connect DataSource(s) and one SpB-DataSink. Inside the DataSink I would like to be able to select certain values from the sources and map them to the metrics kind of like in the below screenshot from the mqtt-sparkplug-device of node-red-contrib-mqtt-sparkplug-plus.

![image](https://user-images.githubusercontent.com/132096802/235764443-3b50e2fa-f49c-4d47-9dd0-dea946d2ef28.png)






GitHub link: https://github.com/apache/streampipes/discussions/1531#discussioncomment-5784609

----
This is an automatically sent email for dev@streampipes.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@streampipes.apache.org