Self-host Grafana OTel LGTM with Levelrail
An all-in-one OpenTelemetry backend with an OTLP collector, Loki logs, Tempo traces, Prometheus metrics and Grafana in one container. The Grafana admin password is generated at install. OTLP ports are not published on the host, so send telemetry from other services in this project to otel-lgtm:4317 (gRPC) or otel-lgtm:4318 (HTTP).
- Authorgrafana
- LicenceApache-2.0
- Memory1 GiB
- Services1
How to self-host Grafana OTel LGTM
-
Pull the images
One image is pulled on your server.
Show images
grafana/otel-lgtm:0.40.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 3000, 4317, 4318.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 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.
After the first start
- Sign in to Grafana as admin with the generated password from the app secrets.
Grafana OTel LGTM requirements
- Memory
- About 1 GiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000, 4317, 4318
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Grafana OTel LGTM. 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 Grafana OTel LGTM docs page.
Deploy Grafana OTel LGTM your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Grafana OTel LGTM from the CLI
levelrail-cli templates install otel-lgtm --name my-otel-lgtm Deploy Grafana OTel LGTM with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/otel-lgtm/install \
-d '{
"name": "my-otel-lgtm"
}' Grafana OTel LGTM configuration
Grafana OTel LGTM services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| otel-lgtm | grafana/otel-lgtm:0.40.0 | 3000, 4317, 4318 | otel_lgtm_data -> /data |
Grafana OTel LGTM environment variables
| Variable | Service | Value |
|---|---|---|
| GF_SECURITY_ADMIN_PASSWORD | otel-lgtm | Generated at deploy |
| GF_SECURITY_ADMIN_USER | otel-lgtm | Preset by the template |
| TZ | otel-lgtm | Preset by the template |
Ports and volumes
- Ports
- 3000, 4317, 4318
- Volumes
- 1 named mount: otel_lgtm_data -> /data
Grafana OTel LGTM FAQ
How much memory does Grafana OTel LGTM need?
The catalog lists about 1 GiB of memory for Grafana OTel LGTM.
Does Grafana OTel LGTM run on arm64?
For Grafana OTel LGTM, arm64 support is not confirmed; amd64 is unknown.
What licence is Grafana OTel LGTM under?
Grafana OTel LGTM is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Grafana OTel LGTM need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Grafana OTel LGTM use?
Grafana OTel LGTM listens on ports 3000, 4317 and 4318 inside the stack.
Where does Grafana OTel LGTM keep its data?
In a named volume: otel_lgtm_data mounted at /data.
Can I deploy Grafana OTel LGTM on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Grafana OTel LGTM, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image grafana/otel-lgtm:0.40.0 is what you deploy there.