Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V1.0.0 #5

Merged
merged 18 commits into from
Jul 27, 2018
Merged

V1.0.0 #5

merged 18 commits into from
Jul 27, 2018

Conversation

carlosalberto
Copy link
Collaborator

No description provided.

* Integration with OT 2.0.
Do not use store our own objects to Tornado objects
if that's not really needed, and use partial functions
instead.
And rename related items (opentracing_tracer and similar
ones). Having it with the Tracer suffix made users think
this was an actual opentracing.Tracer, which is not the case.
Replace the more basic functools, as we are anyway
using wrapt already in part of our code base.
It was not being automatically restored (in contrast to
how it *is* for incoming request's callbacks), so fix
that, and make our tests reproduce such scenario.
The reasons are:

1. It's common to issue many requests at once,
   and that is not supported, as part of
   TornadoScopeManager, as the used StackContext
   gets messed up. This would greatly limit
   our instrumentation code.
2. Issuing requests is the last part of
   the pipeline, so no further children Spans
   could consume it. Nevertheless, we provide
   it in the start_span callback.
'error' needs to be a boolean, and 'error.object' is
a log entry, not a tag.
Use standard tags from opentracing and tune the error logs
as well.
1. trace_all=True, trace_client=True when
   using global patching.
2. trace_all=False, trace_client=False when
   doing explicit decoration.
Simply do not trace anything in such case.
This is in case the start_span_cb was previously set directly
on the TornadoTracing object.
@carlosalberto carlosalberto merged commit 0c71b52 into master Jul 27, 2018
@carlosalberto carlosalberto deleted the v1.0.0 branch October 1, 2018 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant