-
Notifications
You must be signed in to change notification settings - Fork 279
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
Check jax-rs AsyncResponse for span before starting new one #1403
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,6 +15,7 @@ | |
|
||
import com.google.auto.service.AutoService; | ||
import datadog.trace.agent.tooling.Instrumenter; | ||
import datadog.trace.bootstrap.ContextStore; | ||
import datadog.trace.bootstrap.InstrumentationContext; | ||
import datadog.trace.bootstrap.instrumentation.api.AgentScope; | ||
import datadog.trace.bootstrap.instrumentation.api.AgentSpan; | ||
|
@@ -83,7 +84,28 @@ public static class JaxRsAnnotationsAdvice { | |
|
||
@Advice.OnMethodEnter(suppress = Throwable.class) | ||
public static AgentScope nameSpan( | ||
@Advice.This final Object target, @Advice.Origin final Method method) { | ||
@Advice.This final Object target, | ||
@Advice.Origin final Method method, | ||
@Advice.AllArguments final Object[] args, | ||
@Advice.Local("asyncResponse") AsyncResponse asyncResponse) { | ||
ContextStore<AsyncResponse, AgentSpan> contextStore = null; | ||
for (final Object arg : args) { | ||
if (arg instanceof AsyncResponse) { | ||
asyncResponse = (AsyncResponse) arg; | ||
contextStore = InstrumentationContext.get(AsyncResponse.class, AgentSpan.class); | ||
if (contextStore.get(asyncResponse) != null) { | ||
/** | ||
* We are probably in a recursive call and don't want to start a new span because it | ||
* would replace the existing span in the asyncResponse and cause it to never finish. We | ||
* could work around this by using a list instead, but we likely don't want the extra | ||
* span anyway. | ||
*/ | ||
return null; | ||
} | ||
break; | ||
} | ||
} | ||
|
||
Comment on lines
+87
to
+108
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And this doesn't need to be done for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. jaxrs1 doesn't support async. that is the main distinction between the two. |
||
// Rename the parent span according to the path represented by these annotations. | ||
final AgentSpan parent = activeSpan(); | ||
|
||
|
@@ -93,14 +115,22 @@ public static AgentScope nameSpan( | |
|
||
final AgentScope scope = activateSpan(span, false); | ||
scope.setAsyncPropagation(true); | ||
|
||
if (contextStore != null && asyncResponse != null) { | ||
contextStore.put(asyncResponse, span); | ||
} | ||
|
||
return scope; | ||
} | ||
|
||
@Advice.OnMethodExit(onThrowable = Throwable.class, suppress = Throwable.class) | ||
public static void stopSpan( | ||
@Advice.Enter final AgentScope scope, | ||
@Advice.Thrown final Throwable throwable, | ||
@Advice.AllArguments final Object[] args) { | ||
@Advice.Local("asyncResponse") final AsyncResponse asyncResponse) { | ||
if (scope == null) { | ||
return; | ||
} | ||
final AgentSpan span = scope.span(); | ||
if (throwable != null) { | ||
DECORATE.onError(span, throwable); | ||
|
@@ -110,16 +140,11 @@ public static void stopSpan( | |
return; | ||
} | ||
|
||
AsyncResponse asyncResponse = null; | ||
for (final Object arg : args) { | ||
if (arg instanceof AsyncResponse) { | ||
asyncResponse = (AsyncResponse) arg; | ||
break; | ||
} | ||
if (asyncResponse != null && !asyncResponse.isSuspended()) { | ||
// Clear span from the asyncResponse. Logically this should never happen. Added to be safe. | ||
InstrumentationContext.get(AsyncResponse.class, AgentSpan.class).put(asyncResponse, null); | ||
} | ||
if (asyncResponse != null && asyncResponse.isSuspended()) { | ||
InstrumentationContext.get(AsyncResponse.class, AgentSpan.class).put(asyncResponse, span); | ||
} else { | ||
if (asyncResponse == null || !asyncResponse.isSuspended()) { | ||
DECORATE.beforeFinish(span); | ||
span.finish(); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not immediately related, though I discovered this problem in the same investigation and it is tangentially related...
When an executor has multiple
execute
methods, one calling the other, previously they were both instrumented and we would seeFailed to set continuation because another continuation is already set
log messages. This is because the first call would create a continuation, set it on the task, then call the next execute method, which would do the same, but it would close the second one and keep the first. These log messages were a red herring for my investigation as it didn't actually impact the application reporting.