[SVLS-7298] Add support for merging upstream traces with Step Function#31180
[SVLS-7298] Add support for merging upstream traces with Step Function#31180
Conversation
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
janine-c
left a comment
There was a problem hiding this comment.
Looks great, Ryan! I made some really minor suggestions, but none of them are dealbreakers by any means. Don't hesitate to ping me if you have any questions!
| For services not covered in this guide, you can merge traces by manually propagating [Datadog trace context][3]. | ||
|
|
||
| **Upstream services to Step Functions**: Include trace context in the Step Function input payload as JSON under the `_datadog` key, which can be located anywhere in the payload. | ||
|
|
||
| **Step Functions to Downstream services**: Add Step Function execution context to your task definitions using the patterns shown above. Additional configuration of the downstream service may be required. |
There was a problem hiding this comment.
| For services not covered in this guide, you can merge traces by manually propagating [Datadog trace context][3]. | |
| **Upstream services to Step Functions**: Include trace context in the Step Function input payload as JSON under the `_datadog` key, which can be located anywhere in the payload. | |
| **Step Functions to Downstream services**: Add Step Function execution context to your task definitions using the patterns shown above. Additional configuration of the downstream service may be required. | |
| For services not covered in this guide, you can merge traces by manually propagating [Datadog trace context][3]. | |
| - **Upstream services to Step Functions**: Include trace context in the Step Function input payload as JSON under the `_datadog` key, which can be located anywhere in the payload. | |
| - **Step Functions to downstream services**: Add Step Function execution context to your task definitions using the patterns shown above. Additional configuration of the downstream service may be required. |
Preview links (active after the
|
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
janine-c
left a comment
There was a problem hiding this comment.
Looks great! Some more minor suggestions 🙂
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Added to the queue but the mergequeue is not enabled for now.
This pull request was merged directly. |
What does this PR do? What is the motivation?
This PR expands the documentation related to Step Function trace merging and updates the related JSONata strings, which propagate Datadog Context more effectively.
Merge instructions
This is ready to merge once it is approved.
Merge readiness: