When uing Jaegerv2, how do you configure CORS so that a browser app can send traces

[TechWatching]

I have a Vue.js app that is using the opentelemetry SDK to send traces to Jaeger. I receive CORS errors when trying to send the traces to Jaeger. I have seen in the documentation that the allowed origins could be configured using the --collector.otlp.http.cors.allowed-origins CLI command parameter. But I have not been able to make it work:

podman  run --rm --name jaeger -p 16686:16686 -p 4318:4318 jaegertracing/jaeger  --collector.otlp.http.cors.allowed-origins=https://localhost:3000

When running this command, I receive an "unknown flag error".

[dosubot[bot]]

Hello, @TechWatching! I'm here to help you with your Jaeger configuration. Let's work together to solve this issue.

I found a similar closed issue regarding CORS headers on the OTEL HTTP endpoint in Jaeger. The issue was resolved by a pull request that enabled CORS settings on the OTLP HTTP endpoint ^[1].

To configure CORS for your Jaeger setup, ensure you are using the correct prefix for the configuration. The correct prefix for configuring CORS settings in Jaeger's OTLP HTTP endpoint is collector.otlp.http ^[2][3].

If you are receiving an "unknown flag error," it might be due to using an incorrect version of Jaeger that does not support this flag. Make sure you are using a version of Jaeger that includes this feature. If the flag is still not recognized, it could be due to a version mismatch or a different configuration issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[TechWatching]

@dosu I saw the PR but I don't know how to properly configuré this meeting in the Jaeger config file

[dosubot[bot]]

To configure CORS settings in the Jaeger configuration file, you need to set the allowed-headers and allowed-origins using the appropriate flags or configuration options. Here's how you can do it:

1. Allowed Headers: Use the flag cors.allowed-headers to specify a comma-separated list of headers that are allowed in CORS requests. For example:

   --cors.allowed-headers="Content-Type,Authorization"

2. Allowed Origins: Use the flag cors.allowed-origins to specify a comma-separated list of origins that are allowed to make CORS requests. For example:

   --cors.allowed-origins="http://example.com,http://anotherdomain.com"

These settings can also be configured in a configuration file using the viper library, where you would set the cors.allowed-headers and cors.allowed-origins keys with the appropriate values. The configuration will be parsed and applied to the CORSConfig structure, which handles the CORS settings for Jaeger ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[TechWatching]

With Jaeger v2, I have been told we should use a config file instad. Here is my config file:

receivers:
  otlp:
    protocols:
      http:
        include_metadata: true
        cors:
          allowed_origins:
            - https://localhost:3000
exporters:
  debug:
    verbosity: detailed
service:
  extensions: [jaeger_query, jaeger_storage]
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [debug]

extensions:
  jaeger_query:
    storage:
      traces: query_storage
  jaeger_storage:
    backends:
      query_storage:
        memory:
          max_traces: 100000

However that should not be enough as I have this error now on requests to traces: net::ERR_EMPTY_RESPONSE