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
Based on edgexfoundry/go-mod-core-contracts#767
Device, device resource, and device command now have the Tags map[string]interface{} field that allows users to provide additional information. device-sdk should add these tags to reading/event.
Describe the solution you'd like
Before sending out an event, do the following:
Add device resource tags in reading level
Add device command tags in event level
Add device tags in event level
The device tags should take precedence over the device command tags if the tag name is the same.
Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?
The text was updated successfully, but these errors were encountered:
What's the "Why?" here? Why put the tags in every Event, when they are available in metadata?
Event size is always a concern, though the contribution from Tags appears to be small.
@TomBrennan-Eaton the tags will be only if they are defined in Profile or Device. Their default value is empty, so this won't increase any size for the normal usage.
We found some users need the additional information in Event or Reading.
For example, the users might want the sunspec mapping information in the readings. https://sunspec.org/
When the data is sent out to the northbound, they might not be able to access core-metadata from the edge side.
🚀 Feature Request
Relevant Package [REQUIRED]
device-sdkDescription [REQUIRED]
Based on edgexfoundry/go-mod-core-contracts#767
Device, device resource, and device command now have the
Tags map[string]interface{}
field that allows users to provide additional information. device-sdk should add these tags to reading/event.Describe the solution you'd like
Before sending out an event, do the following:
The device tags should take precedence over the device command tags if the tag name is the same.
Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?The text was updated successfully, but these errors were encountered: