Deploy Grafana, Loki and Prometheus with OTEL Collector
Grafana, Loki and Prometheus with a centralized OTEL Collector
Just deployed
/var/tempo
Just deployed
/var/lib/grafana/
Just deployed
/loki
Prometheus
Just deployed
/prometheus
OTEL Collector
Just deployed
Deploy and Host Grafana, Loki and Prometheus with OTel Collector on Railway
A complete observability stack combining OpenTelemetry Collector, Grafana, Prometheus, Loki, and Tempo. This unified solution enables comprehensive application monitoring across metrics, logs, and distributed traces. The OTel Collector acts as a central telemetry hub, processing and routing data to specialized backends, all visualized through Grafana dashboards.
About Hosting Grafana, Loki and Prometheus with OTEL Collector
Deploying this stack involves configuring four interconnected services: the OpenTelemetry Collector receives telemetry data via OTLP protocols (HTTP/gRPC), Prometheus stores metrics via remote write, Loki aggregates logs, and Tempo manages distributed traces. Grafana serves as the visualization layer with pre-configured datasources. Services communicate internally via private networking, with only Grafana exposed publicly. Each component runs containerized with dedicated configuration files. The architecture assumes application-level OpenTelemetry instrumentation sends data to the collector, which then batches and routes it to appropriate backends for storage and analysis.
Common Use Cases
- Full-stack application observability with unified logs, metrics, and traces
- Microservices monitoring with distributed tracing across service boundaries
- Performance debugging and troubleshooting with correlated telemetry data
- Infrastructure monitoring and alerting via Prometheus metrics
- Centralized log aggregation for multi-service applications
Dependencies for Grafana, Loki and Prometheus with OTEL Collector Hosting
All dependencies are included in this template. The only thing you need to spin up is the service that you want to monitor and point it to the OTel Collector!
Deployment Dependencies
- https://opentelemetry.io/docs/
- https://grafana.com/docs/
- https://prometheus.io/docs/
- https://grafana.com/docs/loki/
- https://grafana.com/docs/tempo/
- https://github.com/biancarosa/railway-grafana-stack
Implementation Details
Ready-to-use OTel Collector points to the services spinned up in this template.
Your application only needs to send data to the OTLP Endpoints:
This is a base otel collector - so depending on the config you want, you can go to https://github.com/biancarosa/railway-grafana-stack and choose "Use this template" to create your own copy. Then you can change the repository on your railway deployment to point to your repo instead, which will allow you to fine-tune your OTel Collector configuration.
Why Deploy Grafana, Loki and Prometheus with OTEL Collector on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Grafana, Loki and Prometheus with OTEL Collector on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
GF_SECURITY_ADMIN_USER
Prometheus
biancarosa/railway-grafana-stackOTEL Collector
biancarosa/railway-grafana-stack