[jaeger-v2] Deployment options (GSoC 2024 project) about jaeger HOT 5 OPEN

@yurishkuro I would like to discuss about it and need your valuable guidance to come up with a perfect solution for deployments for v2

from jaeger.

@yurishkuro i would like to work on the issue need some resources to get a brief idea about the project and come with a solution reagarding the issue

from jaeger.

@yurishkuro i would like to work on the issue need some resources to get a brief idea about the project and come with a solution reagarding the issue

There are already project brief and resources in the issue description. Please check those.

If you need further details, you could look deeper into the deployment options of otel collector on kubernetes. For example, this one explains it well (the author is maintainer of both jaeger and otel): https://github.com/jpkrohling/opentelemetry-collector-deployment-patterns/tree/main/pattern-3-kubernetes

from jaeger.

Thanks for the valuable information @haanhvu it surely helped me a lot about the Isuue

from jaeger.

I got working V2 with memory store with the OTEL operator:

kubectl apply -f - <<EOF
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: jaeger
spec:
  image: jaegertracing/jaeger:latest
  ports:
  - name: jaeger
    port: 16686
  config: |
    extensions:
      jaeger_query:
        trace_storage: memstore

      jaeger_storage:
        memory:
          memstore:
            max_traces: 100000

    receivers:
      otlp:
        protocols:
          grpc:
          http:

    exporters:
      jaeger_storage_exporter:
        trace_storage: memstore

    service:
      extensions: [jaeger_storage, jaeger_query]
      pipelines:
        traces:
          receivers: [otlp]    
          exporters: [jaeger_storage_exporter]
EOF

The elasticsearch will be more complicated as it requires index cleaner and rollover which run as cronjobs in jaeger v1. However, this functionality could be implemented in the V2 as a separate extension or be part of the storage exporter e.g.

extensions:
  jaeger_storage:
    elasticsearch:
      index_cleaner:
        num_days: ....

   jaeger_elasticearch_index_cleeaner:
     num_days: ...

Alternatively we could let users configure https://opensearch.org/docs/latest/im-plugin/ism/index/ directly for rollover and index cleaning functionality and later maybe build it into the storage.

Cassandra will require schema creation job at startup which could be as well implemented in Jaeger as an extension.

from jaeger.