my goal has been to get you a solid idea of the slow query, that's as much as you can expect here
underprovisioned clusters, services who do not sample at all, or who add too many tags or logs, or have variables in names can all result in slow, and 15s is really slow.
if you are sending 100% data at any cluster you can kill it
this is why ex in brave we have things like rate-limited samplers
At present, I suspect that the IIS of ES exceeds the maximum number of connections
you can also use prometheus, but this only shows the rate received not the rate sent
if using java the zipkin-reporter-java project has micrometer integartion for sender metrics
Finally, I query the log and find that it is here. If I use aggregation, I will not find the result. Throw timeout.
It's OK to delete the code in red box .
What is the problem? Isorry to ask you something other than Zipkin
It's OK to delete the code in red box .
What is the problem? Isorry to ask you something other than Zipkin
but anyway since you've isolated this you now have a way to troubleshoot your data indepedent of zipkin
when you can do that http command without timeout, then the UI has a chance to operate. you can see if a shorter duration ever completes
ex the "from" and "to"
QUERY_LOOKBACK defaults to 1 day in millis: 86400000
I don't run ES I don't know the troubleshooting tools people use to look at query planner etc
you may be able to find techniques on their forum or docs
most times when someone comes in asking they aren't even running a cluster
just one overloaded JVM for elasticsearch
Hi, I am working with a "synchronous" javascript environment (modified v8 engine inside ArangoDB server). I need to use a tracer for my application that will run on this engine. Async code will not behave properly here (https://www.arangodb.com/docs/stable/foxx.html#compatibility-caveats)
They have provided stubs for setTimeout, setInterval, clearTimeout and the like, so the code will not entirely break.
I was wondering how Zipkin's js client would work in this environment (if it worked at all). Does it depend on an event loop and timers to periodically report its collected spans? Is there a way to disable this behaviour if so? ArangoDB does have a 'Tasks' API that lets you run async code (similar to a cron), but I'm not sure if I can plug in a custom reporter to use this.
Please help me understand if and how I can integrate Zipkin in this setting.'
@rajatsingh998 it would normally be running at http://localhost:9411/zipkin , any reason you're building from source ?
the quickstart is a better way to get up and running: https://github.com/openzipkin/zipkin/#quick-start
@abhisheknalin best is to start from the github root https://github.com/openzipkin/zipkin and start browsing from there. If you're interested how the server part works and is configured : https://github.com/openzipkin/zipkin/tree/master/zipkin-server , if you're interested in instrumentation more then https://github.com/openzipkin/brave/tree/master/brave and more in detail here https://github.com/openzipkin/brave/tree/master/brave .
the documentation is contained in each
README.md of the respective modules
so by browsing https://github.com/openzipkin/ and its subprojects you will find what you need
@pnilesh1 better to check in envoy docs.