-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Cassandra & memory storage update: query service to support spanKind when retrieve operations for a given service. #1921
Comments
guo0693
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 13, 2019
5 tasks
guo0693
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 14, 2019
guo0693
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 19, 2019
This was referenced Nov 19, 2019
yurishkuro
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 22, 2019
guo0693
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 22, 2019
guo0693
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 22, 2019
# Conflicts: # plugin/storage/cassandra/spanstore/operation_names.go # plugin/storage/cassandra/spanstore/operation_names_test.go # plugin/storage/cassandra/spanstore/reader_test.go # plugin/storage/cassandra/spanstore/writer_test.go
guo0693
added a commit
to guo0693/jaeger
that referenced
this issue
Nov 26, 2019
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requirement - what kind of business use case are you trying to solve?
Related to #1920
Cassandra & memory storage update: query service to support spanKind when retrieve operations for a given service.
Update query service so that the restful & grpc endpoints satisfy requirement in Support optional query param "spanKind" when get operations for given service #1920.
Problem - what in Jaeger blocks you from solving the requirement?
Proposal - what do you suggest to solve the problem or improve the existing situation?
Any open questions to address
The text was updated successfully, but these errors were encountered: