influxdata/telegraf

telegraf otel plugin does not support protobuf input

Open

#17,713 opened on Sep 29, 2025

View on GitHub
 (4 comments) (6 reactions) (0 assignees)Go (4,161 forks)batch import
feature requesthelp wantedsize/m

Repository metrics

Stars
 (9,892 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

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

Contributor guide

Research direction
Examine the existing gRPC based otel input plugin in Telegraf, then implement an HTTP server that accepts OTLP HTTP protobuf requests (content type application/x protobuf) and converts them to the same internal metric format used by the gRPC handler.
Tech stack
go
Domain
backendapiobservability
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoOpenTelemetryProtobuf
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60