Deploy Apache SkyWalking

Open-source APM and tracing: OAP server, BanyanDB and Horizon UI

Deploy Apache SkyWalking

Deploy and Host Apache SkyWalking on Railway

Apache SkyWalking is an open-source application performance monitoring (APM) system from the Apache Software Foundation. It collects distributed traces, metrics and logs from SkyWalking agents and OpenTelemetry, draws service topology maps, raises alarms, and shows it all in a web UI. It is built for microservices and cloud-native apps.

About Hosting Apache SkyWalking

A working SkyWalking setup needs three parts: the OAP server, which receives and analyses telemetry; a storage backend; and the web UI. This template deploys SkyWalking 11.1.0 with BanyanDB 0.11.2, SkyWalking's native database and upstream's default storage, and the Horizon UI 1.1.0, as three Railway services on the private network. BanyanDB keeps its data on a volume. OAP waits for BanyanDB, creates its schema on the first start and stays private. Only the UI is public, behind a login whose password is generated at deploy. Plan on about 2 GB of memory for the stack.

Common Use Cases

  • Tracing requests across microservices to find slow endpoints and failing calls
  • Monitoring service, instance and endpoint metrics with topology maps and alarms
  • Collecting OpenTelemetry traces, metrics and logs in one self-hosted backend

Dependencies for Apache SkyWalking Hosting

  • BanyanDB: SkyWalking's time-series storage, deployed as its own service with a volume
  • SkyWalking agents or OpenTelemetry SDKs in the apps you want to monitor

Deployment Dependencies

Implementation Details

Services in this template:

  • SkyWalking (public): the Horizon web UI. It reads data from OAP's query port (12800) and admin port (17128) over the private network.
  • OAP (private): the SkyWalking OAP server. Agents and OpenTelemetry send data to oap.railway.internal:11800 (gRPC); HTTP receivers listen on port 12800.
  • BanyanDB (private): standalone BanyanDB with all data on the /data volume.

After deploy:

  1. Open the SkyWalking service's public URL and sign in as admin. The password is HORIZON_ADMIN_PASSWORD in the SkyWalking service's Variables tab.
  2. Point your apps' agents at OAP, for example SW_AGENT_COLLECTOR_BACKEND_SERVICES=oap.railway.internal:11800 for SkyWalking agents, or an OTLP gRPC exporter at the same address.
  3. BanyanDB keeps traces and logs for 3 days and minute-level metrics for 7 days by default. Change this on the OAP service with the SW_STORAGE_BANYANDB_*_TTL_DAYS variables from upstream's bydb.yml, for example SW_STORAGE_BANYANDB_TRACE_TTL_DAYS.

OAP has no public domain, because its receivers have no login. To collect data from outside Railway, add a TCP proxy to port 11800 and set SW_AUTHENTICATION on OAP and in your agents. All three services build from the template's GitHub repo, so Railway shows you an update when a new SkyWalking version is merged there. Read the repo's CHANGELOG first and update all three services together.

Why Deploy Apache SkyWalking 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 Apache SkyWalking 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

More templates in this category

View Template
Rootprint
Open-source logs and traces with full-text search on object-storage.

Rootprint
1
View Template
Pyroscope profiling
Protected continuous profiling with durable Pyroscope storage.

Anton Orel
1
View Template
SigOnly
Deploy SigNoz with a working demo app & config in one click

zoeyjones
21