OBSERVABILITY Signal 445
Direct OpenTelemetry log export from Rails bypasses Collector; two Ruby SDK bugs fixed upstream
↗
A team configured OpenTelemetry logs in Rails to export directly to Grafana Cloud without a Collector sidecar, and contributed upstream fixes for two Ruby SDK bugs they encountered.
Direct export from the Ruby SDK simplifies infrastructure for low-volume logging by removing the need for an OpenTelemetry Collector sidecar. The two bugs fixed, one dropping the endpoint base path and one mishandling HTTP 204 responses, would have blocked or silently broken log export to vendors like Grafana Cloud.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The team bypassed the OpenTelemetry Collector and exported logs directly from the Ruby SDK to Grafana Cloud, relying on the SDK's built-in batching for their low log volume.
The opentelemetry-exporter-otlp-logs gem dropped the base path from the OTLP endpoint (fixed in v0.5.1) and treated HTTP 204 responses as failures (fixed in v0.4.0).
The setup requires six gems including opentelemetry-logs-sdk and opentelemetry-instrumentation-logger, with configuration via standard OTLP environment variables and a Rails initializer.
THE CLUSTER