You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the configuration parameter `EnableTracePropagation` is enabled,
the traces generated by river workers will be *linked* to the traces
that enqueued them. This is done by use of metadata parameters,
following the example in River's documentation for the middleware
functionality (https://riverqueue.com/docs/middleware).
This uses a *link* instead of directly making a child span which is
semantically more correct.
Fixes#41 (I believe, at least).
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
### Added
11
+
12
+
- Add `EnableTracePropagation` configuration method, which enables linking river job spans to the span that enqueued them for tracing *why* a job was enqueued. [PR #65](https://github.com/riverqueue/rivercontrib/pull/65)
0 commit comments