← Templates · Monitoring & Analytics
OC
OpenTelemetry Collector
CommunityVendor-neutral telemetry pipeline — receive traces, metrics, and logs over OTLP and fan them out to any backend.
Deploy OpenTelemetry Collector
| Runs | otel/opentelemetry-collector-contrib:0.163.1 |
|---|---|
| Stack | go |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard runs it standalone on a server you already pay for — no addons to provision, with zero-downtime deploys and scaling still included.
Deploying OpenTelemetry Collector is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A central ingestion point for traces/metrics/logs from every app on your team, fanned out to multiple backends
- Buffering and batching telemetry before forwarding it to a tracing/metrics backend or a vendor
- Normalizing OTLP data from different SDKs before it reaches storage
Good to know
- Ships with a debug exporter only — telemetry arrives and gets logged to this app's own output. Edit OTEL_CONFIG_YAML after deploy to add real exporters pointing at your tracing/metrics backend
- The whole config lives in the OTEL_CONFIG_YAML variable — there's no mounted config file, so reconfiguring the pipeline means editing that variable and redeploying
- Only the OTLP/gRPC port (4317) is this app's public port; OTLP/HTTP (4318) is reachable from other apps on your team's private network but not from outside Railyard