Self-host Zipkin on a VPS
A distributed tracing system that collects timing data from your services and shows request traces. This uses in-memory storage, so traces reset when the container restarts.
levelrail-cli templates deploy zipkin --name my-zipkinSpecification
- Status
- Listed
- Category
- Monitoring
- Services
- zipkin
- Ports
- 9411
- Volumes
- 0
- Memory
- about 512 MiB
- arm64
- unknown
- amd64
- unknown
- Settings to fill in
- none
- License
- Permissive license, Apache-2.0
- Listing
- Community template
About Zipkin
A distributed tracing system that collects timing data from your services and shows request traces. This uses in-memory storage, so traces reset when the container restarts.
What it deploys
Zipkin runs as one service in a single Compose app, listening on port 9411.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| zipkin | openzipkin/zipkin | 3.6.1 | 9411 | none |
Before you install
- CPU architecture. arm64 unknown. The scan could not read a manifest or the tag is chosen at install time. This is not a claim either way.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
Settings and environment
You do not have to fill in anything. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| zipkin | JAVA_OPTS | Preset by the template |
First run
- Send spans to /api/v2/spans from your tracing library, then open the page to search traces.
Install Zipkin on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get zipkin -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy zipkin --name my-zipkin
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Zipkin.
Docs and upstream
More in Monitoring
- ZabbixEnterprise-grade network, server, and application monitoring with alerting and trend graphs.
- VictoriaMetricsA fast, resource-frugal time-series database that speaks the Prometheus query and remote-write APIs. Has no authentication, so point Prometheus-style senders at victoriametrics:8428 from other services in this project, or attach a domain only behind Basic Auth. Not published on the host.
- VictoriaLogsA log database with a built in web UI and low memory use, with a data volume. Send logs to port 9428 from this project. The API has no login, so restrict access before exposing it.
- VectorHigh performance observability data pipeline for logs and metrics. The install form carries vector.yaml as an editable file, so it starts with an HTTP source and a console sink.
- Uptime Kuma (MariaDB)Uptime Kuma with a MariaDB sidecar provisioned, for the setups that opt out of its default SQLite file.
- Uptime KumaA self-hosted uptime monitor with a clean dashboard for HTTP, TCP, DNS, and ping checks.