effect-observability

To add distributed tracing and structured logging in Effect, you configure a Logger.layer and wrap effects with Effect.withSpan or Effect.fn spans. This emits rich log events with key-value metadata and creates annotated tracing spans for correlation across services.

You export metrics and traces from Effect to Prometheus or OTLP by wiring observability exporters from effect/unstable/observability at the app boundary. This sends telemetry to an OTLP collector or exposes Prometheus-formatted metrics endpoints.

The best way to track counters and histograms in Effect is by defining and updating Metric instruments. You register tagged dimensions for counters, gauges, histograms, summaries, and frequency distributions to measure runtime performance behavior.

Yes, you can configure different observability logger layers per environment in Effect. The approach supports configuring Logger.layers by environment and wiring the specific observability layers at the application boundary to isolate development and production telemetry.

No external Skill dependencies are required to implement OTLP telemetry export in Effect. You utilize the built-in effect/unstable/observability exporters to correctly wire layers and send structured logs, traces, and metrics to your collector endpoint.