-
Notifications
You must be signed in to change notification settings - Fork 714
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
Set endpoint for remove service #15
Comments
Hi, Sorry for not picking this up quickly. I'll look into it and come back to you later this week. Kristof |
Hi, Currently there is no way to provide a custom endpoint in the In the RestEasy integration the endpoint is set once when the first request is intercepted. Off course when you create your 'Postgresql' span you can do: I'm interested in your JDBC pool monitor :) can you explain how it works and in which frameworks it integrates? |
You're right - the API needs some extension, so you can override the endpoint for a given span. What you need is a hook to execute before a database command (with the given SQL query) and a hook just after it is executed. The vanilla JDBC API isn't exactly very extension-friendly, but there are some tools/libraries out there: You can use log4jdbc to wrap your DataSource. You provide a Brave tracer as a logger to log4jdbc. Simple as that! Or eventually (as we have done, since we run stuff on Tomcat) extend JdbcInterceptor from Tomcat's jdbc pool. Our implementation is only about 30 lines of code, but it's not open-sourceable, since it depends on some other internal utilities. |
Fix merged. Close issue. |
I want to implement a JDBC pool monitor that intercepts SQL requests and traces them. However, they are logged as coming from my own service (naturally) but I want them to appear in Zipkin as "Postgresql" , just like Twitter has overriden traces and called them "Memcached" in this example:
http://twitter.github.io/zipkin/images/web-screenshot.png
How can I override the endpoint configuration from the client side?
The text was updated successfully, but these errors were encountered: