-
Notifications
You must be signed in to change notification settings - Fork 11
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
Sending data in zipkin v2 format #11
Comments
I would be more than happy to look over any patch or PR contributed, that's the best I can do for now. |
Gotcha. Yeah, I'm not as familiar with Zipkin as I should be but will keep that in mind. Also, Brave Cassandra doesn't report the query details like this tracing instrumentation. |
@jake-codes parsing etc is a just a feature waiting to be enabled. Mainly the zipkin one is parsimonious by default. |
@adriancole Are you saying that Brave Cassandra can show the raw query details by enabling some setting? If so, would you mind showing an example. I can move this question to another location if more appropriate. |
No what I mean is that brave-cassandra has an issues list where features can be requested and implemented. Parsing is a routine ask, but we only implement things asked. Also, you may be in a position to help implement what you are asking for.. not sure. At any rate, this project is less likely to be maintained and released (momentum), so I would recommend same as mick said, which is to ask specifically what you need in brave-cassandra, if not helping to implement that. |
I can post an issue in Brave Cassandra. |
Having this send out data in this latest v2 format would be a huge help, if possible.
The text was updated successfully, but these errors were encountered: