Skip to content

Propose the addition of FollowsFrom semantics #161

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
erikerikson wants to merge 1 commit into from
Closed

Propose the addition of FollowsFrom semantics #161

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -310,6 +310,19 @@ that contains both context and data).
* MUST be a non-empty string
* MUST be unique within the scope of the producer

### followsFrom
* Type: String
* Description: The eventID of the event that caused this event. The semantics
Copy link
Copy Markdown
Member Author

@erikerikson erikerikson Apr 13, 2018

Choose a reason for hiding this comment

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

one could argue that a set of eventID(s) could be the cause of an event and that this field should allow for this. allowing delimited eventID(s) to be supplied could satisfy that fact at the cost of complexity

of this string are explicitly undefined to ease the implementation of
producers. Enables correlation. The semantics of the relationship between
the event identified by followsFrom and the event identified by eventID are
as defined by the (Open Tracing Standard](https://github.com/opentracing/specification/blob/1be76512597d0e0388de06702f3c8a9e7b554064/specification.md#references-between-spans)
* Examples:
* A database commit ID
* Constraints:
* OPTIONAL
* If present, MUST adhere to ALL constraints of eventID.

### eventTime
* Type: Timestamp per [RFC 3339](https://tools.ietf.org/html/rfc3339)
* Description: Timestamp of when the event happened.
Expand Down