# OTEL LGTM

OTEL LGTM is a self-hosted Docker image that provides an OpenTelemetry backend for observability data. It is open source and self-hosted, installable on ZimaOS.

Canonical page: https://ourlocalhost.com/app/3924/otel-lgtm

## Description

OTEL LGTM is a self-hosted Docker image that provides an OpenTelemetry backend for observability data.

## Platform availability

Available on 1 of 10 platforms: ZimaOS.

## Health score

17/100 (Low), based on 3 of 4 factors.
- Maintained: 0 (GitHub repository no longer exists)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Light to run: 40 (4 GB minimum RAM, runs on ARM)

## Links

- GitHub: https://github.com/bigbeartechworld/big-bear-casaos
- ZimaOS: https://github.com/bigbeartechworld/big-bear-casaos/tree/master/Apps/otel-lgtm

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/3924/otel-lgtm), the self-hosted and open-source app directory.
