We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
here are my code,
use ZipkinTracer::RackHandler, { :service_name => 'demo', :service_port => '80', :sample_rate => 1, :log_tracing => true, :json_api_host => "http://localhost:9411/" }
def get_repositories(_request, _call) project_id, query = _request.project_id, _request.q ZipkinTracer::TraceClient.local_component_span('local relay') do |ztc| ztc.record "relay.get_repositories" ztc.record_tag 'project_id', project_id ztc.record_tag 'query', query p ztc.inspect "result" end end
but, got a NullSpan
"#<ZipkinTracer::NullSpan:0x007f8eeb928750>"
How to solve it?
The text was updated successfully, but these errors were encountered:
Looks good to me. Maybe is a bug in the tracer. Let me take a look and come back to you later
Sorry, something went wrong.
my app is base on sinatra framework
sinatra
in app.rb ZipkinTracer::TraceClient.local_component_span that is ok, but not working inside the lib folder
ZipkinTracer::TraceClient.local_component_span
lib
Can provider a method like this?
def get_repositories(_request, _call) project_id, query = _request.project_id, _request.q ZipkinTracer::TraceClient.reconfig({ :service_name => 'demo', :service_port => '80', :sample_rate => 1, :log_tracing => true, :json_api_host => "http://localhost:9411/" }) ZipkinTracer::TraceClient.local_component_span('local relay') do |ztc| ztc.record "relay.get_repositories" ztc.record_tag 'project_id', project_id ztc.record_tag 'query', query p ztc.inspect "result" end end
No branches or pull requests
here are my code,
but, got a NullSpan
"#<ZipkinTracer::NullSpan:0x007f8eeb928750>"
How to solve it?
The text was updated successfully, but these errors were encountered: