Self-host OpenObserve with Levelrail
A lightweight, single-binary observability platform for logs, metrics, and traces with a built-in UI.
- Authoropenobserve
- LicenceAGPL-3.0
- Memory512 MiB
- Archarm64
- Services1
How to self-host OpenObserve
-
Pull the images
One image is pulled on your server.
Show images
public.ecr.aws/zinclabs/openobserve:v0.90.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
OpenObserve requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 5080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 5080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then OpenObserve. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the OpenObserve docs page.
Deploy OpenObserve your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy OpenObserve from the CLI
levelrail-cli templates deploy openobserve --name my-openobserve Deploy OpenObserve with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/openobserve/deploy OpenObserve configuration
OpenObserve services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| openobserve | public.ecr.aws/zinclabs/openobserve:v0.90.0 | 5080 | openobserve_data -> /data |
OpenObserve environment variables
| Variable | Service | Value |
|---|---|---|
| ZO_DATA_DIR | openobserve | Preset by the template |
| ZO_ROOT_USER_EMAIL | openobserve | Preset by the template |
| ZO_ROOT_USER_PASSWORD | openobserve | Generated at deploy |
| ZO_TELEMETRY | openobserve | Preset by the template |
Ports and volumes
- Ports
- 5080
- Volumes
- 1 named mount: openobserve_data -> /data
OpenObserve FAQ
How much memory does OpenObserve need?
The catalog lists about 512 MiB of memory for OpenObserve.
Does OpenObserve run on arm64?
For OpenObserve, an arm64 image is published; amd64 is image published.
What licence is OpenObserve under?
OpenObserve is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does OpenObserve need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does OpenObserve use?
OpenObserve listens on port 5080 inside the stack.
Where does OpenObserve keep its data?
In a named volume: openobserve_data mounted at /data.
Can I deploy OpenObserve on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id openobserve for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image public.ecr.aws/zinclabs/openobserve:v0.90.0 is what you deploy there.