Add global ID for events

[xibz]

As discussed last week, a global ID is needed to ensure quick and efficient look ups for a series of events.

This new global ID would be a requirement for the links spec #10 as this would eliminate the need for links to backtrack to figure out how a series of events occurred, and instead, a simple query of the global ID would return all events associated with that global ID. Further this would give a logical grouping to the events that occurred for a particular job.

I propose the name span id and further I imagine the SDKs would need to change a little bit. I would imagine if no span ID is present, simply create one, and that would then be passed to all children events. I haven't spent too much time on thinking about this, but is that all that is needed to determine a span of events?

I'll spend some more time thinking about this, and see if I am able to get a proposal out.

[afrittoli]

Thank you @xibz for bringing this up.

[e-backmark-ericsson]

There is a "Distributed Tracing" extension to Cloudevents, that is intended to handle global IDs like the one requested here. If we promote that we will be more tightly coupled with and dependent on Cloudevents, which we might not want to be.

One idea could be that the CDEvents spec don't mention this at all, but that the SDKs (which build on Cloudevents SDKs?) could provide that.

https://github.com/cloudevents/spec/blob/main/cloudevents/extensions/distributed-tracing.md#distributed-tracing-extension

[afrittoli]

#104

[afrittoli]

Related PR: #139

[afrittoli]

@xibz since #139 is merged now, can we close this issue?

[xibz]

closed via #139