we were setting the tags for the trace as a bootstrap process. this means that the tracer.init call does not bootstrap properly (as tracer.use is meant to be called at start-up, prior to actual tracing).
this PR changes it so that the tags are set on the span.
Solution
instead of calling tracer.use, which is a bootstrap call, change to get the active span and calling setTag on that span.
Tests
[ ] Find traces in isomer's APM like this one, and verify that the tags are present
Problem
we were setting the tags for the trace as a bootstrap process. this means that the
tracer.initcall does not bootstrap properly (astracer.useis meant to be called at start-up, prior to actual tracing).this PR changes it so that the tags are set on the span.
Solution
tracer.use, which is a bootstrap call, change to get the active span and callingsetTagon that span.Tests