Skip to content

Introduce source-labels to help IoT cases. #138

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.

Sign up for GitHub

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

Closed
inlined wants to merge 3 commits into from
Closed

Introduce source-labels to help IoT cases. #138

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7ca1b56
Introduce source-labels to help IoT cases.
inlined Apr 2, 2018
937cbff
Avoid using keyword
inlined Apr 25, 2018
3e34a41
* Rename sourceLabels to labels.
inlined May 9, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -328,6 +328,25 @@ that contains both context and data).
* Constraints:
* REQUIRED

### labels
* Type: `Map`
* Description: Non-heirarchical attributes which describe the `source` of
Copy link
Copy Markdown
Collaborator

@duglin duglin May 17, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have to limit it to describing the source instead of the event in general?

the event. Receivers can filter or route based on these attributes.
This is intended to include (but is not limited to) "labels" in cloud
platforms like AWS or Kubernetes.
* Constraints:
* OPTIONAL.
* Keys MUST match the regular expression `[_a-z0-9][_.a-z0-9/]*`
* Keys SHOULD use the character "." as a namespace separator
* Values MUST be `String`s
* Values MUST use URI-safe characters
* Values MUST be non-zero in length
* Examples:
* {
"sensor.configuration": "WINDOW",
"sensor.location": "deployments/house1/window3"
}

### eventID
* Type: `String`
* Description: ID of the event. The semantics of this string are explicitly
Expand Down