Repository navigation
Service Loki
Loki is Atlas' Grafana-native log store, disabled by default. The OpenTelemetry Collector sends redacted OTLP logs to Loki's native endpoint. Grafana provisions a Loki datasource linked to Tempo. Atlas does not automatically scrape container stdout; an application must send OTLP logs to the Collector.
Loki is internal-only, has no Kong route, and should be queried through Grafana. The default retention is short for local development.
- SOURCE:
LOKI_SOURCE=disabledby default. - Internal endpoint:
http://loki:3100. - Direct host URL: none.
- Kong URL: none; no Kong route is generated.
- Grafana surface: the
Lokidatasource is provisioned when Grafana starts.
The service reads ./config/loki.yaml, mounted to /etc/loki/loki.yaml. LOKI_RETENTION_PERIOD defaults to 24h. Compactor retention is enabled: it runs every 10 minutes and deletes expired chunks after the configured two-hour delay. TSDB schema v13 and structured metadata are enabled. Only service.name becomes an index label (service_name). Other OTLP resource attributes and trace/span IDs stay structured metadata, which avoids high-cardinality indexes.
The image is distroless (no shell, no wget), and the loki binary has no probe flag. The container therefore has no health check; Docker watches only process liveness. The Collector waits for Loki to start, not to be ready, and its retry queue covers the startup window. To check readiness, call GET http://loki:3100/ready from another container on the network.
The OpenTelemetry Collector redacts application OTLP logs and exports them to Loki. Grafana queries Loki directly, and its datasource links trace IDs to Tempo. The Atlas-managed ingestion path goes through the Collector. Direct internal writes to Loki are possible but skip the Collector's redaction.
Support tier: experimental — Capability contract declared; no cited cold-start, workflow, or upgrade qualification run yet (evidence at v0.1.0).
| Capability | Status | Verification | Notes |
|---|---|---|---|
| Local Grafana-queryable log storage | supported | tested | Atlas provisions a single local Loki store, accepts redacted OTLP logs from the required Collector, and exposes them through a trace-linked Grafana datasource. |
| Automatic Atlas application log collection | not-supported | tested | The Collector persists logs that applications emit over OTLP, but Atlas does not scrape container stdout or install a Promtail/Docker logging driver automatically. |
| Highly available long-term log retention | not-supported | documented | The bundled filesystem-backed single replica is intended for short local retention and has no replicated object-store deployment. |
- If Grafana cannot query logs, confirm
LOKI_SOURCE=containerandLOKI_ENDPOINT=http://loki:3100. - Query a service with
{service_name="backend"}and add| trace_id = "<32-hex-trace-id>"to filter on OTLP structured metadata. - If the Collector is enabled, Loki must be in container mode too. Otherwise
./start.shstops before it starts any container. - If storage grows unexpectedly, check
LOKI_RETENTION_PERIODand compactor logs. - Roll back by setting
LOKI_SOURCE=disabled.
No upstream calls.
| Service | Category |
|---|---|
| grafana | infra |
| otel-collector | infra |
Open the full-size diagram for a full-screen view.
No high-confidence opportunities identified.
No high-confidence opportunities identified.
No high-confidence opportunities identified.