Open Chriscbr opened 1 year ago
@skyrpex and I discussed this a little bit offline, what we came up with was something like this:
id
(always unique), a parentId
(reference to another trace that "caused" the current trace), and a traceId
(reference to the first trace in the current sequence of correlated events)traceId
field@skyrpex let me know if I missed anything.
It looks good to me, except that what you call traces I call it events. So, the SDK logs events which have an ID, a parent ID, and a trace ID. A trace is a group of events (can be in the shape of a tree).
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
_Originally posted by @skyrpex in https://github.com/winglang/wing/issues/918