Skip to content
This repository was archived by the owner on May 23, 2023. It is now read-only.

Conversation

@jpiper
Copy link

@jpiper jpiper commented Oct 12, 2019

I've been working on lots of tracing where data is exchanged via a message broker, so we're always wanting to start spans as followsFrom rather than ChildOf. As far as I can see, there isn't anything out of the box that deals with this so I've added the functions that would do it here, just in case you think this would be useful.

There are many situations where you might wish to start spans as a followsFrom (e.g. when interacting with a message bus). This adds convenience functions around this
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (master@a7454ce). Click here to learn what that means.
The diff coverage is 71.42%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #224   +/-   ##
=========================================
  Coverage          ?   59.64%           
=========================================
  Files             ?       14           
  Lines             ?      840           
  Branches          ?        0           
=========================================
  Hits              ?      501           
  Misses            ?      299           
  Partials          ?       40
Impacted Files Coverage Δ
gocontext.go 82.6% <71.42%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7454ce...973a7de. Read the comment docs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants