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
* Added replay aware tracing filter
* Few changes to the replay aware filter feature:
* We now emit the span all the times for the endpoint handle method. This seems a reasonable default, and doesn't require the tracing-subscriber dependency (we already pull in tracing as dependency anyway)
* Renamed the span name and the replaying field filter, to avoid confusion and clash
* Now the replay aware filter will look for the exact span name created by the handler. This should make the matching of the exact span we wanna use for filtering more robust.
* Flip the replaying field not only when taking an awaiting, but also when executing `sys_` functions on the state machine. Those are the ones that can cause state transitions.
* Simplify the tracing example
* Rename feature to `tracing-span-filter`
---------
Co-authored-by: Harsha Teja Kanna <h7kanna@gmail.com>
Copy file name to clipboardExpand all lines: src/lib.rs
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -207,7 +207,9 @@
207
207
//! }
208
208
//! ```
209
209
//!
210
-
//! For more information, have a look at the [tracing subscriber doc](https://docs.rs/tracing-subscriber/latest/tracing_subscriber/fmt/index.html#filtering-events-with-environment-variables).
210
+
//! You can filter logs *when a handler is being replayed* configuring the [filter::ReplayAwareFilter].
211
+
//!
212
+
//! For more information about tracing and logging, have a look at the [tracing subscriber doc](https://docs.rs/tracing-subscriber/latest/tracing_subscriber/fmt/index.html#filtering-events-with-environment-variables).
211
213
//!
212
214
//! Next, have a look at the other [SDK features](#features).
0 commit comments