OTEL LGTM
OTEL LGTM is a self-hosted Docker image that provides an OpenTelemetry backend for observability data.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
17/100 Low
- Maintained
- 0GitHub repository no longer exists
- Popular
- No data
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 404 GB minimum RAM, runs on ARM
Based on 3 of 4 factors.
Availability: platform listings confirmed 18 days ago
No GitHub repository data collected yet.
Checked 17 days ago - source: GitHub (bigbeartechworld/big-bear-casaos)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 2 CPU core(s), 10 GB disk. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start the app with the provided run script Run ./run-lgtm.sh (or mise run lgtm) to start the bundled OTEL LGTM container, the all-in-one OpenTelemetry observability stack. Without it, no dashboards or telemetry pipeline are running, so you will not see any app data. source
- Use Docker Compose for the OBI example For the OBI example, run docker compose up --build and wait for the services to initialize. The built-in traffic generator sends test requests automatically, so dashboards should start filling in; if you check too early, the UI may look empty. source
- Check incoming data with the debug exporter If your dashboards look empty, start the container with OTEL_COLLECTOR_DEBUG_EXPORTER=true ./run-lgtm.sh. This logs all received telemetry to the terminal, so you can tell whether data is reaching the collector. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I start the bundled OTEL LGTM container?
Run ./run-lgtm.sh or mise run lgtm to start the bundled OTEL LGTM container. Without it, no dashboards or telemetry pipeline are running, so you will not see any app data.
How can I check whether telemetry is reaching the collector?
Start the container with OTEL_COLLECTOR_DEBUG_EXPORTER=true ./run-lgtm.sh. This logs all received telemetry to the terminal, so you can tell whether data is reaching the collector.
Why might the OBI example dashboards look empty?
Run docker compose up --build and wait for the services to initialize. The built-in traffic generator sends test requests automatically, so dashboards should start filling in; checking too early may make the UI look empty.
What cost factors should I consider for a self-hosted LGTM OSS stack?
Cost depends on your setup and where you run the stack. Cross-region or cross-account data transfer can be expensive. Self-hosting can be cost-efficient when the cluster and automation are already efficient.
Answers sourced from github.com, github.com, github.com, www.reddit.com
Community
- An OpenTelemetry backend in a Docker image: Introducing grafana/otel-lgtm (reddit)
- How do I join target_info into OpenTelemetry metrics? (other)
- Enterprise LGTM Stack - Missing Logs - Grafana Labs Community Forums (other)
- open telemetry - Grafana Tempo not receiving OpenTelemetry traces from ... (forum)
- Open Source Monitoring tools : SigNoz Vs Grafana Vs The ... - Reddit (reddit)
Collected 48 days ago - public community threads