Jaeger client node is supported for HTTPS endpoint?

[Yasuyuki Kubota]

I'm trying to report a span with the Span reporting APIs (Thrift over HTTP (stable)) which is described in the following doc.

https://www.jaegertracing.io/docs/1.22/apis/#thrift-over-http-stable

I think that Jaeger client node is supported for HTTPS endpoint,

because this doc mentions,

"In these scenarios the Jaeger Clients can be configured to submit spans directly to the Collectors over HTTP/HTTPS."

"The same jaeger.thrift payload can be submitted in HTTP POST request to /api/traces endpoint, for example, https://jaeger-collector:14268/api/traces."

Is my understanding is right?

However,  I received the following error from jeager-collector when I tried to report span with the jaeger client node to HTTPS endpoint.

(3f1c9896-f590-4a63-a47d-44a31e21ec3b) Received response. Status: 400, Integration latency: 24 ms

(3f1c9896-f590-4a63-a47d-44a31e21ec3b) Endpoint response headers: {content-type=text/plain; charset=utf-8, x-content-type-options=nosniff, date=Thu, 11 Mar 2021 15:28:35 GMT, content-length=105, x-envoy-upstream-service-time=0, server=istio-envoy}

(3f1c9896-f590-4a63-a47d-44a31e21ec3b) Endpoint response body before transformations: Unable to process request body: *jaeger.Span error reading struct: Required field TraceIdHigh is not set

The route from HTTPS endpoint to jaeger-collector as follows:

AWS Lambda(Jaeger client node)--(HTTPS)-->AWS API Gateway(REST API Proxy)--(HTTP)-->AWS Network Load Balancer(istio-ingress-gateway)--(HTTP)-->jaeger-collector(k8s service port 14268)

I want to know whether this error is caused by the jaeger client node or the AWS API Gateway.

[Yasuyuki Kubota]

As a side note, I can report span with the following route.

AWS Lambda(Jaeger client node)--(HTTP)-->AWS Network Load Balancer(istio-ingress-gateway)--(HTTP)-->jaeger-collector(k8s service port 14268)

2021年3月12日金曜日 12:56:47 UTC+9 Yasuyuki Kubota: