Same certain spans in tracing are missing #462
Replies: 1 comment
-
We found out in the team that we made noop for these libs and it was the issue on our side, not on openfga package - I apologise for it 😅 if slices.Contains(t.names, name) {
return t.noop.Tracer(name, opts...)
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, people!
Setup
My team uses
github.com/openfga/openfga v1.8.11
for our application. We initialise the server with the following function:MustNewServerWithOpts directly with some options.
F.e.
Problem
If I want to check the trace for the call Server.Check,
I could observe only certain spans: cache.Read or resolveTypesystem, but I couldn't find any spans with other span names. F.e. Check or
ResolveCheck.
It looks quite weird that only certain spans are presented in every trace.
Adding some screenshots from our Honeycomb:

Do I miss something in the configuration, or is it something expected?
I am not really sure that it's an "issue" on this package side, but it seems like sampling for spans, when every time it affects the certain span names 😅
The help will be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions