-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create tag property / field on Event #270
Labels
2-medium
priority denoting issues with cross-cutting project impact
enhancement
New feature or request
hanoi
Hanoi release
Comments
jpwhitemn
added
2-medium
priority denoting issues with cross-cutting project impact
enhancement
New feature or request
hanoi
Hanoi release
labels
Aug 20, 2020
Is a single tag a simple string like |
Also, if this is for Hanoi, then it applies to both V1 models and V2 DTOs/models, correct? |
Yes on V1 and V2 question. |
lenny-goodell
referenced
this issue
in lenny-goodell/go-mod-core-contracts
Aug 21, 2020
closes #270 Signed-off-by: lenny <[email protected]>
13 tasks
13 tasks
lenny-goodell
referenced
this issue
in lenny-goodell/go-mod-core-contracts
Aug 31, 2020
closes #270 Signed-off-by: lenny <[email protected]>
lenny-goodell
referenced
this issue
in lenny-goodell/go-mod-core-contracts
Aug 31, 2020
closes #270 Signed-off-by: lenny <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2-medium
priority denoting issues with cross-cutting project impact
enhancement
New feature or request
hanoi
Hanoi release
Per the architect's meeting of July 20th and Core WG meeting of 8/20/20, it was decided that EdgeX should provide the means to attribute all event/readings to a gateway, host platform or originating EdgeX instance. Therefore, each Event object should have a "tags" field (and array of strings) that allow for the platform to place identifying information into the tags field that help attribute the event/reading(s) to the host.
How and when the EdgeX instance places platform identifying information in "tags" is still being worked out. For the initial implementation, the application services will offer an optional enrichment function that will use configuration data to populate the tags field of the event before is exported out of EdgeX.
See these documents for more details:
The text was updated successfully, but these errors were encountered: