Thanks. The competition is high indeed thanks to OpenTelemetry. Let me know if have any ideas / feature requests - it is interesting how other people see OpenTelemetry + ClickHouse working together.
You can use Uptrace to monitor routes/queries performance, errors, and partially logs (only Go at the moment and it is unofficial). Distributed tracing excels at finding the root cause and resolving issues in production. That is the future / present of any kind of monitoring and the potential is immense.
>Also, are there plans for an Elixir client?
Uptrace client is a just pre-configured distribution of OpenTelemetry so you try to configure OpenTelemetry https://github.com/open-telemetry/opentelemetry-erlang . We will provide a pre-configured client for Elixir if there is an interest.
I will try, but I don't know that much about Jaeger and it is hard to be unbiased.
UI-wise, Uptrace does not have service dependency analysis, because I don't find it very useful/interesting (let me know if I am wrong). I believe Jaeger does not have span grouping, percentiles, and filters/aggregation are much much simpler.
Jaeger has remote sampling which can be a powerful feature if users are ready to spend their time configuring it. Would be nice to hear if that is the case and
if many people are using it.
I've also seen some work on in-memory tail-based sampling, but I don't know if that is ready to use or not. I plan to add tail-based sampling to Uptrace too.
We use remote sampling. I don't have a ton of experience with Jaeger, but I've used it a lot, and implemented OpenTracing in a dozen or so apps.
The benefit of remote sampling, as I understand it, is that the sample rata doesn't need to be configured in each app. So in principle, you could have a little slider in the UI to adjust the sample rate for each individual app, perhaps increasing it during a particular incident to capture more traffic data.
Without remote sampling, you'd have to hard-code the rate into the app's config or code, which then requires a redeploy to change the setting. With a lot of microservices to maintain, it seems a lot simpler to have a central location for such settings.
Uptrace looks fantastic, by the way. It's about time someone gives Zipkin and Jaeger some competition. And Clickhouse makes a lot more sense as a backend than Cassandra.
Yes you are mostly right, we can open an issue on github and try to compare them, if you agree. This would be among the first things a user wants to know before picking up uptrace.
Sure, I am very interested to know what features are people looking for.
I don't provide direct comparison, because it is hard to judge which features are relevant. For example, the few people I've asked told me that they don't use "service dependency analysis" and I don't find that functionality useful myself. But you will find that feature in most products so perhaps I've asked the wrong people :)
Uptrace is an open source distributed tracing system that uses OpenTelemetry to collect data and ClickHouse database to store it. ClickHouse is the only dependency.
