Chris Goller

Hi @yurishkuro we'd like to contribute influxdb as a trace support backend. Currently, we are getting experience with writing spans with [telegraf](https://github.com/influxdata/telegraf/tree/zipkin) into InfluxDB running with the new[ TSI engine](https://www.influxdata.com/path-1-billion-time-series-influxdb-high-cardinality-indexing-ready-testing/)...

Probably a lack of experience on my part ! > On Aug 21, 2017, at 9:39 PM, Yuri Shkuro wrote: > > @goller just saw this https://github.com/influxdata/jaeger. Just curious -...

@yurishkuro To better understand zipkin's model, we implemented a telegraf plugin here: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/zipkin Our goal is to support OpenTracing for sure, but, we figured we would support zipkin's data model...

Hi @mcandre, you can run chronograf with a few options to tell it to reach your influxdb: ``` --influxdb-url= Location of your InfluxDB instance [$INFLUXDB_URL] --influxdb-username= Username for your InfluxDB...

Howdy, I used [depot.dev](https://depot.dev/) and was able to get the un-cached build down to around [15 minutes](https://github.com/goller/qdrant/actions/runs/4894483607/jobs/8738768946) with no Dockerfile changes. The depot client is a drop-in replacement for the...

> @goller I think its about the integration tests which take 30 minutes in your fork too. @JojiiOfficial I see this in the issue: > It would be ideal if...

@spenczar @nathanielc and I have been working on a different go client based on the merging here: https://github.com/influxdata/tdigest Is this useful to you?

Right on! We'd like to get a lot more testing in first. Specifically, we want to use similar tests to the java implementation (https://github.com/influxdata/tdigest/issues/5) We are adding it to our...

Great... btw, LOVE twirp!