Kuber Kaul

@vikrambe otel collector already has jaeger exporter : https://www.jaegertracing.io/docs/1.21/opentelemetry/

@vikrambe both jaeger/zipkin reciever/exporter already exist in the open telemetry container.

Facing the same issue, any documentation or work done on this ? : @pracucci Partitioned my bucket by time into 3 stores , all using a r5.large memcache each (3...

+1

have the same question, is it possible to set multiple cluster issuers in istio-csr(using AWS PCA) ?

@kekbur why are you getting : Verify return code: 19 (self signed certificate in certificate chain) ? even when using Vault CA

This is what the pipeline looks like ``` raw-pipeline: source: pipeline: name: "entry-pipeline" processor: - otel_trace_raw_processor: sink: - elasticsearch: hosts: [ 'https://xxx.us-east-1.es.amazonaws.com' ] insecure: true aws_region: "us-east-1" trace_analytics_raw: true service-map-pipeline:...

@kowshikn ^

Thanks @kowshikn, Ill move to the next version. We have about 10 different clusters ( 10 AWS accounts) which house very different applications. The idea would be two keep two...

@wrijeff yup, I am on it now. This was the plan anyway to move to a scalable data-prepper cluster so this just speeds things up for us. Ill report back...