how to debug jaeger collector receving otlp

[cridam]

As a new incomer with jaeger, I 've deployed jaeger using the helmchart https://jaegertracing.github.io/helm-charts and configure the collector to receive from the OTEL SDK (sidecar exporter). On client side, request looks to be prepared, but nothing occurs on jaeger collector side (below the collector configuration).
I d like to activate the log to understand why the OTLP http export traces are not processed whereas it look fine with a empty span using curl.
In both cases, i don't succeed in producing log on collector level. What's wrong? Thanks for your help

          extraEnv:
      - name: JAEGER_LOG_LEVEL
        value: debug  
      enabled: true
      service:
        otlp:
          grpc:
            port: 4317
            name: otlp-grpc
          http:
            port: 4318
            name: otlp-http (modifié) 

[dosubot[bot]]

Hey @cridam! I'm here to help you with your Jaeger collector configuration. Let's get to the bottom of this together.

To debug the Jaeger collector not processing OTLP HTTP exports, ensure the following:

1. OTLP Receiver Enabled: Verify that the OTLP receiver is enabled in your configuration. Check if the collector.otlp.enabled option is set to true.

2. Port Configuration: Ensure that the ports are correctly configured. The default ports for OTLP are 4317 for gRPC and 4318 for HTTP. Make sure these match your configuration.

3. Logging Level: Since you've set JAEGER_LOG_LEVEL to debug, ensure that the logs are being output correctly. Check the deployment logs to see if there are any errors or warnings related to the OTLP receiver.

4. Deployment Status: Verify that the Jaeger collector is running and receiving requests. You can check the status of the deployment using Kubernetes commands like kubectl get pods and kubectl logs <collector-pod-name>.

5. Network and Configuration Issues: Common issues include incorrect host/port configuration, TLS misconfiguration, and CORS issues. Ensure these are correctly set up ^[1].

If these steps do not resolve the issue, further investigation into the network settings and collector configuration may be necessary.

To continue talking to Dosu, mention @dosu.

[cridam]

@dosu , collector.otlp.enabled doesn't exist in jaeger chart .
the JAEGER_LOG_LEVEL has no effect at all, looks not consider at all

[dosubot[bot]]

The JAEGER_LOG_LEVEL might not affect the Jaeger collector logs because the log level is typically set using the log-level option in the configuration, not through an environment variable. Ensure that the log-level is correctly set in your configuration file or command line arguments.

To enable OTLP in the Jaeger Helm chart, you can set the following in your configuration:

collector:
  otlp:
    enabled: true

If collector.otlp.enabled doesn't exist, ensure your Helm chart is up to date, as this option should be available in recent versions ^[1].

To continue talking to Dosu, mention @dosu.

[cridam]

@dosu please refresh your knowledge model ;-) ... the collector.otlp doesn't exist as well , collector.enabled=true and the OTLP is triggered whenver oltp service is filled seethe master branch https://github.com/jaegertracing/helm-charts/blob/4aab996119cfcb9bec3cf098462f66d255f5f663/charts/jaeger/templates/collector-deploy.yaml#L65.

[dosubot[bot]]

To ensure the Jaeger collector processes OTLP exports, you need to configure the OTLP receiver settings correctly. Even if collector.oltp doesn't exist, you can still set up the OTLP service by defining the necessary ports and enabling the service.

Here's how you can configure it:

1. Enable the Collector: Make sure collector.enabled is set to true.

2. Define OTLP Service: Configure the OTLP service by specifying the gRPC and HTTP ports in your Helm chart:

   collector:
     enabled: true
     service:
       otlp:
         grpc:
           port: 4317
           name: otlp-grpc
         http:
           port: 4318
           name: otlp-http

3. Logging Configuration: If JAEGER_LOG_LEVEL isn't working, ensure the log level is set in the configuration file or command line arguments, not just as an environment variable.

By setting these configurations, the OTLP service should be triggered when the collector is enabled and the service is defined ^[1].

To continue talking to Dosu, mention @dosu.

[yurishkuro]

@cridam please explain your YAML snippet. I don't understand what it refers to - neither Jaeger collector nor OTEL Collector would have a section service defined like you have.

[cridam]

@yurishkuro , let me reword a bit, i have a worload that exports in OTLP to the jaeger collector (on 4318 port) deployed uisng the helm chart (not the chart with operator). This chart has the following conf :

    provisionDataStore:
      cassandra: false
    allInOne:
      enabled: false
    storage:
      type: badger
    agent:
      enabled: true
    collector:
      serviceAccount:
        create: true # disable if otel instruments jaeger itself 
      extraEnv:
      - name: JAEGER_LOG_LEVEL
        value: debug  
      enabled: true
      service:
        otlp:
          grpc:
            port: 4317
            name: otlp-grpc
          http:
            port: 4318
            name: otlp-http
    ingester:
      enabled: false  #required kafka
    query:
      ingress:
        enabled: false #to integrate
      extraEnv:
      - name: JAEGER_LOG_LEVEL
        value: "debug"
      replicaCount: 1
      enabled: true
      oAuthSidecar: # oAuthProxy possible to configure a security proxy for query service (keycloak)
        enabled: false
        resources: {}
    extraObjects: # any extra object to create like RoleBinding, ServiceAccount 
`

[cridam]

any news what's wrong (i use 3.3.1 chart back on 1.53.0) ? i alo tried the allinone configuration as well, i cannot see any log or any traces from the query interface.