You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of collector will cache the submitted spans in a local queue for better performance, it means when you exit your program, you may need wait a while for those pending messages with zipkin_collector_shutdown
In addition to what @flier mentions @cli99, you must give the span a service name for it to appear in the UI via the zipkin_span_annotate call, which is missing from your code snippet. @flier I think this would be good to add to the docs. Something just saying that while the server will receive spans without a service name annotation, they will not be easily visible in the UI without it.
Can you give a complete local tracing example?
I have the following test code. It compiles and runs but my zipkin server does not capture anything.
I have zipkin server running as
docker run -d -p 9411:9411 openzipkin/zipkin
Thanks.
The text was updated successfully, but these errors were encountered: