effect-time-tracing-logging

Timeouts guard asynchronous tasks by combining Clock to measure elapsed time and Duration to set limits. Use Effect.sleep with timeout logic to interrupt long-running operations and log when deadlines are exceeded, ensuring tasks complete within specified intervals.

Structured logging in effectful programs uses logInfo and logError APIs to emit machine-readable logs with context. Pair logging with tracing spans via withSpan to correlate events across async boundaries and track latency, enabling observability across distributed task execution.

Tracing spans with withSpan instrument async operations to measure latency end-to-end. Combine Clock.currentTimeMillis with Duration calculations inside spans to analyze performance, then export structured logs showing execution time and dependencies between concurrent tasks.

Clock provides millisecond-precision time access and Duration represents time intervals for concurrent code. Together they enable deadline-driven logic: access current time via Clock, calculate remaining Duration, and branch task execution based on time constraints in effectful programs.

Use tracing spans when you need to correlate multiple log events across async task boundaries and measure operation latency. Spans provide hierarchical context that simple logs lack, making them essential for observability when tasks spawn subtasks or call external services.

Time-based deadlines and logging are built into effectful program APIs through Clock, Duration, timeout, withSpan, and logInfo/logError. No external dependencies are required; the Skill uses only core effect utilities for implementing time control and structured instrumentation.