Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

posthog-rails logs: /i/v1/logs returns JSON {} to protobuf OTLP requests, causing ExportLogsServiceResponse decode ERROR on every export

Aperta
  • Qualcosa non va?
#291 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ruby
Ambito
api, backend

Direzione di ricerca

The report identifies the /i/v1/logs ingestion endpoint and the OTLP logs exporter as the relevant entry points, but does not name repository files or tests. Start by tracing how the endpoint handles application/x-protobuf requests and compare its response with the OTLP/HTTP expectation described here. Done means protobuf requests receive a valid protobuf response (or an empty body) with the appropriate content type, without triggering the exporter decode error.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug team/logs

Summary

With config.logs_enabled = true, posthog-rails sets up OpenTelemetry::Exporter::OTLP::Logs::LogsExporter pointed at https://us.i.posthog.com/i/v1/logs. The exporter sends Content-Type: application/x-protobuf, but the endpoint replies 200 with content-type: application/json and a body of {}. The exporter then tries to decode that body as a protobuf ExportLogsServiceResponse and fails, which logs an ERROR on every batch export.

Environment

  • Ruby 3.3
  • posthog-ruby 3.23.x
  • posthog-rails 3.18.6
  • opentelemetry-exporter-otlp-logs 0.6.0 (latest)
  • opentelemetry-logs-sdk 0.8.0

Repro

curl -s -D - -X POST https://us.i.posthog.com/i/v1/logs \
  -H 'Content-Type: application/x-protobuf' \
  -H 'Authorization: Bearer phc_test' \
  --data-binary @/dev/null

Response:

HTTP/2 200
content-type: application/json
content-length: 2

{}

On a 2xx response the exporter calls log_partial_success(response.body), which runs ExportLogsServiceResponse.decode("{}") and raises Google::Protobuf::ParseError. Every export then logs:

ERROR -- : OpenTelemetry error: unexpected error decoding ExportLogsServiceResponse in OTLP::Exporter#log_partial_success - Error occurred during parsing - .../opentelemetry-exporter-otlp-logs-0.6.0/lib/opentelemetry/exporter/otlp/logs/logs_exporter.rb:246:in 'decode'

Expected vs actual

  • Expected: Per the OTLP/HTTP spec, the response uses the request's Content-Type, so a protobuf request gets back a protobuf-encoded ExportLogsServiceResponse. An empty body is a valid empty message. No error is logged.
  • Actual: The JSON {} body causes an ERROR-level log line on every batch export from every process. Records are still ingested, because the exporter has already returned SUCCESS. But the noise is constant and hides real export failures.

Suggested fix

  • Ingestion endpoint: for application/x-protobuf requests, return an empty body or a protobuf-encoded ExportLogsServiceResponse with content-type: application/x-protobuf.
  • Until then, posthog-rails could install a scoped OpenTelemetry.error_handler filter for this specific decode error, or document the noise.
Lingua principale
Ruby
Stelle
37
Fork
34
Merge medio
20h 30m
PR unite (30g)
24

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PostHog/posthog-ruby

Tutte le issue di PostHog/posthog-ruby

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.