-
-
Notifications
You must be signed in to change notification settings - Fork 427
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
Align span op
spec
#2261
Comments
So this is still undecided on what these should change to, so feedback here is welcome. We can always also amend the develop docs based on this. |
Yep, @romtsn said he's gonna take a look at it. |
@AbhiPrasad so here's the summary: SentrySpanAdvicePretty straightforward, because we can treat this essentially as a manual instrumentation/span. Users have to manually add a I don't think we need to have a strict span op for that, since again, it's manual instrumentation. SentryInstrumentationThe first part will be set to the type that contains the queried fields. For root operations it'd be one of For example, for this query:
There will be 2 spans: I think what you suggested should work here, so either just SentryApolloInterceptor/SentryApollo3InterceptorIt will either set the op to the operation name or
will set it to
cc @adinauer |
If we want to leverage our performance issues feature for AOP instrumentation, we'd need a defined Do you have any suggestions here? |
I was not aware we can detect slow custom spans. Could you provide more details on how we would do that? Will we allow users to set their custom thresholds for slow spans? |
Sorry, I don't understand how can we have a pre-defined |
If these are methods, could we default to applying the
Can this be the span description instead? The operation than will stay consistent, while the description can have a higher range of unique values. |
sounds good 👍
Yes, we can default to this for the description. It can be still overwritten by users though, but I think it's alright. As for the other 2, can we agree on |
Sounds good to me! |
Description
getsentry/develop#693
sentry-java/sentry-apollo/src/main/java/io/sentry/apollo/SentryApolloInterceptor.kt
Line 88 in e2ea31c
sentry-java/sentry-graphql/src/main/java/io/sentry/graphql/SentryInstrumentation.java
Line 136 in e2ea31c
The text was updated successfully, but these errors were encountered: