Debugging thrift_http in OpenTelemetry Collector to send Tekton Traces - Stack Overflow

I have an otel-collector deployed that works perfectly accepting OTLP traces. Now, I want configure Tek

I have an otel-collector deployed that works perfectly accepting OTLP traces. Now, I want configure Tekton to add traces of the executed Pipelines. Currently, it only provides traces in HTTP Thrift format.

Therefore, I added the Jaeger receiver and configured it in the receivers section:

receivers:
  # Enable Thrift receiver for Tekton traces
  jaeger:
    protocols:
      # grpc:
        # endpoint: 0.0.0.0:14250
      # thrift_binary:
        # endpoint: 0.0.0.0:6832 
      # thrift_compact:
        # endpoint: 0.0.0.0:6831
      thrift_http:
        endpoint: 0.0.0.0:14268

However, on the Tekton side, I get the following error:

2025/01/28 12:34:18 traces export: failed to send to :14268/api/traces: 400 Bad Request

On the collector logs I cannot see any extra error. How can I debug this? Is it possible that the thrift http protocol has been updated and it might not be compatible? Maybe Tekton might use an old version of Thrift?

I have an otel-collector deployed that works perfectly accepting OTLP traces. Now, I want configure Tekton to add traces of the executed Pipelines. Currently, it only provides traces in HTTP Thrift format.

Therefore, I added the Jaeger receiver and configured it in the receivers section:

receivers:
  # Enable Thrift receiver for Tekton traces
  jaeger:
    protocols:
      # grpc:
        # endpoint: 0.0.0.0:14250
      # thrift_binary:
        # endpoint: 0.0.0.0:6832 
      # thrift_compact:
        # endpoint: 0.0.0.0:6831
      thrift_http:
        endpoint: 0.0.0.0:14268

However, on the Tekton side, I get the following error:

2025/01/28 12:34:18 traces export: failed to send to http://app-to-kafka-collector.otel.svc.cluster.local:14268/api/traces: 400 Bad Request

On the collector logs I cannot see any extra error. How can I debug this? Is it possible that the thrift http protocol has been updated and it might not be compatible? Maybe Tekton might use an old version of Thrift?

Share Improve this question asked Jan 29 at 11:29 BigEndian32BigEndian32 311 silver badge5 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

I come back just to share the actual asnwer. According to the Tekton documentation and this issue (https://github/tektoncd/pipeline/issues/7175) I thought that the traces where exported in thrift_http, but it is actually OTLP http. So I just changed the url to http://app-to-kafka-collector.otel.svc.cluster.local:4318 and it started to work :) If someone uses this in the future, please share it here! :)

发布者:admin,转转请注明出处:http://www.yc00.com/questions/1745301858a4621481.html

相关推荐

发表回复

评论列表(0条)

  • 暂无评论

联系我们

400-800-8888

在线咨询: QQ交谈

邮件:admin@example.com

工作时间:周一至周五,9:30-18:30,节假日休息

关注微信