Yuri Shkuro

Good idea. Our Cassandra lazy session (I saved it as [gist][]) had to implement larger API than just the span storage. However, in order to do this at the generic...

Currently what Jaeger defines as "storage backend" must support (a) trace lookup by ID, and (b) indexing & searching. The former is relatively easy to do with S3 (you may...

Reopening this to link to @muhammadn 's work mentioned in https://github.com/jaegertracing/jaeger/issues/638#issuecomment-820213986

@bogdandrutu aside from some convenience functions, `/model` is just auto-generated classes from proto. I don' think that warrants a cross-dependency, why not just re-generate them in the collector?

We do, but the otel-collector does not need the functionality in those classes. In fact, those classes tie the implementation to a particular version of proto & gogo and are...

@bogdandrutu could you please point to the code that depends on jaeger/model?

We need to make the name sanitizing more strict. Right now it only swaps a couple of characters, but perhaps we should flip that and only allow a fixed set...

Alternatively, we could avoid calling prom_client methods that panic and instead call those that return errors, in this case `hist.GetMetricWithLabelValues` instead of `hist.WithLabelValues`. Then use some kind of fallback. Even...

The repro script doesn't work for me ``` $ bash run.sh Creating network "nil-ptr_default" with the default driver Creating nil-ptr_es01_1 ... done Creating nil-ptr_collector01_1 ... done ERROR: for ingestor Container...

We already have a fix being worked on in #3819. > I have a program to produce spans & concat them with a trace ID based on our business logic,...