Telemetry - Tracelit

Prefer a guided setup? In the Tracelit app, add a service and choose I’m an engineer (bash recipe) or I’m a vibe coder (explicit AI prompt). Both paths use language → framework → log library, then a live connection check for INFO and ERROR logs.

Why this exists

OpenTelemetry installs easily for traces. Application logs only show up in Tracelit when your logger is bridged (or when a runtime agent captures it — e.g. the Java agent + Logback). These pages document the exact recipes we show in onboarding:

Set OTLP env vars toward Tracelit ingest
Install the language SDK / agent
Wire your framework
Bridge your log library
Emit an INFO log and an ERROR, then verify

Shared environment variables

OTEL_SERVICE_NAME=my-service
OTEL_RESOURCE_ATTRIBUTES=deployment.environment=production
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.tracelit.app
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer <WORKSPACE_INGEST_KEY>

Protocol must be http/protobuf. SDKs that default to gRPC will fail silently against Tracelit ingest.

Supported deployment.environment values for backend services: local, development, production.

Languages

Language	Frameworks & log libraries	Guide
Go	Gin, Echo, Chi, Fiber, net/http — slog, zerolog, zap, logrus	Install
Node.js	Express, Fastify, NestJS — pino, winston, console	Install
Python	FastAPI, Flask, Django — logging, structlog, loguru	Install
Java	Spring Boot — Logback, Log4j2 via the official javaagent	Install
.NET	ASP.NET Core — ILogger, Serilog	Install
Ruby	Rails, Sinatra — Logger, Semantic Logger	Install
Rust	Axum, Actix — tracing, log	Install