influxdata/telegraf

telegraf otel plugin does not support protobuf input

Open

#17,713 建立於 2025年9月29日

在 GitHub 查看
 (4 留言) (6 反應) (0 負責人)Go (9,892 star) (4,161 fork)batch import
feature requesthelp wantedsize/m

描述

Use Case

Telegraf open telemetry plugin assumes gRPC input. However there are applications (example: pulp) that log open telemetry using http protobuf port 4318)

Changing the service address to use port to 4318 in the current collector does not change its behavior of expecting gRPC data.

Please add support for http protobuf (already present on the http input plugin) to the otel input

Expected behavior

When listening on service address with port 4318 the otel input should accept and parse http protobuf POST data

Actual behavior

When listening on service address with port 4318 the otel input still expects gRPC input data

Additional info

No response

貢獻者指南

技術棧
go
領域
observabilitydata
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingOpenTelemetry protocolHTTPprotobuf
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the existing OpenTelemetry input plugin in plugins/inputs/opentelemetry/ and the HTTP input plugin in plugins/inputs/http/. The goal is to add HTTP protobuf support to the OTEL input, similar to how the HTTP input handles protobuf. Review the gRPC vs HTTP protobuf differences in OpenTelemetry specification. The issue does not have linked PRs or assignees; ensure the implementation aligns with maintainer expectations by checking comments for any additional guidance.