Show HN: Distributed Tracing Using OpenTelemetry and ClickHouse

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.<p>Would be happy to answer your questions here.

Nice, I&#x27;m using Clickhouse to build Luabase[0]. I saw &quot;ClickHouse cluster support&quot; on your roadmap, are you just using a single node right now? How are you handling persistent storage?<p>0 - <a href="https:&#x2F;&#x2F;luabase.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;luabase.com&#x2F;</a>

Is data being inserted into CH as it&#x27;s received, or is there an intermediary buffer? A general overview of the flight of telemetry data through the system would be very welcome.

Uptrace looks really pretty interesting. I particularly like the query language that you can use to query your distributed trace data. This is the biggest limitation I have found with jaeger, lots valuable data is stored in storage, but it&#x27;s very hard to analyze in aggregate.<p>For example, a question I want to be able to answer with a query against the distributed trace data: show me the (mean, median) time between a parent http request and a child http request in the same trace tree. As far as I understand, this requires the query language to be able to group by trace id, then be able to identify parent&#x2F;child relations.<p>Does the Uptrace query language allow you to do something like this?

I&#x27;ve been thinking about mixing OpenTelemetry and CH for a while. There is a wild competition in this area, hope you luck and fun!

This solution has some great ideas but there’s always “but”.<p>Main things distinguishing this from Jaeger are on the storage side. Jaeger has pluggable span writers and readers so it would be possible to do the same right in Jaeger.<p>The UI part is probably more work than the actual storage but the default Jaeger UI is anyway not the main tool people tend to work with.

Now that ClickHouse has released async writes you won&#x27;t need to use the buffer engine anymore, which has been always a non recommended solution anyway.

Looks interesting. Can you share a couple of common use cases, say - for somebody running a typical saas app? Also, are there plans for an Elixir client?

This is quite cool piece of work. Would you please make a comparison between uptrace and jaeger?

I wonder how this works well with cloki (loki for clickhouse)

how is different from datadog ?

how is it different from <a href="https:&#x2F;&#x2F;signoz.io" rel="nofollow">https:&#x2F;&#x2F;signoz.io</a><p>signoz datastore is built with cassandra and yours with clickhouse.