otlp grpc trace and headers_setter

[elysiumHL]

Component(s)

extension/headerssetter

Describe the issue you're reporting

1. I found that if javaagent uses grpc trace endpoint, then the header_setter extension of otel-collector cannot handle the headers, X-Scope-OrgID is not set correctly. I'm not sure if this is normal
2. The javaagent and otel-collector configurations are as follows.

• Here is the configuration of javaagent

export OTEL_SERVICE_NAME="your-service-name"
export OTEL_EXPORTER_OTLP_HEADERS="tenant_id=abc"
export OTEL_EXPORTER_OTLP_ENDPOINT="http://otelcol:4317"
export JAVA_TOOL_OPTIONS="-javaagent:/path/to/opentelemetry-javaagent.jar"
java -jar myapp.jar

• Here is the configuration of the otell-Collector

extensions:
  memory_ballast:
    size_mib: 1024
  headers_setter:
    headers:
      - action: upsert
        key: X-Scope-OrgID
        from_context: tenant_id

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
        include_metadata: true
      http:
        endpoint: 0.0.0.0:4318
        include_metadata: true

processors:
  memory_limiter:
    limit_mib: 1536 
    spike_limit_mib: 512
    check_interval: 5s

exporters:
  debug:
    verbosity: detailed
  otlp/tempo:
    endpoint: tempo:4317
    tls:
      insecure: true
    auth:
      authenticator: headers_setter

service:
  extensions: [memory_ballast, headers_setter]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter]
      exporters: [debug, otlp/tempo]

[github-actions]

Pinging code owners:

• extension/headerssetter: @jpkrohling

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

I'm curious as to why this was closed. Did you find an solution that works for your situation?