dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update alert 

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
This commit is contained in:
Hannah Hunter 2023-06-28 18:05:55 -04:00
parent e24313c2f1
commit fed1396c76
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-cloudevents.md
View File

@ -66,6 +66,12 @@ As another example of a v1.0 CloudEvent, the following shows data as XML content
} }
``` ```
{{% alert title="Important" color="warning" %}}
While you can specify `traceid`/`traceparent` and `tracestate` in the metadata request, it's recommended to use Open Telementry and Zipkin protocols for distributed traces. [Learn more about distributed tracing.]({{< ref "tracing-overview.md" >}})
{{% /alert %}}
### Override CloudEvent values ### Override CloudEvent values
When not provided, Dapr automatically generates several CloudEvent properties. You can override these generated CloudEvent properties by providing the following optional metadata keys: When not provided, Dapr automatically generates several CloudEvent properties. You can override these generated CloudEvent properties by providing the following optional metadata keys:
@ -90,15 +96,11 @@ For example, to override the applicable values from [the first CloudEvent exampl
"cloudevent-source": "checkout", "cloudevent-source": "checkout",
"cloudevent-type": "com.dapr.event.sent", "cloudevent-type": "com.dapr.event.sent",
"time": "2020-09-23T06:23:21Z", "time": "2020-09-23T06:23:21Z",
"cloudevent-traceparent": "00-113ad9c4e42b27583ae98ba698d54255-e3743e35ff56f219-01"
} }
``` ```
{{% alert title="Important" color="warning" %}} {{% alert title="Important" color="warning" %}}
While you can override `traceid` and `tracestate`, this is not the recommended way to specify trace ID or trace state. The following fields should be specified in the publish metadata request, not the JSON payload: While you can specify and then override `traceid`/`traceparent` and `tracestate`, doing this may interfere with tracing tools. It's recommended to use Open Telementry and Zipkin protocols for distributed traces. [Learn more about distributed tracing.]({{< ref tracing-overview.md >}})
- `cloudevent-id`
- `cloudevent-traceid`
- `cloudevent-tracestate`
{{% /alert %}} {{% /alert %}}