quickwit-oss / quickwit

Cloud-native search engine for observability. An open-source alternative to Datadog, Elasticsearch, Loki, and Tempo.
https://quickwit.io
Other
7.86k stars 317 forks source link

in helm install,oltp has export in quickwit ui , but jaeger demo is invoke error #5396

Closed freshgeek closed 1 week ago

freshgeek commented 1 week ago

there are two question :

  1. doc:https://quickwit.io/docs/get-started/tutorials/tutorial-jaeger , use 1.52 Tag and env : SPAN_STORAGE_TYPE=grpc-plugin
    jaeger-query:
    image: jaegertracing/jaeger-query:1.52
    ports:
      - 16686:16686
    environment:
      - SPAN_STORAGE_TYPE=grpc-plugin
      - GRPC_STORAGE_SERVER=quickwit:7281
      - GRPC_STORAGE_TLS=false

    but in doc : https://quickwit.io/docs/distributed-tracing/plug-quickwit-to-jaeger , use latest Tag and env : SPAN_STORAGE_TYPE=grpc-plugin , in latest has not support grpc-plugin ,will get error ,only support grpc

    
    docker run --rm --name jaeger-qw  --network=host \
    -e SPAN_STORAGE_TYPE=grpc-plugin \
    -e GRPC_STORAGE_SERVER=127.0.0.1:7281 \
    -p 16686:16686 \
    jaegertracing/jaeger-query:latest

2.  In both of the above situations, I am unable to obtain the data in the example properly in Jaeger, as both display errors:

"stream error: rpc error: code = Unimplemented desc = "

![image](https://github.com/user-attachments/assets/15231500-792c-4ead-9e52-58b7d3ed2841)

in quick-wit ui has success export 

![image](https://github.com/user-attachments/assets/8d33dc02-5511-4ce2-95b5-5e96ac778fe6)

My configuration is as follows:

helm

additionalLabels: {} annotations: {} bootstrap: affinity: {} enabled: true extraEnv: {} extraEnvFrom: [] indexes: extraVolumeMounts: [] extraVolumes: [] initContainers: [] nodeSelector: {} resources: {} sources: command: [] extraVolumeMounts: [] extraVolumes: [] initContainers: [] tolerations: [] config: data_dir: /quickwit/qwdata default_index_root_uri: s3://quickwit/indexes gossip_listen_port: 7282 listen_address: 0.0.0.0 version: 0.8 indexer: enable_otlp_endpoint: true storage: s3: access_key_id: xxx endpoint: http://oss-cn-hangzhou.aliyuncs.com region: oss-cn-hangzhou secret_access_key: xxx configLocation: /quickwit/node.yaml configMaps: [] control_plane: affinity: {} annotations: {} args: [] extraEnv: {} extraEnvFrom: [] extraVolumeMounts: [] extraVolumes: [] initContainers: [] livenessProbe: httpGet: path: /health/livez port: rest nodeSelector: {} podAnnotations: {} readinessProbe: httpGet: path: /health/readyz port: rest resources: {} serviceAnnotations: {} startupProbe: failureThreshold: 12 httpGet: path: /health/livez port: rest periodSeconds: 5 tolerations: [] environment: {} environmentFrom: [] fullnameOverride: '' image: pullPolicy: IfNotPresent repository: quickwit/quickwit imagePullSecrets: [] indexer: affinity: {} annotations: {} args: [] extraEnv: OTEL_EXPORTER_OTLP_ENDPOINT: http://quickwit-indexer:7281 QW_ENABLE_OPENTELEMETRY_OTLP_EXPORTER: true extraEnvFrom: [] extraVolumeMounts: [] extraVolumes: [] initContainers: [] livenessProbe: httpGet: path: /health/livez port: rest nodeSelector: {} persistentVolume: enabled: true storage: 1Gi storageClass: nfs podAnnotations: {} podDisruptionBudget: {} readinessProbe: httpGet: path: /health/readyz port: rest replicaCount: 1 resources: {} serviceAnnotations: {} startupProbe: failureThreshold: 12 httpGet: path: /health/livez port: rest periodSeconds: 5 tolerations: [] updateStrategy: {} ingress: annotations: nginx.ingress.kubernetes.io/proxy-body-size: 10m className: nginx enabled: true hosts:


jaeger yaml :

apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: '6' creationTimestamp: '2024-09-06T09:59:23Z' generation: 7 labels: workload.user.cattle.io/workloadselector: apps.deployment-default-jaeger-ui managedFields:

fmassot commented 1 week ago

@freshgeek someone add a comment here to describe his setup with jaeger

freshgeek commented 1 week ago

@freshgeek someone add a comment here to describe his setup with jaeger

thanks replay ~ His issue solved my problem

I feel that the document still lacks validation and friendly prompts