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
Distributed Tracing for Entities (In-Process) (#1190)
* added distributed tracing for entities
* change in how the distributed trace context is propagated in the case that an entity in WebJobs starts an orchestration
* slight style update
* some more tiny style things
* addressing two more PR comments
* forgot to add one annotation
* yet another small style change
* addressing PR comments
* forgot one file
* addressing more PR comments
* forgot two comments
* addressing a few small comments
* refactored most of the tracing into this repo to more accurately reflect the end time of activites (like, when the call/signal request to an entity is actually sent, or when an orchestration is actually created by an entity)
* fixing spacing
* slight change in formatting of the create orchestration trace
* addressing PR comments
* adding back new lines at the ends of files
* trying to fix these line endings
* dealing with new lines again
* tiny change
* missed a null check
* reverting to old design
* missed some
* and missed some more
* missed even more
* will it ever end
* last one i think
* moved activity for entity starting an orchestration back into webjobs
* as always missed some stuff
* added support for an entities enabled flag
* added a null check for client span ID when creating the activity for scheduling a suborchestration
* getting rid of an extra line
* addressing PR comment
* addressing a few PR comments
* addressing some PR comments, slightly changing the logic of the modified TaskHubClient method
---------
Co-authored-by: Sophia Tevosyan <[email protected]>
// If a parent trace context was provided via the CreateSubOrchestrationAction.Tags, we will use this as the parent trace context of the suborchestration execution Activity rather than Activity.Current.Context.
// If a parent trace context was provided but we fail to parse it, we don't want to attach any parent trace context to the start event since that will incorrectly link the trace corresponding to the orchestration execution
1179
+
// as a child of Activity.Current, which is not truly the parent of the request
0 commit comments