Skip to main content
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. This page describes the Levelrail template for Zipkin (Monitoring). It deploys the services below as one Docker Compose app on your own server. Project site: https://zipkin.io/. Recommended memory: about 512 MiB.

​
Services, ports and volumes

​
Environment variables

Passwords and keys marked as generated are created for you when the app is deployed and stored as secrets. Values are not shown here.

​
Security and requirements

Level: Standard. What this template needs:
  • Nothing beyond a standard container: no extra privileges, host mounts or published ports.
What Levelrail adds around it:
  • Automatic HTTPS and an ingress shield in front of every domain.
  • Deploys are gated on the health check before traffic switches.
  • One-step rollback to the previous revision.
  • Exposure report shows what is reachable from outside.
  • Host firewall rules managed for published ports.

​
Deploy Zipkin with Levelrail

In the dashboard, open Apps, choose New app, then Browse templates, and select Zipkin. Review the Compose body and deploy. With the CLI:
See the service template catalog for how templates work, and Getting started if you have not installed Levelrail yet.

​
More Monitoring templates

All templates are listed in the self-host gallery.
Last modified on November 2, 2026