From aa987d111914b0a654c3745b3bcbcb6cf55a7f00 Mon Sep 17 00:00:00 2001 From: Jan Klasser <52920852+JanKlasser3000@users.noreply.github.com> Date: Wed, 6 Sep 2023 16:26:17 +0200 Subject: [PATCH] chore(docs): update cloudevents comparison (#55) --- dev-context/async/comparison-cef-cloudevents.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-context/async/comparison-cef-cloudevents.md b/dev-context/async/comparison-cef-cloudevents.md index 1548e559..16078a3f 100644 --- a/dev-context/async/comparison-cef-cloudevents.md +++ b/dev-context/async/comparison-cef-cloudevents.md @@ -34,7 +34,7 @@ Currently, most events are encoded using CEF. Therefore, this article focuses on | type and version | [type](https://api.otto.de/portal/guidelines/r200009) | yes | Type must follow name schema defined in our guideline [MUST follow naming scheme for type context attribute](https://api.otto.de/portal/guidelines/r200009). Version must be part of the type within OTTO. | | context and sequenceKey | part of [source](https://api.otto.de/portal/guidelines/r200010) | yes | source may contain more context information such as the event source. If a sequenceKey exists in CEF, it should be included in the `source` context attribute. See "sequenceNumber" for more information on how to convert the sequence attributes to CloudEvents. | | eventTime | [time](https://api.otto.de/portal/guidelines/r200011) | yes | | -| traceId and spanId | [traceparent](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/extensions/distributed-tracing.md#traceparent) | yes | trace_parent is defined in the [distributed tracing](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/extensions/distributed-tracing.md) extension. Follows the W3C trace context specification. The trace_parent context attribute contains the traceId as [trace-id segment](https://www.w3.org/TR/trace-context/#trace-id) and the spanId as [parent-id segment](https://www.w3.org/TR/trace-context/#parent-id). TL;DR `traceparent`= `00---00` | +| traceId and spanId | [traceparent](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/extensions/distributed-tracing.md#traceparent) | yes | trace_parent is defined in the [distributed tracing](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/extensions/distributed-tracing.md) extension. Follows the W3C trace context specification. The trace_parent context attribute contains the traceId as [trace-id segment](https://www.w3.org/TR/trace-context/#trace-id) and the spanId as [parent-id segment](https://www.w3.org/TR/trace-context/#parent-id). TL;DR `traceparent`= `00---00`. spanId must be set(value different than only 0). In cloud events trace_parent for now is optional. | | sequenceNumber | [sequence](https://api.otto.de/portal/guidelines/r200003) | yes | sequence just contains a string. The semantics of this string is either defined by an out-of-band communication or by an additional [sequencetype](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/extensions/sequence.md#sequencetype) context attribute. The predefined [Integer](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/extensions/sequence.md#integer) sequencetype defines the same semantics as `sequenceNumber` in CEF if the `source` context attribute contains the `sequenceKey`. | | test | n/a | yes | not defined within the CloudEvents spec, may be added by Otto with a custom extension. | | `{"data": {...} }` | `{ ... }` | yes | The "`data`" node is obsolete with CloudEvents. The payload starts at the beginning. |