Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-1221

Implement native OTEL Elasticsearch storage

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • jaeger-2.0.0.TP1
    • None
    • None
    • None
    • Tracing Sprint #41, Tracing Sprint #42

      Implement Elasticsearch writer that accepts OTEL data model (pdata.Traces).

      Requirements:

      However, Jaeger ES Bulk configuration exposes a different configuration that OTEL batch processing:

      ```
      --es.bulk.actions int The number of requests that can be enqueued before the bulk processor decides to commit (default 1000)
      --es.bulk.flush-interval duration A time.Duration after which bulk requests are committed, regardless of other thresholds. Set to zero to disable. By default, this is disabled. (default 200ms)
      --es.bulk.size int The number of bytes that the bulk requests can take up before the bulk processor decides to commit (default 5000000)
      ```

      OTEL batch is able to configure only time based bulking and size - number of spans. We should do perf tests to assure that the new implementation has similar characteristics than the current one.

      Related to https://github.com/jaegertracing/jaeger/issues/2163

              ploffay@redhat.com Pavol Loffay
              ploffay@redhat.com Pavol Loffay
              Distributed Tracing
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: