Adrian Cole
Adrian Cole
Interesting to hear folks say jaeger has a better client library, especially as Jaeger is OpenTracing which is supposed to make that point moot between systems. If anyone cares to...
This will not work out of the box as some other logic would need to change. we can leave this to see if it is popular or not
@openzipkin/elasticsearch any interest on this?
@xeraa do you know which version rollover index was added? I agree the core issue here is size.
@libeilin before we experiment with a non-OSS feature, can you comment if rollover indexing is desirable? maintaining features has a cost, especially so with non OSS distributions (as it affects...
email related to this thread on our dev list https://lists.apache.org/thread.html/73c2efa69e3ff0a519c6b6c2f5e551159c34902c29df01b2703e9126@%3Cdev.zipkin.apache.org%3E
@untergeek thanks for the pointer. I think you are pointing to this specifically right? https://www.elastic.co/guide/en/elasticsearch/client/curator/5.6/ex_rollover.html To elaborate this approach, we'd need some more details about what this will take in...
> Just as an idea: Maybe this is going a bit too deep down the rabbit hole for one datastore and it would make more sense to leave that part...
I think this issue got stuck as we were worried about how to address varied granularity. @narayaruna opened #2767 which doesn't imply varied granularity. If we limit this to hourly...
@xeraa so I think the concern from @narayaruna is that with TB scale indexes, search, even with our cherry-picked indexing, require bumping read timeouts to 60s.. so more about query...