Pavol Loffay
Pavol Loffay
Which is misleading and should be probably logged when waiting on kafka to be up during the first deployment.
@chhetripradeep from https://github.com/pavolloffay/jaeger-clickhouse/pull/34#issuecomment-886882402 > We run with 3 replica and as we need to expand the cluster we add more shards. One thing to note is clickhouse doesn't have any...
The distributed table could be created with multiple sharding functions: `rand()`, `cityHash64(traceID)` - see https://clickhouse.tech/docs/en/sql-reference/functions/hash-functions/. The hash functions take an argument, we should consider using `traceID` to keep data from...
https://github.com/pavolloffay/jaeger-clickhouse/blob/main/config.yaml#L4
Support elasticearch rollover indices - we need to read data from `jaeger-span-read` and not daily indices. The write could be done to daily indices - we do not support rollover...
Related to https://github.com/jaegertracing/jaeger-operator/issues/294
We should inter-service links if a service creates internal spans. However the same link is showed also if a service calls itself via HTTP. The dependency graph could partition calls...
Some thoughts: * run elastic and cassandra tests in parallel * do not shut down containers between tests but rather wipe all data (e.g. in C* via CQL and for...
There are two possible integrations: - [ ] put SpanContext into standard logs - there is a problem that OpenTracing does not define getters on SpanContext therefore it's not possible...